![]() Previously deleting a key in certain qos specs was accomplished via 'update' API. Unfortunately, 'update' isn't able to tell the difference between setting a key with no value and deleting a key (and its value). This change adds an new API 'delete_keys' to qos_specs API extension. 'delete_keys' API allows client to specify a list of to-be-deleted keys in one single request (batch mode!), which can be handy when removing multiple keys in a qos specs. Example URL and request body for 'delete_keys' API: PUT to http://127.0.0.1:8776/v2/qos-specs/QOS_SPECS_UUID/delete_keys with body: {'keys': ['foo', 'bar', 'zoo']} Above example request will result in 'foo', 'bar', 'zoo' key/value pairs of QOS_SPECS_UUID be marked as deleted in DB. If QOS_SPECS_UUID doesn't exist, a 404 error will return; if any key in 'foo', 'bar', 'zoo' couldn't be found in QOS_SPECS_UUID, a 400 error will return with error message telling which key couldn't be found. Note that Cinder will puke 400 and stop trying the rest once it encounters a non-existing (or deleted) key amoung the given list of keys. This change also fixes 'list'/'show' API includes deleted keys in result. Fix bug: # 1223660 Fix bug: # 1223677 Change-Id: Ia3cb07e204d655a9b837b317ce7117feb3c86a2d |
||
---|---|---|
bin | ||
cinder | ||
contrib | ||
doc | ||
etc/cinder | ||
tools | ||
.coveragerc | ||
.gitignore | ||
.gitreview | ||
.mailmap | ||
.testr.conf | ||
CONTRIBUTING.md | ||
HACKING.rst | ||
LICENSE | ||
MANIFEST.in | ||
README.rst | ||
babel.cfg | ||
openstack-common.conf | ||
pylintrc | ||
requirements.txt | ||
run_tests.sh | ||
setup.cfg | ||
setup.py | ||
taskflow.conf | ||
test-requirements.txt | ||
tox.ini |
README.rst
The Choose Your Own Adventure README for 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.
To monitor it from a distance: follow @openstack on twitter.
To tame it for use in your own cloud: read http://docs.openstack.org
To study its anatomy: read http://cinder.openstack.org
To dissect it in detail: visit http://github.com/openstack/cinder
To taunt it with its weaknesses: use http://bugs.launchpad.net/cinder
To watch it: http://jenkins.openstack.org
To hack at it: read HACKING.rst