Third attempt to send to list also
> Yaniv,
> Most of this is obe...but I'll answer the questions. It's been resolved
> as in my other email to this chain.
>
>
> On Thu, Jun 14, 2018, 4:56 PM Yaniv Kaul <ykaul(a)redhat.com> wrote:
>
>>
>>
>> On Wed, Jun 13, 2018, 4:05 PM RabidCicada <rabidcicada(a)gmail.com> wrote:
>>
>>> All,
>>> I recently tried to used the OVA export/import functionality. It
>>> seems I misunderstood the intentions. I expected OVA export/import to
>>> be reciprocal functionalities. I expected what we export as OVA to be
>>> importable as OVA in ovirt.
>>>
>>> What I have found is the following:
>>>
>>> * It seems OVA export does export an OVA, though the format is not
>>> spec compliant
>>>
>>
>> Which spec?
>>
> I believe every version of the dmtd ovf specification.
>
>>
>> * We use 'disk/' in the HostResource xml field instead of '/disk/'
>>> for example in the ovf.
>>>
>>
>> Who's 'we'?
>>
> Ovirt software/group. I was including myself in a friendly manner soas to
> not sound accusatory. I know it's a group effort :).
>
>
>> * It seems OVA import is intended specifically for VMWare OVA's?
>>>
>>
>> That's a common case, but we can look at other OVAs. The problem is that
>> the spec is quite loose.
>> Y.
>>
>
> Agreed. I know that's why it's hard to be inter-compatible.
>
