Description of problem: Please implement v2v support in REST API. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
I understand the need for QA automation, but I'm not sure about practical usefulness. it's a very long running operation, rarely used. And it is just supposed to wrap virt-v2v invocation. It would be easier to call tools directly instead of proxying through ovirt.
setting this to low then
damn you, bot
We need to have probably two APIs: 1. When there is a VMware external provider in RHEV configured, to v2v the VMs. 2. Via CloudForms, be able to perform a V2V without specifying (creating) a VMware external provider in RHEV.
basic REST support is covered by bug 1346847, this one is for providers, perhaps even remote listing of VMs (item 1 from comment #4)
I thought this is all implemented?
I do not quite recall, but I think this one asked for more (like listing) than the "basic" support in bug 134687 I do not really see the need so let's close it *** This bug has been marked as a duplicate of bug 134687 ***