... please don't bypass the mailing-list On 2013-01-18 09:44, Ollie Leahy wrote: > > On 17/01/13 22:25, Andreas Kurz wrote: >> Is there a special reason to no upgrade to at least Ubuntu 12.04 LTS? > We do want to get to 12.04 LTS, and we tried that first, but introducing > the > precise node (crm version 1.4.x) into the cluster caused the existing nodes > to crash. Since there were two minor versions between 11.04 and 12.04 we > thought we might have more luck taking the intermediate step. Not expected to work, yes >> >> Any suggestions for how to do a roling upgrade of a pacemaker/corosync >> cluster? >> You should test this: >> >> * compile latest 1.4 Corosync for both Ubuntu releases >> * switch Pacemaker to maintenance-mode on running systems >> * stop Pacemaker (services keep on running) >> * stop Corosync and upgrade Corosync in the old cluster and on the new >> system >> * start new 1.4 Corosync on old and new system and check if it works >> correctly >> * start old Pacemaker on old cluster and try to integrate new Pacemaker >> node ... if all is fine, disable maintenance-mode and switch-over >> services to new cluster-node. > Thanks for the detail instructions, I guess we will end up doing > something like this, > unfortunately it means we will have to interrupt service on production > clusters. No service downtime if you are using maintenance-mode ... you need to stop Pacemaker and Corosync but not your services ... except you use a service like DLM that needs Corosync membership information to run. Regards, Andreas -- Need help with Pacemaker? http://www.hastexo.com/now
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________ discuss mailing list discuss@xxxxxxxxxxxx http://lists.corosync.org/mailman/listinfo/discuss
