On 03/11/2016 11:16 AM, Sven Kieske wrote:
On 10/03/16 15:24, Juan Hernández wrote:
On 03/10/2016 02:25 PM, Sven Kieske wrote:
On 07/03/16 09:47, Sven Kieske wrote:
On 06/03/16 22:04, Arik Hadas wrote:
Actually it depends on the content of the OVA file. If the OVA file was generated by vSphere (export VM) then since oVirt 3.6 you can import it via the webadmin (virtual machines tab -> import -> select OVA as the source). Note that you'll need to copy the OVA to one of your hosts that is installed with virt-v2v for that. This action is missing in the API.
Hi,
is there already a bug tracking this missing feature for the rest api or should I create one?
Ping?
As far as I know there is no such RFE, please open it.
Here you go:
https://bugzilla.redhat.com/show_bug.cgi?id=1316854
PS: It took me a while to find the rest api component (under ovirt-engine product).
In my opinion it should be selectable on the "product" level, just like the SDKs. What do you think?
From a developer point of view the API is a part of the engine: same repository, same build process, same release cycle, etc. So it makes sense to have it as component. It may make less sense from the user
Thanks Sven. point of view. Next time, if you have doubts when deciding the component, just use "General" or "RFEs". Actually, this particular request, will probably need changes in multiple places, not just the API, so the bug may be moved to other components. -- Dirección Comercial: C/Jose Bardasano Baos, 9, Edif. Gorbea 3, planta 3ºD, 28016 Madrid, Spain Inscrita en el Reg. Mercantil de Madrid – C.I.F. B82657941 - Red Hat S.L.