How To Contribute a driver to Cinder
Deadline for the Current Development Cycle
For clarification, a patch is considered a new driver when it's introducing a new protocol into the driver. For example, if your driver supports iSCSI, but your patch proposes support for FibreChannel, that's a new driver patch.
The deadline for new backend drivers, with working third party CI and no code review issues, is always posted on the current release schedule. (Take the link for the "Series" name, and a link to the release schedule will be at the top of the page.)
Third Party CI Requirement Policy
See third party CI wiki.
For people working on getting their CI to handle Python 3, see Cinder Third Party CI update to Python 3.7
Before you write any code
- Read the How To Contribute Page.
- Read the Cinder wiki page.
- Understand how Cinder works, what it's used for, why the other projects in OpenStack may or may not use it. Fully understand the difference between ephemeral storage on the Nova side versus the persistent storage offered by Cinder
- Cinder offers a reference implementation that should be used as a model. The reference implementation driver file is cinder/volume/drivers/lvm.py, not to be mistaken for cinder/volume/driver.py which is the base class that all of the drivers inherit from. Note that there are a lot of options that show up there regarding iSCSI targets etc, but this gives you an idea of the expectations in terms of features that are implemented and some of the behaviors. I strongly recommend loading up devstack (you're going to need it to test your driver anyway) and play around with the default LVM. It's really important that you get a feel for how Cinder works and interacts with the other OpenStack projects before you get too far along.
- You don't need a cinder spec for most drivers. You always need to submit a blueprint in Launchpad introducing your driver, so that it can be targeted for a release.
- We have a development channel on freenode: #openstack-cinder. There are developers here round the clock, it's a great resource for you get started. Log in, ask questions, don't stare at code in isolation for a week... if you're stuck on something just ask. There's also no need to start off with "Can I ask a question"... you likely won't get a response. Just type in your question, that way anybody monitoring the channel that might know the answer can step in and answer.
- You must implement all of the methods that exist as core features.
- Your driver should not make any state changes. (e.g. make Cinder database calls). The volume manager is responsible for making state changes after the driver is done talking to the storage backend. Your driver should try not to read from database if possible.
- Unit tests for new code are required.
- Make sure you're not duplicating a configuration option that already exists. To verify this, you'll need to need look at the cinder/etc/cinder.conf.sample file.
- Every effort should be made to reuse common config options before introducing driver-specific ones.
- If options are added, you will need to run "tox -e genopts" to update the opts.py file that is used to generate our configuration references.
- Make sure to follow the OpenStack Style Guide. Very likely you'll get nit pick reviews otherwise, which is not productive either way.
- Cinder's manager layer will log useful information like failures from the driver that are raised. However, you're more than welcome to add additional logging, but please follow our logging guideline. Use log markers by importing cinder.i18n so that log translations can be made.
Submitting Driver For Review
When submitting your driver, please include a release note along with your patch. See the Reno Documentation for details on how to generate new release notes.
The release note should be something along the lines of:
--- features: - Added backend driver for vendor storage.
- All new code should also be Python 3.7 compatible. Unit tests will be run with both python 2.7 and python 3.7, but additional runtime testing should be performed. Check the supported runtimes for the current cycle.
- Do NOT bother the Cinder team for reviews. We are aware of your patch being posted.
- Make sure your commit message follows the OpenStack project guidelines.
- Make sure your driver has appropriate third party testing done. It is required that your CI posts the necessary tests pass. Since your driver is not yet merged, follow instructions to have you unmerged driver properly tested.
- Documentation is now kept in the openstack/cinder repo. At a minimum, please add a basic description of your driver and its configuration options under the volume driver section of the Configuration reference.
After Your Driver Is Added
Congratulations! You're not done yet though. After your driver has been merged there are still some things that need to be done.
- Make sure there is documentation for your driver
- Add a liaison name to https://wiki.openstack.org/wiki/Documentation/VendorDrivers after reading this spec
- Refer to Documentation Contributor Guide on how to contribute.
- Continue to be available on IRC and attend the weekly meetings in case questions come up.
- Subscribe to receive bugs for your driver! The Cinder team will be triaging bugs and will tag bugs with the name of your company that are related to your driver. To subscribe:
- Go to https://bugs.launchpad.net/openstack/cinder/+bug
- Click 'Subscribe to bug mail'
- Click the radio button "are added and changed in any way"
- Click checkbox 'Bugs must match this filter (...)"
- Click tags
- With "match all tags" selected type in the field the name of your company.