[ClusterLabs] OS Patching Process

Toni Tschampke tt at halle.it
Thu Nov 24 11:41:11 EST 2016

We recently did an upgrade for our cluster nodes from Wheezy to Jessie. 
To reduce possible problems with drbd we first updated the kernel to the 
backport version, which is the same as the stable kernel in Jessie.
After that drbd versions matched while one node was on whezzy and one 
node already was on Jessie.

While holding the cluster in maintenance we could safely upgrade the 
second node and then going through the different configuration/syntax 
changes from older corosync/pacemaker versions to the backport versions 
from Jessie.

Since the version jump was big from corosync 1 & pacemaker 1.1.7 to 
corosync 2 & pacemaker 1.1.15 there was quite some work dealing with 
upgraded configurations but cluster works again as expected.


Mit freundlichen Grüßen

Toni Tschampke | tt at halle.it
bcs kommunikationslösungen
Inh. Dipl. Ing. Carsten Burkhardt
Harz 51 | 06108 Halle (Saale) | Germany
tel +49 345 29849-0 | fax +49 345 29849-22
www.b-c-s.de | www.halle.it | www.wivewa.de


Weitere Informationen erhalten Sie unter www.wivewa.de

Am 22.11.2016 um 17:35 schrieb Jason A Ramsey:
> Can anyone recommend a bulletproof process for OS patching a pacemaker
> cluster that manages a drbd mirror (with LVM on top of the drbd and luns
> defined for an iscsi target cluster if that matters)? Any time I’ve
> tried to mess with the cluster, it seems like I manage to corrupt my
> drbd filesystem, and now that I have actual data on the thing, that’s
> kind of a scary proposition. Thanks in advance!
> --
> *[ jR ]*
>   /there is no path to greatness; greatness is the path/
> _______________________________________________
> Users mailing list: Users at clusterlabs.org
> http://clusterlabs.org/mailman/listinfo/users
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org

More information about the Users mailing list