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?
* We use 'disk/' in the HostResource xml field instead of '/disk/'
for example in the ovf.
Who's 'we'?
* 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.
* I thought I read about export domains being deprecated, and
> incorrectly assumed the recently added OVA export/import was to make
> things better for one off import/export.
> Can anyone clarify the
following:
> * Is OVA import really just VMWare OVA's?
> * Are we really not spec compliant with the OVA/OVF format as my
> example above shows? OR do I misunderstand something?
> * After spending my time yesterday, I recall now that the deprecation
> of export domain is in favor of detaching and re-attaching ANY data
> domain.
> * What is the purpose of our OVA export if we ourselves indeed cannot
> import our own OVA? Or can you tell me how we import our own if I'm
> wrong.
> Please feel free to overshare details :), as any context
will help
> prevent more confusion on my part.
> ~Kyle
> _______________________________________________
> Users mailing list -- users(a)ovirt.org
> To unsubscribe send an email to users-leave(a)ovirt.org
> Privacy Statement:
https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct:
>
https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
>
https://lists.ovirt.org/archives/list/users@ovirt.org/message/MYWHJF4ZJS4...