Hi all, I have an Ubuntu 12.04 based HA cluster running a few CentOS VMs and was wondering what the best practices are for updating both the host machines and virtual machines that are managed by Corosync + Pacemaker?
I was thinking that I would put the cluster into maintenance-mode and then update the machines, but what if one of the updates require a machine reboot? I'm just worried that something will cause my cluster, and therefore my services, to go down. Here are the steps I was thinking: 1. put cluster into maintenance-mode 2. update vms 3. update secondary host 4. switch secondary host to primary (moving vms) 5. update host that was primary How does that sound? I'm not sure how switch secondary to primary by command, but I'm sure it's in the documentation somewhere. And I guess when I switch secondary to primary all of the VMs will be down momentarily? What do the professionals do to keep all of their cluster machines up to date without angering the entire customer base? Thanks, Josh _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
