f2427b4618
Let drivers declare that they can clone a volume into a different pool and relax the checks when creating a volume from an image (both with and without the image cache). Change-Id: Idbac4dae00f9fa03fb14547a204666721bf67d96 Implements: blueprint clone-across-pools
17 lines
734 B
YAML
17 lines
734 B
YAML
---
|
|
features:
|
|
- Add the clone_across_pools driver capability
|
|
|
|
Drivers can now declare that they can clone a volume into a
|
|
different pool. Essentially, if this capability is declared, Cinder
|
|
will skip the check that the pool of the destination volume is the
|
|
same as the pool of the source volume.
|
|
|
|
Some drivers do not have such a restriction and it may be possible
|
|
to complete the "create volume from image" operation very
|
|
efficiently instead of falling back to the "attach and dd" option.
|
|
|
|
This affects creating a volume from an image with and without the
|
|
image cache. For more details please check `bp clone_across_pools
|
|
<https://blueprints.launchpad.net/cinder/+spec/clone-across-pools>`__
|