Re: [ovirt-users] [RFI] oVirt 3.6 Planning
----- Original Message -----
From: "Blaster" <Blaster(a)556nato.com>
To: "Itamar Heim" <iheim(a)redhat.com>
Cc: users(a)ovirt.org
Sent: Sunday, December 21, 2014 7:56:12 AM
Subject: Re: [ovirt-users] [RFI] oVirt 3.6 Planning
On 12/12/2014 10:08 AM, Itamar Heim wrote:
>
> If your existing raw images are from an ovirt storage domain you can
> keep it as is and import the entire storage domain or specific vms
> from it.
> That's a new 3.5 feature. Mind you yii must first upgrade the storage
> domain to 3.5 before reinstalling
>
Thanks for the tip. This didn't work for me this time. My AIO setup
started out with 3.2, upgraded all the way up to 3.5, I was missing the
OVF files, so I couldn't import the storage domain. So I bit the bullet
one more time and did it the hard way (created new VMs, disks, then
copied over the old image). This time I created a storage domain for
each VM so I can import them into a new setup individually.
Creating storage domain per vm is not a good idea.
The system is expecting all storage domain to be accessible by all hosts. So
if you have multiple storage domains and one become inaccessible, a host
may become non-operational, which will cause migration storm from this host
to other hosts. Basically, the more storage domains you have, your system
is more fragile.
Create new storage domains only when you must (e.g. separating testing and
production environments). For importing and exporting vms, you can use the
export domain.
Nir