Bug 1140156
| Summary: | RFE: Export to RHEV data domain | ||
|---|---|---|---|
| Product: | [Community] Virtualization Tools | Reporter: | Shahar Havivi <shavivi> |
| Component: | libguestfs | Assignee: | Richard W.M. Jones <rjones> |
| Status: | CLOSED UPSTREAM | QA Contact: | |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | unspecified | CC: | ahadas, iheim, mbooth, michal.skrivanek, ptoscano, rbalakri, rjones, shavivi |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | libguestfs-1.27.45-1.1.el7 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-09-14 14:11:54 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Shahar Havivi
2014-09-10 11:42:36 UTC
Not quite sure I understand the bug. Is there something virt-v2v should be doing which it doesn't do already? Its a general RFE bug, Two main issues that v2v need to address: 1. not create any dir on data domain (in export domain it does create the directory structure) - maybe a new flag to indicate export/domain... 2. add estimated size to each disk when calling v2v with --no-copy Just a note that in 1.27.43, there is a new -o vdsm mode, and all the --rhev* flags have been renamed to --vdsm* (but otherwise are unchanged). This is a development release so we're allowed to make significant changes to unreleased code like this. In 1.27.45, the ovf:actual_size field is an estimate when --no-copy is used. https://github.com/libguestfs/libguestfs/commit/88dea548031db0eaccc08b63c4ee1e3644cd0e83 (In reply to Richard W.M. Jones from comment #3) > Just a note that in 1.27.43, there is a new -o vdsm mode, and > all the --rhev* flags have been renamed to --vdsm* (but otherwise > are unchanged). > > This is a development release so we're allowed to make significant > changes to unreleased code like this. I think --ovirt* would make more sense? Pretty sure --vdsm* makes more sense, since these flags are only used when under the control of VDSM. |