[Users] oVirt-engine Migration Docs
Hi guys, I've read the following regarding upgrading from 3.0 to 3.1... "Due to the nature of this upgrade, we DO NOT recommend it, users are advised to do a 3.1 clean installation, and to import all VM's and template into the new installation." I'm running a live ovirt-engine(very early 3.1 release with no upgrade path) system with 3 VM's and I'd like to do the recommended -- "clean installation and import all VM's and template", but I'd like to know if there are any detailed guides on how to do this? I also have an unused server that I can use as a spare host that I can add into my clean engine install to get the VDSM onto the latest version as well, but how do you go about exporting and importing the VM's and the template? I am working on a live system and downtime needs to be limited, not sure if this is the correct procedure? Prepare old engine: 1.) Create a export storage domain 2.) Suspend each VM and export (presume suspending is enough and they don't need to be shutdown?) 3.) Detach export storage domain Prepare new engine machine: 1.) Install new ovirt-engine 2.) "Restore previous keystore and preserve .sh scripts" presume this is how the configs and DB are restored? 3.) Log into ovirt as admin and add only the spare host (to ensure that VDSM 4.10 is used, because I'm currently using VDSM 4.9) 4.) Attach export storage domain 5.) Import VM's all running on new "spare" host Upgrade old VDSM hosts: 1.) Remove VDSM 4.9 on old hosts(2 of them)? 2.) Add/install the new hosts from inside webadmin to get the old hosts up to VDSM 4.10? I'll gladly document the steps in detail if there is no detailed guide already for this. Thanks, any assistance is greatly appreciated. Regards. Neil Wilson.
On 09/06/2012 03:58 PM, Neil wrote:
Hi guys,
I've read the following regarding upgrading from 3.0 to 3.1...
"Due to the nature of this upgrade, we DO NOT recommend it, users are advised to do a 3.1 clean installation, and to import all VM's and template into the new installation."
I'm running a live ovirt-engine(very early 3.1 release with no upgrade path) system with 3 VM's and I'd like to do the recommended -- "clean installation and import all VM's and template", but I'd like to know if there are any detailed guides on how to do this?
I also have an unused server that I can use as a spare host that I can add into my clean engine install to get the VDSM onto the latest version as well, but how do you go about exporting and importing the VM's and the template?
I am working on a live system and downtime needs to be limited, not sure if this is the correct procedure?
Prepare old engine: 1.) Create a export storage domain 2.) Suspend each VM and export (presume suspending is enough and they don't need to be shutdown?)
I'm pretty sure they need to be in 'down' state for export.
3.) Detach export storage domain
Prepare new engine machine: 1.) Install new ovirt-engine 2.) "Restore previous keystore and preserve .sh scripts" presume this is how the configs and DB are restored?
edit dns entry to point to new engine? backup the db on source engine and restore on new engine.
3.) Log into ovirt as admin and add only the spare host (to ensure that VDSM 4.10 is used, because I'm currently using VDSM 4.9) 4.) Attach export storage domain
you need to detach it from first engine.
5.) Import VM's all running on new "spare" host
Upgrade old VDSM hosts: 1.) Remove VDSM 4.9 on old hosts(2 of them)? 2.) Add/install the new hosts from inside webadmin to get the old hosts up to VDSM 4.10?
I'll gladly document the steps in detail if there is no detailed guide already for this.
Thanks, any assistance is greatly appreciated.
Regards.
Neil Wilson. _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Prepare old engine: 1.) Create a export storage domain 2.) Suspend each VM and export (presume suspending is enough and they don't need to be shutdown?)
I'm pretty sure they need to be in 'down' state for export.
Couldn't you take a live snapshot of the running VM, clone a new VM from the snapshot, and export the clone? Tim Hildred, RHCE Content Author II - Engineering Content Services, Red Hat, Inc. Brisbane, Australia Email: thildred@redhat.com Internal: 8588287 Mobile: +61 4 666 25242 IRC: thildred
On 09/07/2012 04:15 AM, Tim Hildred wrote:
Prepare old engine: 1.) Create a export storage domain 2.) Suspend each VM and export (presume suspending is enough and they don't need to be shutdown?)
I'm pretty sure they need to be in 'down' state for export.
Couldn't you take a live snapshot of the running VM, clone a new VM from the snapshot, and export the clone?
yes you can, in 3.1... but your source is 3.0 iiuc
Thank you very much for the info! On Fri, Sep 7, 2012 at 6:56 AM, Itamar Heim <iheim@redhat.com> wrote:
On 09/07/2012 04:15 AM, Tim Hildred wrote:
Prepare old engine: 1.) Create a export storage domain 2.) Suspend each VM and export (presume suspending is enough and they don't need to be shutdown?)
I'm pretty sure they need to be in 'down' state for export.
Thank you!
Couldn't you take a live snapshot of the running VM, clone a new VM from the snapshot, and export the clone?
yes you can, in 3.1... but your source is 3.0 iiuc
Although I'm running a very early release of 3.1 I'd still be happier downing the VM's completely rather than trying to do it live. Thank you very much for your advice, will attempt the upgrade next week if I have a chance. Regards. Neil Wilson.
participants (3)
-
Itamar Heim -
Neil -
Tim Hildred