7a19f6f5bd
If the source and destination volumes are in the same StorPool template (as defined by either the volume type or the global config setting), forego the need to create the transient snapshot at all and use StorPool's "base this volume on that one" API call (which does the same thing internally, but much more efficiently and atomically). If the destination volume should be in a different StorPool template, then make sure that the transient snapshot is also in that template so that, if other volumes are cloned from the same source volume later, they can all use the same data underneath (the internal workings of StorPool will detect that all those snapshots are exactly the same and not duplicate any data in the destination template). This will avoid data duplication, sometimes with drastic results. Bump the minimum required version of the "storpool" third-party library for snapshotUpdate(template=...) support. Change-Id: Ib9bb76cf2e2f2b035b92e596b1ef185558b190d6
7 lines
237 B
YAML
7 lines
237 B
YAML
---
|
|
features:
|
|
- |
|
|
StorPool driver: improved the way volumes are cloned into different
|
|
StorPool templates (exposed as Cinder storage pools) if requested,
|
|
eliminating some data duplication in the underlying StorPool cluster.
|