openstack/deb-cinder
Code Issues Proposed changes
RETIRED, further work has moved to Debian project infrastructure
8,428 Commits 6 Branches 247 Tags 38 MiB
106c14a84b
Go to file
John Griffith 106c14a84b Replication v2.1 (Cheesecake) 
This focuses the replication work on a specific use case,
and eliminates some of the ambiguity in earlier versions.

Additionally this implementation addresses needs for
devices that do replication based on the whole backend-device
or on Pools.

Use case:
  DR scenario, where a storage device is rendered inoperable.
  This implementation allows the preservation of user data
  for those volumes that are of type replication-enabled.

  The goal is NOT to make failures completely transparent
  but instead to preserve data access while an Admin tries
  to rebuild/recover his/her cloud.

It's very important to note that we're no longer interested in
dealing with replication in Cinder at a Volume level.  The concept
of have "some" volumes failover, and "others" left behind, proved
to not only be overly complex and difficult to implement, but we
never identified a concrete use-case where one would use failover
in a scenario where some volumes would stay and be accessible on
a primary but other may be moved and accessed via a secondary.

In this model, it's host/backend based.  So when you failover,
you're failing over an entire backend.  We heavily leverage
existing resources, specifically services, and capabilities.

Implements: blueprint replication-update

Change-Id: If862bcd18515098639f94a8294a8e44e1358c52a
2016-02-26 13:15:19 -07:00
cinder Replication v2.1 (Cheesecake) 2016-02-26 13:15:19 -07:00
doc Replication v2.1 (Cheesecake) 2016-02-26 13:15:19 -07:00
etc/cinder Merge "cinder-api-microversions code" 2016-02-25 00:38:03 +00:00
rally-jobs Disable Rally backup-related scenarios 2016-02-15 20:44:52 +02:00
releasenotes Merge "NetApp: Implement CGs for ONTAP Drivers" 2016-02-26 18:16:05 +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 Updated from global requirements 2016-02-20 21:54:23 +00:00
run_tests.sh Detect addition of executable files 2015-08-31 12:19:51 -04:00
setup.cfg Remove version per M-1 release instructions 2015-12-03 08:32:41 -06:00
setup.py Updated from global requirements 2015-09-18 16:37:17 +00:00
test-requirements.txt Updated from global requirements 2016-02-11 07:38:36 +00:00
tests-py3.txt Merge "Port netapp dataontap driver to Python 3" 2016-02-24 16:50:17 +00:00
tox.ini Revert changes to use ostestr 2016-02-17 16:04:40 +02:00

README.rst

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