On 08/09/2012 11:41 PM, Dominic Kaiser wrote:
So what is the answer we have to blow away our installations? What? That sounds like an awful way to upgrade.
that is the question i asked below, so would wait for a reply first.
dk
On Thu, Aug 9, 2012 at 10:50 AM, Itamar Heim <iheim@redhat.com <mailto:iheim@redhat.com>> wrote:
On 08/09/2012 02:35 PM, Gavin Spurgeon wrote:
Eli/Ofer/Juan - what was the result of fixing the upgrade script to work from 3.0 to 3.1?
Hash: SHA1
On 08/09/2012 11:55 AM, Jacob Wyatt wrote:
See the migration instructions at the bottom of the relese notes. Basically you shut down all of your VMs, export them to your export domain. Now all you have to do is preserve that export domain storage. Everything else should be blown away and rebuilt as a completely new install. Then you import that storage domain you saved and restore the VM's. It worked just fine for me.
But this requires that my entire Production Environment being off-line, to do a point update of the oVirt from 3.0 to 3.1.....
oVirt Nodes can run without a Manager being present and all Guest will stay Up and running. What if, Taking the whole environment off line, is not an option...
- From a DR point of view, oVirt needs a Backup solution to backup the Manager, and more importantly a Restore Option that would mean you can bring an oVirt Manager Back online without the whole lot being off-line.
__________________________________________ From: users-bounces@ovirt.org <mailto:users-bounces@ovirt.org> [users-bounces@ovirt.org <mailto:users-bounces@ovirt.org>] on behalf of Gavin Spurgeon [gspurgeon@dageek.co.uk <mailto:gspurgeon@dageek.co.uk>] Sent: Wednesday, August 08, 2012 11:35 AM To: users@ovirt.org <mailto:users@ovirt.org> Cc: Dale Macartney Subject: Re: [Users] Wondering about updating ovirt from 3.0 to 3.1
Hi All,
I know I am not the 1st to ask, and I know I will not be the last....
I have oVirt3.0 on F16, The Release Notes for 3.1 give a guide on how to upgrade oVirt to 3.1 via a Fedora Upgrade...
Can I do the same thing via a Clean Install of F17 (I do not like Upgrades of OS's) ?
Or is there a documented DR procedure assuming the host was backed up and a new Host/OS had to be used to get oVirt back on-line ?
Basically, What do I need to backup to then bring down the F16/oVirt3.0 Box and replace it with a F17/oVirt3.1 Box ?
Is this Documented yet ?
-- This message was scanned by DaGeek Spam Filter and is believed to be clean.
_________________________________________________ Users mailing list Users@ovirt.org <mailto:Users@ovirt.org> http://lists.ovirt.org/__mailman/listinfo/users <http://lists.ovirt.org/mailman/listinfo/users>
-- This message was scanned by DaGeek Spam Filter and is believed to be clean. Click here to report this message as spam. https://spam.dc.dageek.co.uk/__cgi-bin/learn-msg.cgi?id=__CCB7E27DF7.B3479 <https://spam.dc.dageek.co.uk/cgi-bin/learn-msg.cgi?id=CCB7E27DF7.B3479>
- --
Gavin Spurgeon. AKA Da Geek
- ------------------------------__------------------------------__---------- "The happiest of people don't necessarily have the best of everything, they just make the most of everything that comes along their way.."
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAlAjoGcACgkQvp6arS__3vDioQPQCbB55CGX5q3lGJ3dnJ5LY+__bjKA AgoAmgOn20QMNUWTBek3ONUknPFvgL__hU =sHwm -----END PGP SIGNATURE-----
-- This message was scanned by DaGeek Spam Filter and is believed to be clean.
_________________________________________________ Users mailing list Users@ovirt.org <mailto:Users@ovirt.org> http://lists.ovirt.org/__mailman/listinfo/users <http://lists.ovirt.org/mailman/listinfo/users>
_________________________________________________ Users mailing list Users@ovirt.org <mailto:Users@ovirt.org> http://lists.ovirt.org/__mailman/listinfo/users <http://lists.ovirt.org/mailman/listinfo/users>
-- Dominic Kaiser Greater Boston Vineyard Director of Operations
cell: 617-230-1412 fax: 617-252-0238 email: dominic@bostonvineyard.org <mailto:dominic@bostonvineyard.org>