Official Title: OpenStack Block Storage Cinder
PTL: Sean McGinnis <sean d0t mcginnis at gmail d0t com>
To implement services and libraries to provide on demand, self-service access to Block Storage resources. Provide Software Defined Block Storage via abstraction and automation on top of various traditional backend block storage devices.
Cinder is a Block Storage service for OpenStack. It's designed to allow the use of either a reference implementation (LVM) to present storage resources to end users that can be consumed by the OpenStack Compute Project (Nova). The short description of Cinder is that it virtualizes pools of block storage devices and provides end users with a self service API to request and consume those resources without requiring any knowledge of where their storage is actually deployed or on what type of device.
See current members.
Getting in Touch
We use the email@example.com mailing list for discussions using subjects with the prefix "[cinder]". We also hang out on IRC in #openstack-cinder on freenode. IRC logs are available in: http://eavesdrop.openstack.org/irclogs/#openstack-cinder/
Core Volume Drivers
For a list of the core drivers in each OpenStack release and the volume operations they support, see https://wiki.openstack.org/wiki/CinderSupportMatrix
For any new features, significant code changes, new drivers, or major bug fixes, please add a release along with your patch. See the Reno Documentation for details on how to generate new release notes.
How To Contribute A Driver
How To Contribute A New Feature
The cinder.conf.sample is no longer maintained and tested in the source tree. Currently you can obtain a copy of a nightly generated conf file here: nightly_generated_conf_files
Note that the base cinder.conf.sample.txt (no time-stamp appended) is the current "good" generated conf for the previous milestone.