Bug 1592891

Summary: [RFE] [V2V] Extend the virt-v2v-wrapper for OpenStack
Product: Red Hat CloudForms Management Engine Reporter: Anandeep Pannu <apannu>
Component: V2VAssignee: Marek Aufart <maufart>
Status: CLOSED ERRATA QA Contact: Kedar Kulkarni <kkulkarn>
Severity: high Docs Contact: Red Hat CloudForms Documentation <cloudforms-docs>
Priority: high    
Version: unspecifiedCC: aarapov, apannu, bthurber, dmetzger, fdupont, gblomqui, jfrey, jhardy, mburns, mfeifer, obarenbo, sclewis, simaishi, smallamp, ytale
Target Milestone: MVPKeywords: FutureFeature, Triaged
Target Release: 5.10.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-02-07 23:03:14 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: V2V Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1601090    

Description Anandeep Pannu 2018-06-19 14:30:53 UTC 
Description of problem:

The virt-v2v-wrapper is the Ansible wrapper for the the virt-v2v binary, and is the interface between CloudForms and the Virt-v2v functionality.  There is an existing solution for ovirt (RHV) which needs to be adapted for OpenStack v2v migration. 

The virt-v2v-wrapper communicates with a conversion VM on OpenStack, in contrast to RHV which uses a conversion host. This has to be taken into account when creating the OpenStack virt-v2v-wrapper. 

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 14 Kedar Kulkarni 2018-11-30 20:18:11 UTC 
With CFME 5.10.0.27 and Conversion VM/Instance correctly configured on OpenStack, I was able to migrate VMs successfully from VMware to OSP. This produced wrapper logs that indicated wrapper was used and working as designed.
Comment 15 errata-xmlrpc 2019-02-07 23:03:14 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2019:0212