Bug 760796 - support moving volume to another pool
Summary: support moving volume to another pool
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Virtualization Tools
Classification: Community
Component: libvirt
Version: unspecified
Hardware: All
OS: All
unspecified
low
Target Milestone: ---
Assignee: Libvirt Maintainers
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-12-07 00:56 UTC by alekibango
Modified: 2016-03-23 14:42 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-03-23 14:42:27 UTC
Embargoed:


Attachments (Terms of Use)

Description alekibango 2011-12-07 00:56:29 UTC
Description of problem:

I wish to be able to move volume from one pool to another using libvirt api.
Possibly those pools could have different backend (lvm, dir, ...)

Comment 1 Daniel Berrangé 2011-12-07 09:25:21 UTC
Moving between different types of pools effectively means doing a deep copy of the data. This is in fact already possible by using the virStorageVolCreateXMLFrom API - this creates a volume in a pool, and then copies all data from the passed-in volume which can be in any other pool. Then just delete the original volume

Explicit support for moving volumes between pools would however be useful for moving volumes between pools of the directory pool type, since a minimal overhead rename could be done instead of full copy+delete.

Comment 2 Cole Robinson 2016-03-23 14:42:27 UTC
We have vol-upload and vol-download APIs which can enable this


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