Bug 1306562 - [RFE] Allow virDomainBlockCopy to use remote RBD volumes as the base backing image
[RFE] Allow virDomainBlockCopy to use remote RBD volumes as the base backing ...
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: libvirt (Show other bugs)
x86_64 Linux
high Severity high
: rc
: ---
Assigned To: Peter Krempa
Han Han
: FutureFeature
Depends On: 760547
Blocks: 1293440 1306569 1477664 1546815 1558125 1519149
  Show dependency treegraph
Reported: 2016-02-11 05:05 EST by Lee Yarwood
Modified: 2018-05-10 17:38 EDT (History)
13 users (show)

See Also:
Fixed In Version:
Doc Type: Rebase: Bug Fixes and Enhancements
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Lee Yarwood 2016-02-11 05:05:55 EST
Description of problem:

At present virDomainBlockRebase only allows the base backing image to be identified by a local file path on the system or by referencing the device[index] already present in the domain [1].

This is an issue when copying the entire chain to a new base image that is not yet connected to the host in question. For example with RBD volumes there should be no need to map these to the system prior to calling virDomainBlockRebase. It would be useful if virDomainBlockRebase would accept the connection details of a remote RBD volume as the base and then handle connecting to the volume before starting the rebase operation. This would allow Openstack Nova and other higher level services to avoid having to map RBD volumes etc to the host prior to calling for a rebase, simplifying the process greatly.

[1] https://libvirt.org/html/libvirt-libvirt-domain.html#virDomainBlockRebase
Comment 7 Peter Krempa 2017-03-31 08:36:37 EDT
The main problem here is with virDomainBlockCopy, which can also be reached (in a limited way) from the virDomainBlockRebase API. Using RBD natively will only be possible with the virDomainBlockCopy since only that allows to pass in a target specification via XML which is necessary for network storage.

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