Hi, Justin Zygmont <jzygmont@proofpoint.com> writes:
This is true -- I have to bring everything down when I want to upgrade the system, especially the host itself. So I don't upgrade as often as I might if I had multiple hosts where I could migrate.
How can you do it without a second host and importing with a temporary storage domain?
I just shut everything down. So long as it's planned my users can >handle a 30-60 minute outage. And this is only when I update the >host. I can update the Engine on its own, and often will update my VMs >simultaneously to minimize downtime. But I'm okay with some >downtime.
I see, so you just did an in place update of engine I guess, what if you want to update the node as well, and install a new HE? You'd lose the locally stored NFS domains. Or what if the engine update stuffs up, there'd be no way to access the admin portal right?
Yes, log into engine and run: yum update 'ovirt-*-setup' Then engine-setup. As for the host, I'm not using Node. It's just a regular CentOS system with the ovirt host software installed. I update it the normal way you'd update any other CentOS system: yum update I don't understand what you mean by "install a new HE"? If this is a single-host system, what do you mean by installing a new hosted engine? If you're asking about starting with one host and adding a second host, then that returns back to the previous statement that you'd have to migrate HE to a new (Gluster-based) storage system. If you stayed with NFS, then you "master host" could never go down or your HE would also go down (because its [NFS-based] storage would go away). You're right that if the Engine update breaks somehow then the admin portal would go away -- but I'm never updating systems through the portal. It's always via SSH (or worst case local console on the host). If the engine update breaks so much that even ssh wont work, then I'm definitely in trouble. That's what backups are for! :) -derek -- Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory Member, MIT Student Information Processing Board (SIPB) URL: http://web.mit.edu/warlord/ PP-ASEL-IA N1NWH warlord@MIT.EDU PGP key available