URL:
Reporter RHNID:
Section: - Importing and Exporting Virtual Machine Images
Language: en-US (English)||||||||
Workaround:

Description: #REF!

Description: In ch10s03, and steps 8-10 of ch10s04 GE, we use export domains to import and export OVA packages. Export domains are deprecated and this is likely to break in RHV 4.2. This content should be dropped and as necessary replaced at the next RHV 4.x revision.

For importing OVA files, you can use Admin Portal right now as long as the OVA packages are from VMWare. You can also directly import virtual machines from vCenter or a RHEL libvirt box.

For exporting OVA files, your only supported option is currently not the export domain hack (which was documented back in RHEV 3.2 admin guide appendix somewhere and since dropped) but to use the API. There's a python SDK example which supposedly works with upstream oVirt 4.2 to export a VM as an OVA: https://github.com/oVirt/ovirt-engine-sdk/blob/master/sdk/examples/export_vm_as_ova.py. I'm not sure this is official, not sure it'd be supported even once RHV 4.2 comes out. It'd also be considered out of scope at present.

Note that our current exam competency is not to do either of these things, but to take a disk image in QCOW2 or RAW format, import it as a floating disk into the data domain, and attach it to a newly-defined VM. There is no export competency.