[ClusterLabs] Special care needed when upgrading Pacemaker Remote nodes

[Ken Gaillot]

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 <kgaillot at redhat.com> 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.