[ovirt-users] [RFI] oVirt 3.6 Planning

Itamar Heim iheim at redhat.com
Thu Nov 5 14:55:15 UTC 2015


On 11/05/2015 08:50 AM, Robert Story wrote:
> On Wed, 4 Nov 2015 19:06:18 -0500 Itamar wrote:
> IH> On 09/18/2014 11:35 AM, Robert Story wrote:
> IH> > On Fri, 12 Sep 2014 15:22:41 +0300 Itamar wrote:
> IH> > IH> With oVirt 3.5 nearing GA, time to ask for "what do you want to
> IH> > IH> see in oVirt 3.6"?
> IH> >
> IH> > I've always thought it would be a good idea to have a 'storage agent'
> IH> > to run on storage domains, which could perform some operations more
> IH> > optimally that the current system. For example, exporting/importing
> IH> > domains currently reads the whole VM image over the network, then
> IH> > writes it back. In my case, my storage is all located on the smae NFS
> IH> > server, which could simply do an OS copy locally, instead of
> IH> > reading/writing gigabytes over the network. I don't know if other
> IH> > storage type could perform similar optimizations
> IH>
> IH> not in 3.6. doing native storage operations is for sure a top item in
> IH> the storage list going forward.
> IH> notice you can do these operations today at disk level and register the
> IH> externally cloned disks via the REST API.
>
> That's good to know. Is there a wiki page/script for how to externally clone
> a VM for export?

need to check per storage type (which we'll do). for now, if you can 
clone it, we can register it.
netapp has a service that provides this in an integrated way.





More information about the Users mailing list