Bug 1469077 - [RFE] Import from kvm source when guest's disk type is volume
[RFE] Import from kvm source when guest's disk type is volume
Status: MODIFIED
Product: vdsm
Classification: oVirt
Component: RFEs (Show other bugs)
4.19.20
x86_64 Unspecified
medium Severity medium (vote)
: ovirt-4.2.0
: ---
Assigned To: Tomáš Golembiovský
Nisim Simsolo
: FutureFeature
Depends On: 1468509
Blocks:
  Show dependency treegraph
 
Reported: 2017-07-10 07:01 EDT by Tomáš Golembiovský
Modified: 2017-09-19 15:20 EDT (History)
13 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1468509
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: Virt
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
michal.skrivanek: ovirt‑4.2?
mavital: testing_plan_complete?
rule-engine: planning_ack?
michal.skrivanek: devel_ack+
rule-engine: testing_ack?


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
oVirt gerrit 79834 master POST v2v: allow import of disk with type='volume' 2017-07-26 06:52 EDT

  None (edit)
Comment 1 Tomáš Golembiovský 2017-07-10 07:07:32 EDT
*** Bug 1468509 has been marked as a duplicate of this bug. ***
Comment 2 Michal Skrivanek 2017-07-11 06:26:12 EDT
*** Bug 1468944 has been marked as a duplicate of this bug. ***
Comment 3 Tomáš Golembiovský 2017-07-11 09:24:34 EDT
For the context: type='volume' allows user to use disks from storage pool without caring about details how the pool was defined.

For example with the pool 'pool1' deined like:

    <pool type="dir">
      <name>pool1</name>
      <target>
        <path>/var/vm_pool/</path>
      </target>
    </pool>

The following disk definitions are equivalent:

    <disk type='file' device='disk'> 
      <source file='/var/vm_pool/machine1.qcow2'/>
      ...
    </disk>

and

    <disk type='volume' device='disk'> 
      <source pool='pool1' volume='machine1.qcow2'/>
      ...
    </disk>

Note You need to log in before you can comment on or make changes to this bug.