RETIRED, further work has moved to Debian project infrastructure
Go to file
John Griffith 4eaf8f5909 Add ability to failback for replication V2.1
Initially we had setup replication V2.1 (Cheesecake) to NOT
do fail-back at least in the initial version.

It turns out that fail-back in the Cinder code is rather easy,
we just enable calling failover-host on a host that's already
failed-over and use the *special* keyword of "default" as the
backend_id argument which signifies we want to switch back to
whatever is configured as the default in the cinder.conf file.

To do this we just add some logic that checks the secondary_backend_id
param in volume.manager:failover_host and set service fields
appropriately.  Note that we're sending the call to the driver
first and giving it a chance to raise an exception if it can't
satisfy the request at the current time.

We also needed to modify the volume.api:failover_host to allow
failed-over as a valid transition state, and again update the
Service query to include disabled services.

It's up to drivers to figure out if they want to require some
extra admin steps and document exactly how this works.  It's also
possible that during an initial failover that you might want to
return a status update for all volumes NOT replicated and mark
their volume-status to "error".

Expected behavior is depicted in the service output here:
    http://paste.openstack.org/show/488294/

Change-Id: I4531ab65424a7a9600b2f93ee5b5e1a0dd47d63d
2016-02-29 14:59:55 -07:00
cinder Add ability to failback for replication V2.1 2016-02-29 14:59:55 -07:00
doc Remove unused pngmath sphinx extension 2016-02-28 20:38:22 +01:00
etc/cinder Misprint in policy.json 2016-02-27 12:22:44 +00:00
rally-jobs Disable Rally backup-related scenarios 2016-02-15 20:44:52 +02:00
releasenotes Merge "Move deprecation release notes to correct section" 2016-02-29 16:47:46 +00:00
tools Fix tox -e fast8 2016-01-08 11:05:44 -05:00
.coveragerc Change ignore-errors to ignore_errors 2015-09-21 14:25:22 +00:00
.gitignore Add reno for release notes management 2015-11-05 14:58:17 +01:00
.gitreview Initial fork out of Nova. 2012-05-03 10:48:26 -07:00
.testr.conf Move integrated tests to 'functional' directory 2016-02-09 23:28:27 +02:00
babel.cfg Initial fork out of Nova. 2012-05-03 10:48:26 -07:00
CONTRIBUTING.rst Update CONTRIBUTING.md to CONTRIBUTING.rst 2015-11-10 23:10:38 +08:00
HACKING.rst Hacking Checks for assertTrue/IsNone() 2015-11-25 11:22:35 -06:00
LICENSE Initial fork out of Nova. 2012-05-03 10:48:26 -07:00
MANIFEST.in Use setuptools-git. 2012-08-10 11:56:00 -04:00
openstack-common.conf Move oslo-incubator's scheduler module to cinder 2015-11-24 15:49:31 +01:00
pylintrc Use six to fix imports on Python 3 2015-06-11 17:19:19 +02:00
README.rst Update README.rst to current state 2015-01-12 14:02:24 +01:00
requirements.txt Merge "Move anyjson to test-requirements" 2016-02-29 13:35:40 +00:00
run_tests.sh Detect addition of executable files 2015-08-31 12:19:51 -04:00
setup.cfg replace deprecated oslo_messaging _impl_messaging 2015-12-18 20:56:32 +08:00
setup.py Updated from global requirements 2015-09-18 16:37:17 +00:00
test-requirements.txt Move anyjson to test-requirements 2016-02-20 23:32:41 +08:00
tox.ini Merge "always use pip constraints" 2016-02-29 18:45:29 +00:00

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.

Getting Started

If you'd like to run from the master branch, you can clone the git repo:

git clone https://github.com/openstack/cinder.git

For developer information please see HACKING.rst

You can raise bugs here http://bugs.launchpad.net/cinder

Python client

https://github.com/openstack/python-cinderclient.git