Bug 1062910
Summary: | [RFE] Full support for vmware image conversion | ||
---|---|---|---|
Product: | [Retired] oVirt | Reporter: | Maurice James <midnightsteel> |
Component: | ovirt-image-uploader | Assignee: | Michal Skrivanek <michal.skrivanek> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | bugs <bugs> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 3.5 | CC: | gabicr, herrold, iheim, jiri.slezka, mbooth, mzhan, oourfali, rjones, s.kieske |
Target Milestone: | --- | Keywords: | FutureFeature, Reopened |
Target Release: | 3.6.0 | ||
Hardware: | Unspecified | ||
OS: | All | ||
Whiteboard: | virt | ||
Fixed In Version: | Doc Type: | Enhancement | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-06-02 10:55:09 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | Virt | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Maurice James
2014-02-08 14:16:14 UTC
AFAIK, you should use "virt-v2v -o rhev ......" in order to convert a vmware guet to oVirt/RHEV. So you already have a tool for doing that. Closing as wontfix since the tool already exists. (In reply to Sandro Bonazzola from comment #1) > AFAIK, you should use "virt-v2v -o rhev ......" in order to convert a vmware > guet to oVirt/RHEV. So you already have a tool for doing that. > Closing as wontfix since the tool already exists. This works only if you have an existing esx instance. If some on give me an exported vmware vm, how do I get it into RHEV/oVirt? Rich - any insight if the new guestconv will cover this use case? Is there any traction on this? (In reply to Maurice James from comment #2) > (In reply to Sandro Bonazzola from comment #1) > > AFAIK, you should use "virt-v2v -o rhev ......" in order to convert a vmware > > guet to oVirt/RHEV. So you already have a tool for doing that. > > Closing as wontfix since the tool already exists. > > This works only if you have an existing esx instance. If some on give me an > exported vmware vm, how do I get it into RHEV/oVirt? Currently there is no way to do this. We're working on some things upstream, and hope to eventually have OVA conversion working in virt-v2v, but there's no code at the moment. I also think that this is really needed feature. There are lot of (enterprise) appliances in form of *.ovf and there is no easy way to import them into oVirt (in contrast to VirtualBox for example). I vote also for possibility to import *.ovf also directly from web management... I guess these BZs overlap at least a bit, can they get merged? https://bugzilla.redhat.com/show_bug.cgi?id=1049604 (In reply to Sven Kieske from comment #8) > I guess these BZs overlap at least a bit, can they get merged? > https://bugzilla.redhat.com/show_bug.cgi?id=1049604 No, they are two quite different requests. (In reply to Jiří Sléžka from comment #7) > I also think that this is really needed feature. There are lot of > (enterprise) appliances in form of *.ovf and there is no easy way to import > them into oVirt (in contrast to VirtualBox for example). I vote also for > possibility to import *.ovf also directly from web management... Nothing is going to happen on this topic until someone steps up to do the work. Tentatively targeting this to 3.6 since it seems a widely requested feature. Richard, in comment #6 you said "We're working on some things upstream, and hope to eventually have OVA conversion working in virt-v2v, but there's no code at the moment." Do we have a reference bug on virt-v2v side for introducing this support? Something we can track? Dropping target 3.6 and reducing priority, need to figure out first when and if virt-v2v will support this use case. Reassigning to virt guys current RHEL 7 release understands .ova please open a virt-v2v bug if there is any specific issue/bug I do not think this is "closed current release". this bug was about support of conversion from vmware based ova's without a running esxi instance. maybe this bug should be assigned to virt-v2v instead of ovirt? virt-v2v would be better fit indeed. But from the perspective of oVirt support this is addressed as long as you are on EL 7 or Fedora; we added that in 3.5, hence closed in oVirt. virt-v2v already has support for importing OVAs (since 7.1). |