c5e2ed9daf
Async migration was introduced to accelerate the cloning of volume (
The cloned volume can be accessed after the migration starts, no need
to wait it for finishing).
However, before the migration finishes, snapshots cannot be created from
the source volume any more, which could affect subsequent clones from
the same source volume. That is the constraint of async migration.
The fix is adding the constraint to the doc of VNX driver. And give
users some advises on how to make the subsequent volume clone work.
Change-Id: I6ad3c6b967d5a33966b40c3a54c0f110576c8d87
Closes-bug: #1796825
(cherry picked from commit
|
||
---|---|---|
api-ref/source | ||
cinder | ||
contrib/block-box | ||
doc | ||
etc/cinder | ||
playbooks/legacy/cinder-tempest-dsvm-lvm-lio-barbican | ||
rally-jobs | ||
releasenotes | ||
tools | ||
.coveragerc | ||
.gitignore | ||
.gitreview | ||
.stestr.conf | ||
.zuul.yaml | ||
CONTRIBUTING.rst | ||
HACKING.rst | ||
LICENSE | ||
README.rst | ||
babel.cfg | ||
bindep.txt | ||
driver-requirements.txt | ||
lower-constraints.txt | ||
pylintrc | ||
requirements.txt | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini |
README.rst
Team and repository tags
CINDER
You have come across a storage service for an open cloud computing service. It has identified itself as Cinder. It was abstracted from the Nova project.
- Wiki: https://wiki.openstack.org/Cinder
- Developer docs: https://docs.openstack.org/cinder/latest/
- Blueprints: https://blueprints.launchpad.net/cinder
- Release notes: https://docs.openstack.org/releasenotes/cinder/
Getting Started
If you'd like to run from the master branch, you can clone the git repo:
For developer information please see HACKING.rst
You can raise bugs here https://bugs.launchpad.net/cinder
Python client
https://git.openstack.org/cgit/openstack/python-cinderclient