----- Original Message -----
From: "Moti Asayag" <masayag(a)redhat.com>
To: "Itamar Heim" <iheim(a)redhat.com>
Cc: "engine-devel" <engine-devel(a)ovirt.org>
Sent: Sunday, July 14, 2013 11:25:41 AM
Subject: Re: [Engine-devel] VNIC profiles
On 07/13/2013 01:17 PM, Itamar Heim wrote:
> On 07/08/2013 11:21 AM, Moti Asayag wrote:
>>
>>
> ...
>>
>> The wiki was updated with the VM/Template import logic:
>>
>>
http://www.ovirt.org/Features/Vnic_Profiles#VM_snapshot.2Fimport.2Fexport
>
> 1. you are updating the OVF - have you found a matching field in the OVF
> spec[1] for vnic profiles?
>
Currently the only field used to specify the network is "Connection".
There is no specific field for specifying a vnic profile. We can make
a use of the 'OtherResourceType' which isn't in use by the engine for
storing the vnic profile name.
An alternative would be using the Connection field to store both
Network:Profile, and parsing it when a vm or template are being imported.
I'm in favour of the first option for simplicity and in order not to
modify the Connection field as is being used today.
I'm in favor of this option as well.
> 2. import/export - please note exporting is backward compatible
based on
> DC level (iirc - omer should remember better), i.e., if the DC is 3.2,
> the export should ignore vnic profiles, etc.
>
> 3. while at it - just to make sure before i add more comments- are the
> screenshots in the wiki up to date?
The images should be updated since the vnic profiles will be a main-tab,
appears only when a network is selected, instead of a sub-tab of the
networks.
>
> Thanks,
> Itamar
>
> [1]
http://dmtf.org/standards/ovf
_______________________________________________
Engine-devel mailing list
Engine-devel(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/engine-devel