I did research about OpenStack that I covered in: A Guide to Developer Contributions in the OpenStack Juno Blueprints. In this episode of The New Stack Analysts podcast, I presented with Alex Williams and co-hosts Donnie Berkholz of RedMonk and Michael Cote of 451 Research about the research I did. For more episodes of The New Stack Analysts, check out the podcast section of The New Stack.
- OpenStack blueprints are used to track the implementation of significant features in OpenStack.
- The New Stack tracked the 11 integrated projects of the OpenStack Juno release.
- Every feature added to a project is equally significant. Incubated projects have to follow a lifecycle before getting considered as an integrated project. Priority of a blueprint is the value added it brings to the project.
- The Compute project has many new features added along with the addition of proprietary drivers by third party vendors.
- Priority of a blueprint is decided by the developers who are committed to that particular project.
- Glance has few blueprints implemented. One reason: the project is relatively mature.
- Storage policy seems to be one common feature added to most of these project.
- The OpenStack dashboard has a relative larger number of features added. That is in part due to the integration of the Sahara project, which aims to bring data intensive application cluster on top of OpenStack.
- Complete workflow and requirements for a project to be part of OpenStack is provided here.
- OpenStack Neutron blueprint has considerable activity. One of the main reason: networking vendors are adding their driver to the Neutron Core. Neutron brings network as a service to OpenStack. Project details can be found here
- Smaller companies are also making their presence felt in overall OpenStack project like B1 Systems and Torsera.
- OpenStack releases post Havana are in end of life and carrier providers are asking for some kind of long term release. The release cycle of OpenStack project can be found here