
Currently, a request to ESM API for a snapshot deletion looks this way: {'addr': 'cms', 'data': { 'repoName': repository_name, 'lvName': snapshot_name}, 'op': 'orchStrLunMods', 'args': 'delClSnap'} This is correct, however, some versions of the ESM API have a bug that prevents it from validation this valid request and it fails with: Must define the new LV name to be assigned to the clone/clSnap. As a workaround for this bug, provide an 'newLvName' property with a 'noop' value to make the validation pass even on buggy versions. Fixes bug #1365417 Change-Id: I3fd7f3c6a64cac992735b098368b52b9ab21d85c
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
Description
Languages
Python
99.7%
Smarty
0.3%