Sean McGinnis e918482674 Use constants for microversion values
We very often end up with merge conflicts for any patches that increment
microversions due to conflicting numbers. We can't really solve that,
but we can avoid the need to update version numbers throughout the code
by defining a constant value in one place and using that variable instead.

Change-Id: Ib3a80fee6caaabb49af097aa197f550c65d94985
2017-09-22 08:15:56 -05:00
2017-09-06 07:39:10 -05:00
2017-09-22 08:15:56 -05:00
2016-07-26 11:09:05 -05:00
2012-05-03 10:48:26 -07:00
2012-05-03 10:48:26 -07:00
2017-04-08 15:03:44 +08:00
2017-09-07 11:55:44 +08:00
2012-05-03 10:48:26 -07:00
2015-06-11 17:19:19 +02:00
2017-07-13 12:12:20 +00:00
2017-03-02 23:53:29 +00:00
2017-08-16 16:18:48 -04:00

Team and repository tags

image

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://git.openstack.org/openstack/cinder.git

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
OpenStack Block Storage (Cinder)
Readme 913 MiB
Languages
Python 99.7%
Smarty 0.3%