Ask Your Question

What's the best way to develop drivers for inclusion in official OpenStack releases?

asked 2013-09-25 01:05:46 -0500

wenimble gravatar image

updated 2013-09-26 17:56:28 -0500

smaffulli gravatar image

We have finished developing our Cinder driver for Grizzly release. Is it possible to release/support it by supplying the binary async from the release? Is it possible to check it into a maintenance release of Grizzly?

We are working to enhance it to add addt'l functionality in Havanna, but we have customers wanting to use what we have for Grizzly. Just want to understand what release options are available.

edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted

answered 2013-09-26 17:54:17 -0500

smaffulli gravatar image

The stable-maint team manages the stable branch for OpenStack core projects with the support of the core developers of those projects and the release team. From

the stable branch is intended to be a safe source of fixes for high impact bugs and security issues which have been fixed on master since a given release.

So releasing new features in the stable branch would not be a good thing. You can definitely provide your plugin to your customers outside of the main OpenStack trunk and keep it in sync with the stable branch. I would suggest you to work early in the release cycle with the Cinder PTL to include the driver in the next release.

edit flag offensive delete link more

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower


Asked: 2013-09-25 01:05:46 -0500

Seen: 135 times

Last updated: Sep 26 '13