Re: [ClusterLabs] Cluster reboot fro maintenance
Maintenance worked perfectly: - cluster in maintenance: crm configure property maintenance-mode=true - update vm os etc - stop corosync/pacemaker - reboot - start corosync/pacemaker - cluster out of maintenance: crm configure property maintenance-mode=false - all resources went up ok Best regards Marco On Mon, 20 Jun 2016 15:42:11 -0500 Ken Gaillot wrote: > On 06/20/2016 07:45 AM, ma...@nucleus.it wrote: > > Hi, > > i have a two node cluster with some vms (pacemaker resources) > > running on the two hypervisors: > > pacemaker-1.0.10 > > corosync-1.3.0 > > > > I need to do maintenance stuff , so i need to: > > - put on maintenance the cluster so the cluster doesn't > > touch/start/stop/monitor the vms > > - update the vms > > - stop the vms > > - stop cluster stuff (corosync/pacemaker) so it do not > > start/stop/monitor vms > > - reboot the hypervisors. > > - start cluster stuff > > - remove maintenance from the cluster stuff so it start all the vms > > > > What is the corret way to do that ( corosync/pacemaker) side ? > > > > > > Best regards > > Marco > > Maintenance mode provides this ability. Set the maintenance-mode > cluster proprerty to true, do whatever you want, then set it back to > false when done. > > That said, I've never used pacemaker/corosync versions that old, so > I'm not 100% sure that applies to those versions, though I would > guess it does. > > ___ > 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 ___ 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] Cluster reboot fro maintenance
On 06/20/2016 07:45 AM, ma...@nucleus.it wrote: > Hi, > i have a two node cluster with some vms (pacemaker resources) running on > the two hypervisors: > pacemaker-1.0.10 > corosync-1.3.0 > > I need to do maintenance stuff , so i need to: > - put on maintenance the cluster so the cluster doesn't > touch/start/stop/monitor the vms > - update the vms > - stop the vms > - stop cluster stuff (corosync/pacemaker) so it do not > start/stop/monitor vms > - reboot the hypervisors. > - start cluster stuff > - remove maintenance from the cluster stuff so it start all the vms > > What is the corret way to do that ( corosync/pacemaker) side ? > > > Best regards > Marco Maintenance mode provides this ability. Set the maintenance-mode cluster proprerty to true, do whatever you want, then set it back to false when done. That said, I've never used pacemaker/corosync versions that old, so I'm not 100% sure that applies to those versions, though I would guess it does. ___ 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] Cluster reboot fro maintenance
Hi, i have a two node cluster with some vms (pacemaker resources) running on the two hypervisors: pacemaker-1.0.10 corosync-1.3.0 I need to do maintenance stuff , so i need to: - put on maintenance the cluster so the cluster doesn't touch/start/stop/monitor the vms - update the vms - stop the vms - stop cluster stuff (corosync/pacemaker) so it do not start/stop/monitor vms - reboot the hypervisors. - start cluster stuff - remove maintenance from the cluster stuff so it start all the vms What is the corret way to do that ( corosync/pacemaker) side ? Best regards Marco ___ 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