Note: The wiki.openstack.org pages are for development team collaboration and documentation. If you are looking for official project documentation, please go to https://docs.openstack.org/cinder/latest/.
Official Title: OpenStack Block Storage Cinder
PTL: Brian Rosmaita <rosmaita daht fossdev 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.
- 1 Description
- 2 Documentation
- 3 Core Team
- 4 Project Meetings
- 5 Getting in Touch
- 6 Related projects
- 7 Core Volume Drivers
- 8 Contributing Code
- 9 Sample cinder.conf
- 10 Resources
Cinder is a Block Storage service for OpenStack. It's designed to present storage resources to end users that can be consumed by the OpenStack Compute Project (Nova). This is done through the use of either a reference implementation (LVM) or plugin drivers for other storage. The short description of Cinder is that it virtualizes the management 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]".
- Mailing list archive: http://lists.openstack.org/pipermail/openstack-discuss/
- For discussions prior to Mon Nov 19 00:04:26 UTC 2018, see the old "dev list" archive: http://lists.openstack.org/pipermail/openstack-dev/
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://docs.openstack.org/cinder/latest/reference/support-matrix.html
For any new features, significant code changes, new drivers, or major bug fixes, please add a release note along with your patch. See the Reno Documentation for details on how to generate new release notes.
How To Contribute A Driver
NOTE: For people working on getting their CI to handle Python 3, see Cinder Third Party CI update to Python 3.7
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 by running the command 'tox -e genconfig' in a cloned version of the Cinder project and then look in etc/cinder/ for the cinder.conf.sample file.
The newly generated file will have all options in the Cinder project, driver options included.
Additionally, the generated file is available in the Cinder documentation: https://docs.openstack.org/cinder/latest/configuration/block-storage/samples/cinder.conf.html
- Cinder/Nova API Changes
- Newton Midcycle
- Newton Summit Ideas
- Mitaka Final Push
- Mitaka Spec Review Tracking
- Mitaka Midcycle Meetup- Planning
- Mitaka Summit- Planning
- Liberty Midcycle Meetup- Notes
- Liberty Midcycle Meetup- Planning
- Cinder Priority Reviews Dashboard
- Cinder Projects Review Inbox
- In progress bugs
- New bugs
- Stable Branches Reviews
PTG and Summit Meeting Summaries
- Victoria PTG Summary
- Ussuri Mid-Cycle Summary
- Ussuri PTG Summary
- Train Mid-Cycle Summary
- Train Summit and PTG Summary
- Stein Mid-Cycle Summary
- Stein PTG Summary
- Vancouver Summit 2018 Summary
- Rocky PTG Summary
- Queens PTG Summary
- Pike PTG Summary