
This adds a bool column to volumes to notify consumers if the backend hosting the volume utilizes shared_targets or not. We use the volume-drivers capabilities report to determine this and default to True if a driver doesn't report anything. The purpose of the column is to notify Nova that it needs to do some sort of locking around connect/disconnect to be sure other volumes on the same node aren't sharing the iscsi connection. Using a default of "True" is safe because although locking and doing the extra checks might be somewhat inefficient it works fine because it will just appear that there's never any other volumes in use. So this change adds the column to the DB as well as an online migration to go through and update any existing volumes. With this and the service_uuid column consumers will have everything the need to: 1. determine if they need to lock 2. use the service_uuid as a unique lock name That last remaining change in this set will be to add the fields to the view-builder and bump the API version. Change-Id: If600c28c86511cfb83f38d92cf6418954fb4975e
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/
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
Description
Languages
Python
99.7%
Smarty
0.3%