FW: [Pacemaker] RFC: How do you upgrade?

Pinto, Phil (GTS) phil_pinto at ml.com
Tue May 6 14:15:27 EDT 2008


We would normally do a rolling implementation of a new release of heartbeat / pacemaker where possible.  We run with two node clusters in a virtualized environment.    

1. Shutdown Backup node 
2. Update Heartbeat and Pacemaker packages on the backup node
3. Restart the backup node 
4. Put the primary node in standby - to relocated the resources to the updated backup node 
5. Shutdown the Primary Node  
6. Install the updated Heartbeat / Pacemaker packages on the primary node 
7. Restart the primary node 
8. Take the primary node out of standby - it is now the backup node for the cluster 

This approach only requires a single application outage to the end users 

Phil Pinto 

-----Original Message-----
From: pacemaker-bounces at clusterlabs.org [mailto:pacemaker-bounces at clusterlabs.org] On Behalf Of Andrew Beekhof
Sent: Tuesday, May 06, 2008 9:03 AM
To: The Pacemaker cluster resource manager
Subject: [Pacemaker] RFC: How do you upgrade?

Me again,

I'd like to get a sense of how people upgrade their clusters...

* rolling upgrade (node-by-node)
* big-bang (all nodes at once with all resources stopped)
* detach and reattach (all nodes at once with resources still running)
* other?

I'm interested to know how popular the various methods are.


Pacemaker mailing list
Pacemaker at clusterlabs.org

This message w/attachments (message) may be privileged, confidential or proprietary, and if you are not an intended recipient, please notify the sender, do not use or share it and delete it. Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Merrill Lynch. Subject to applicable law, Merrill Lynch may monitor, review and retain e-communications (EC) traveling through its networks/systems. The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or error-free. This message is subject to terms available at the following link: http://www.ml.com/e-communications_terms/. By messaging with Merrill Lynch you consent to the foregoing.

More information about the Pacemaker mailing list