Re: [ClusterLabs] Special care needed when upgrading Pacemaker Remote nodes
On 10/31/2016 11:17 AM, Andrei Borzenkov wrote: > 31.10.2016 17:15, Ken Gaillot пишет: >> On 10/29/2016 07:55 AM, Ferenc Wágner wrote: >>> Ken Gaillot writes: >>> This spurred me to complete a long-planned overhaul of Pacemaker Explained's "Upgrading" appendix: http://clusterlabs.org/doc/en-US/Pacemaker/1.1-pcs/html/Pacemaker_Explained/_upgrading.html Feedback is welcome. >>> >>> Since you asked for it..:) >>> >>> 1. Table D.1.: why does a rolling upgrade imply any service outage? Always? >> >> Putting a node into standby will move all resources off it, so there's >> at least a brief outage. Although I suppose if all of your resources are >> live-migratable there wouldn't be. :) Probably worth a footnote to clarify. >> > > > What about stopping pacemaker leaving resources running, upgrading > pacemaker on the node, starting pacemaker? Is it technically possible? Yes, that's the "detach-and-reattach" method described at the link above. ___ Users mailing list: Users@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
Re: [ClusterLabs] Special care needed when upgrading Pacemaker Remote nodes
31.10.2016 17:15, Ken Gaillot пишет: > On 10/29/2016 07:55 AM, Ferenc Wágner wrote: >> Ken Gaillot writes: >> >>> This spurred me to complete a long-planned overhaul of Pacemaker >>> Explained's "Upgrading" appendix: >>> >>> http://clusterlabs.org/doc/en-US/Pacemaker/1.1-pcs/html/Pacemaker_Explained/_upgrading.html >>> >>> Feedback is welcome. >> >> Since you asked for it..:) >> >> 1. Table D.1.: why does a rolling upgrade imply any service outage? Always? > > Putting a node into standby will move all resources off it, so there's > at least a brief outage. Although I suppose if all of your resources are > live-migratable there wouldn't be. :) Probably worth a footnote to clarify. > What about stopping pacemaker leaving resources running, upgrading pacemaker on the node, starting pacemaker? Is it technically possible? ___ Users mailing list: Users@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
Re: [ClusterLabs] Special care needed when upgrading Pacemaker Remote nodes
On 10/29/2016 07:55 AM, Ferenc Wágner wrote: > Ken Gaillot writes: > >> This spurred me to complete a long-planned overhaul of Pacemaker >> Explained's "Upgrading" appendix: >> >> http://clusterlabs.org/doc/en-US/Pacemaker/1.1-pcs/html/Pacemaker_Explained/_upgrading.html >> >> Feedback is welcome. > > Since you asked for it..:) > > 1. Table D.1.: why does a rolling upgrade imply any service outage? Always? Putting a node into standby will move all resources off it, so there's at least a brief outage. Although I suppose if all of your resources are live-migratable there wouldn't be. :) Probably worth a footnote to clarify. > 2. Detach method: why use rsc_defaults instead of maintenance mode? Good question. I think that would be equivalent (and easier). I'll verify there are no special concerns and swap it. > > 3. When do you think 1.1.16 will be released? With approximately how >much ABI incompatibility in the libraries? I plan on starting the release cycle for 1.1.16 very soon. I expect all the ABI changes will be backward-compatible. I think we had a few public function additions but that's it. ___ Users mailing list: Users@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
Re: [ClusterLabs] Special care needed when upgrading Pacemaker Remote nodes
Ken Gaillot writes: > This spurred me to complete a long-planned overhaul of Pacemaker > Explained's "Upgrading" appendix: > > http://clusterlabs.org/doc/en-US/Pacemaker/1.1-pcs/html/Pacemaker_Explained/_upgrading.html > > Feedback is welcome. Since you asked for it..:) 1. Table D.1.: why does a rolling upgrade imply any service outage? Always? 2. Detach method: why use rsc_defaults instead of maintenance mode? 3. When do you think 1.1.16 will be released? With approximately how much ABI incompatibility in the libraries? -- Thanks, Feri ___ Users mailing list: Users@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
[ClusterLabs] Special care needed when upgrading Pacemaker Remote nodes
Hi all, See the following wiki page if you are planning a rolling upgrade to Pacemaker 1.1.15 from an earlier version, and your cluster includes Pacemaker Remote nodes: http://clusterlabs.org/wiki/Upgrading_to_Pacemaker_1.1.15_or_later_from_an_earlier_version Details for anyone interested: Pacemaker 1.1.15 included an increase in the LRMD protocol version, which applies to communication between Pacemaker Remote nodes and the full cluster nodes. Because that was the first time that had ever happened, the impact on rolling upgrades was not immediately noticed. I'm surprised we haven't received any reports of problems since 1.1.15 was released. Pacemaker 1.1.14 and earlier requires that the LRMD protocol version be identical between the cluster and remote nodes. Any change means the remote connection will fail. The workaround (detailed in the wiki page) is to use constraints to tie older remote nodes to older cluster nodes, and newer remote nodes to newer cluster nodes, until the rolling upgrade is complete. As of Pacemaker 1.1.15, the interpretation was modified so that older remote nodes may connect to newer cluster nodes. So going forward, it will be sufficient to upgrade all cluster nodes, then the remote nodes, in a rolling upgrade. It is even possible to leave the remote nodes on the older version, which might be useful, for example, if you are using a remote node to run a legacy application in an older OS environment. This spurred me to complete a long-planned overhaul of Pacemaker Explained's "Upgrading" appendix: http://clusterlabs.org/doc/en-US/Pacemaker/1.1-pcs/html/Pacemaker_Explained/_upgrading.html Feedback is welcome. -- Ken Gaillot ___ Users mailing list: Users@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
