[ovirt-devel] virt-v2v integration feature

[Itamar Heim]

On 09/02/2014 04:26 PM, Arik Hadas wrote:
> Hi All,
>
> Better late than never..
>
> Thanks for all the feedback, it was really constructive.
> I made major changes in the wiki page to address the comments,
> Please take another look:
> http://www.ovirt.org/Features/virt-v2v_Integration
>
> Thanks,
> Arik
>
> ----- Original Message -----
>> Hi All,
>>
>> The proposed feature will introduce a new process of import virtual machines
>> from external systems using virt-v2v in oVirt.
>> I've created a wiki page that contains initial thoughts and design for it:
>> http://www.ovirt.org/Features/virt-v2v_Integration
>>
>> You are more than welcome to share your thoughts and insights.
>>
>> Thanks,
>> Arik
>> _______________________________________________
>> Devel mailing list
>> Devel at ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/devel
>>
> _______________________________________________
> Devel mailing list
> Devel at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel
>

much much better :)
now we just need to do all this...

few comments:
- upload vm - indeed tbd, but hopefully will resolve this as well
   independently.
- Windows VMs - v2v would need to make sure relevant iso is in the iso
   domain probably with the drivers expected by v2v?
- proxy host - do we really need this? I assume we are going to require
   virt-v2v by vdsm, so all hosts will simply have all needed to do
   this. to rephrase - I wouldn't make this the architectural choice to
   require a single host with v2v, rather default to all (for both
   ovirt-node and plain deployment)
   we may still want to allow choosing which host to do the import from,
   for specific network toplogy use cases. I wouldn't default to that,
   and i think it can be phase II actually
- per shahar's comment on SPM from discussion with storage group - just
   a btw we hope SPM to go away in 3.6. still, you should separate meta
   data (create volume) and data (copy) operations.
- external providers - I think this one requires more thinking. if you
   will define these as providers, with their credentials, then all
   admins can import. i don't think we should require the provider to be
   defined, not require it to keep credentials (could be just a helper
   list).
   i.e., unlike the other providers, i think here the providers are just
   to auto complete fields in the import form (i can choose a provider
   with its user/password, i can choose a provider without user/pass and
   fill myself, i can just type provider and user/pass)
- I'll be able to provider more feedback on mockups...

Thanks,
    Itamar