I will "back port" the release notes into the new migration guide at some point in the future. But in order to migrate to glu 5.1.0, you should:
* since 4.6.2 is java 1.6, you need to migrate to glu 4.7.2 first
* then upgrade your java environment to java 1.7
* then migrate to 5.1.0 (5.0.0 is simply the same as 4.7.2 but compiled with java 7 so you can skip) or in other words the steps from 5.0.0 -> 5.1.0 are the same as 4.7.2 -> 5.1.0 (AFTER you are running under java 7)
I guess you could switch from 4.6.2 to 5.1.0 directly as long as you switch from Java 6 to Java 7 at the same time.
In practice upgrading the agents is rather simple. What we do is:
* stop the old agent
* install the new agent
* copy the data directory from the old install
* copy the pre_master_conf.sh from the old install
* update JAVA_HOME in pre_master_conf.sh if needed
* start the new agent
The console is fairly similar except the data is stored in the DB and we just need to pass the config files along.
Unfortunately this is all from memory and I don't have a detailed procedure to share.
There is a section in the documentation about how to upgrade the agents. By far the recommended way is to use the console as it does it for you: you simply need to point to the "upgrade" tar ball. (Also note that since 5.1.0 you can build your own custom upgrade tarball).
The gotcha with upgrading the agents from the console is that it does not preserve pre_master_conf.sh since it is inside the versioned directory. Our approach around it is that we have a pre_master_conf.sh symlink in that versioned directory that point to a static pre_master_conf.sh that is machine specific (agent name and fabric name are set there). We have the agents managed by Salt anyhow so we do not use the console to upgrade them.
1) with 5.1.0 you can build your own agent upgrade tar ball which can obviously include your own pre_master_conf.sh (although you may not even need to do that, as configTokens may be enough!)
2) there is this ticket (https://github.com/pongasoft/glu/issues/215) about "Add ability to configure agent outside the "tarball"" which I will implement in the next release of glu (did not want to add more changes as there were already so many in this one)
Yan , i tried to upgrade agents.
But the problem is i have to manually restart agent to get it done. Though agent has been upgraded but while opening on glu console. console is throwing run time exception.
And please tell how to upgrade console also
-=Zed=- a.k.a -=Fauji=-
More quieter you are , more you can hear
Upgrading the agents should not require manual intervention. Only the migration from java 6 to java 7 should as there is no current way to bounce an agent. With the small amount of details you provide ("console is throwing run time exception") I am not sure what you want me to do about it.
Upgrading the console depends on what you did to configure it and which database you use. After 5.1.0 it is a lot cleaner and easier since you should keep your customization outside the console in the meta model. That being said since you are not there, the way to upgrade is the following:
* shut down the running console
* copy your conf/glu-console-webapp.groovy into the conf folder of the new console
* copy your jetty-distribution-8.1.10.v20130312/database folder (IF you are using the database provided with glu, which is not recommended) into the jetty-distribution-8.1.10.v20130312 folder of the new console