--Apple-Mail=_0ECB03C9-E3A7-455D-8F4D-5DD3F97F58B5 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 On Sep 12, 2014, at 4:35 PM, Itamar Heim <iheim@redhat.com> wrote:
=20 =20 On 12.09.2014 14:22, Itamar Heim wrote:
With oVirt 3.5 nearing GA, time to ask for "what do you want to see = in oVirt 3.6"? =20 An official supported way to import existing raw disk images would be = nice. =20
On 09/12/2014 04:22 PM, Morten Stevens wrote: please review: http://www.ovirt.org/Features/virt-v2v_Integration
I don=92t think that=92s what we are looking for. With this process, if = I have an X size virtual disk, I have to come up with X+2X more storage = to go through this silly import process. With ESXi, I just right click, = add to inventory and I=92m off. Right now, I=92m looking at moving my AIO configuration to a new host. = I=92ll have to create the new AIO host, create a new storage domain on = the old disks, create new VMs that look like the old ones, create new = virtual disks, then go rummage around the storage, figure out what=92s = what in these user unfriendly UUID names, then move the old images onto = the new ones. With ESXi, I just reinstall the hypervisor, create the new VM, then = right click, add to inventory on the old disk image, and I=92m done. https://bugzilla.redhat.com/show_bug.cgi?id=3D1049604 The concept of storage domains seems rather clumsy and limited to me. --Apple-Mail=_0ECB03C9-E3A7-455D-8F4D-5DD3F97F58B5 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=windows-1252 <html><head><meta http-equiv=3D"Content-Type" content=3D"text/html = charset=3Dwindows-1252"></head><body style=3D"word-wrap: break-word; = -webkit-nbsp-mode: space; -webkit-line-break: = after-white-space;"><br><div><div>On Sep 12, 2014, at 4:35 PM, Itamar = Heim <<a href=3D"mailto:iheim@redhat.com">iheim@redhat.com</a>> = wrote:</div><br class=3D"Apple-interchange-newline"><blockquote = type=3D"cite">On 09/12/2014 04:22 PM, Morten Stevens = wrote:<br><blockquote type=3D"cite"><br><br>On 12.09.2014 14:22, Itamar = Heim wrote:<br><blockquote type=3D"cite">With oVirt 3.5 nearing GA, time = to ask for "what do you want to see in<br>oVirt = 3.6"?<br></blockquote><br>An official supported way to import existing = raw disk images would be nice.<br></blockquote><br>please review:<br><a = href=3D"http://www.ovirt.org/Features/virt-v2v_Integration">http://www.ovi= rt.org/Features/virt-v2v_Integration</a></blockquote><br></div><div>I = don=92t think that=92s what we are looking for. With this process, = if I have an X size virtual disk, I have to come up with X+2X more = storage to go through this silly import process. With ESXi, I just right = click, add to inventory and I=92m off.</div><div><br></div><div>Right = now, I=92m looking at moving my AIO configuration to a new host. = I=92ll have to create the new AIO host, create a new storage = domain on the old disks, create new VMs that look like the old ones, = create new virtual disks, then go rummage around the storage, figure out = what=92s what in these user unfriendly UUID names, then move the old = images onto the new ones.</div><div><br></div><div>With ESXi, I just = reinstall the hypervisor, create the new VM, then right click, add to = inventory on the old disk image, and I=92m = done.</div><div><br></div><div><a = href=3D"https://bugzilla.redhat.com/show_bug.cgi?id=3D1049604">https://bug= zilla.redhat.com/show_bug.cgi?id=3D1049604</a></div><div><br></div><div>Th= e concept of storage domains seems rather clumsy and limited to = me.</div><div><br></div></body></html>= --Apple-Mail=_0ECB03C9-E3A7-455D-8F4D-5DD3F97F58B5--