Multi-Release Roadmap Sub-Team
The Product Working Group, in partnership with the OpenStack Foundation, is building a multi-release directional view of the OpenStack cloud platform by collecting (and aggregating) feedback from multiple PTLs (Project Team Leads). The roadmap covers 20 projects as of the Mitaka release but this list will continue to expand over time. This wiki page will maintain a link to previous versions of the roadmap, team member information, explanation of the various "views" shown in the roadmap slides, and status for the upcoming roadmap refresh/release.
Next Roadmap Presentation: OpenStack Summit in Tokyo [Thursday, October 29th, 2015 at 2:40PM JST]
The information presented in the "roadmap slides" for information only. It is the authors’ interpretation of information collected and does not represent commitments for features or timelines by the projects or PTLs.
As with any open-source project, items proposed by the team can be impacted by number of developers, hurdles, external forces, and change in direction… All decisions for the accepted blueprints/specs will ultimately be at the discretion of the project core teams. We can merely show a snapshot of a point-in-time in the projects’ evolution and the actual “delivery” of items may shift after that point-in-time. We will try our best to keep this snapshot updated.
Previous Roadmap Presentations
May 2015 (Kilo release; Liberty Design Summit): SlideShare
Note: Future versions of the roadmap presentation will be stored at openstack.org
The roadmap refresh team uses a questionnaire to collect feedback from the PTLs about the state of their projects. The roadmap refresh team engages with the developer community twice during a release cycle to refresh our understanding of current/future release plans after key release cycle milestones. The first questionnaire is sent out approximately 2-3 weeks after the design summit for the upcoming release and the primary focus of this engagement is to go back and update our understanding of what used to be the future release as it becomes the upcoming release. The second questionnaire is sent out after feature freeze for the current release cycle and we use this time to refresh our understanding of what actually made it into the upcoming release along with start building a view for the next couple of releases.
Product WG Cross-Project Liaisons
The roadmap team consists of the Product WG cross project liaisons (CPL) and additional team members. If a project already has a CPL then that is the person who works with the project team to refresh the questionnaire data. If a project does not have an assigned Product WG CPL then one of the roadmap team members will contact the PTL.
More information can be found on the Product WG Cross-Project Liaisons on this page.
Tracked OpenStack Projects and Status
The "Liaison" column denotes a CPL if there is an asterisk next to the persons' name, otherwise the person is only helping with the collection of the roadmap data and is not the CPL.
|Nova||Hugh B.*||Updated at Liberty FF|
|Neutron||Mike C.*||Updated at Liberty FF|
|Cinder||Shamail T.*||Updated at Liberty FF|
|Glance||Nate Z.*||Updated at Liberty FF|
|Keystone||Sheena G.*||Updated at Liberty FF|
|Heat||Kenny J.||Awaiting update for Liberty FF|
|Swift||Phil W.*||Partially updated at Liberty FF||Need data for M+N|
|Trove||Leong S.||Awaiting update for Liberty FF|
|Ceilometer||Krish R.||Updated at Liberty FF|
|Horizon||Carol B.*||Updated at Liberty FF|
|Ironic||Shamail T.||Updated at Liberty FF|
|Triple O||Carol B.||Updated at Liberty FF|
|Sahara||Shamail T.||Data Received for Liberty FF|
|Manila||Pete C.*||Awaiting update for Liberty FF|
|Oslo||Sheena G.*||Updated at Liberty FF|
|OSClient||Carol B.||Awaiting update for Liberty FF|
|Magnum||Mike C.*||Updated at Liberty FF|
|Kolla||Carol B.*||Updated at Liberty FF|
|Designate||Kenny J.||Awaiting update for Liberty FF|
|Kuryr||Shamail T.||Updated at Liberty FF|
Contact Information The best way to contact the roadmap sub-team is to post on the Product Working Group Mailing List and add "[roadmap]" to your subject line.