On Mo, 2014-05-12 at 16:02 -0400, Doron Fediuck wrote: > > ----- Original Message ----- > > From: "Darrell Budic" <[email protected]> > > To: "Doron Fediuck" <[email protected]> > > Cc: "users" <[email protected]> > > Sent: Monday, May 12, 2014 10:15:53 PM > > Subject: Re: [ovirt-users] Ovirt-3.4.1: How to: Upgrading Hosted Engine > > Cluster > > > > > > On May 10, 2014, at 1:47 AM, Doron Fediuck <[email protected]> wrote: > > > > > > > > > > > ----- Original Message ----- > > >> From: "Daniel Helgenberger" <[email protected]> > > >> To: [email protected] > > >> Sent: Friday, May 9, 2014 6:45:36 PM > > >> Subject: [ovirt-users] Ovirt-3.4.1: How to: Upgrading Hosted Engine > > >> Cluster > > >> > > >> 1. Set cluster to global maintance > > >> 2. Login to ovit engine and to the upgrade according to the release > > >> nodes. > > >> 3. After the upgrade is finished and the engine running, set the > > >> first Node in local maintenance. > > >> 4. Login the first node and yum update (with the removal of > > >> ovirt-release as mentioned in release notes).* I rebooted the > > >> node because of the kernel update. > > >> 5. Return to oVirt and reinstall the Node from GUI, it will be set > > >> to operational automatically** > > >> 6. Repeat steps 3-6 for the rest of the Nodes. > > >> 7. Remove global maintenance. > > >> 8. Update the last Node.*** > > >> > > > > > > Hi Martin, > > > Thanks for sharing! > > > > > > A few notes on your nice 8 steps ;) > > > > > > - There are 2 maintenance modes to cover host maintenance (local) and > > > VM maintenance (global). Global maintenance disarms all HA hosts in > > > the cluster, so use it with caution as there's no fail over in this > > > mode. > > > > > > - Initially these were available only as a command line[1]. Since 3.4.0, > > > this was integrated into the UI, so all you need to do is move a host > > > to maintenance in order to achieve local maintenance, and activate it > > > to remove the maintenance mode. For global maintenance, right click > > > the engine VM, and you will see enable/disable ha-maintenance for > > > the global mode. > > > > > > - No need to re-install nodes. All you need to do is activate it. > > > > > > - Basically a standard procedure should include: > > > * Move host to maintenance, login and update the host, activate the host. > > > * Follow the above for all other HA hosts > > > * Set the engine VM to ha maintenance (global), login to the vm and > > > upgrade it, unset vm's ha-maintenance. > > > > > > Appreciate your feedback. > > > Also, were you aware of [1] or did you look for info elsewhere? I'd like > > > to know what we can do to improve documentation. Hi Doron,
thanks for pointing out [1]. I was not aware of this, basically these are the steps I wrote ;) Thanks for pointing out the availability of the maintenance mode in the GUI; I noticed local maint. being transparent (from GUI -> command line, though not the other way around). Also, I need the global maintenance for step one because of the engine upgrade because I suspect ha-agent would interfere because of necessary service restarts/downtime. It could have been reactivated much earlier though! Cheers, Daniel -- Daniel Helgenberger m box bewegtbild GmbH P: +49/30/2408781-22 F: +49/30/2408781-10 ACKERSTR. 19 D-10115 BERLIN www.m-box.de www.monkeymen.tv Geschäftsführer: Martin Retschitzegger / Michaela Göllner Handeslregister: Amtsgericht Charlottenburg / HRB 112767
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Users mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/users
