Jump to: navigation, search

Difference between revisions of "ProductTeam/MultiRelease Roadmap"

m (Next Roadmap Presentation: [http://sched.co/49w1 OpenStack Summit in Tokyo [Thursday, October 29th, 2015 at 2:40PM JST]])
(Tracked OpenStack Projects and Status)
 
(5 intermediate revisions by 2 users not shown)
Line 3: Line 3:
 
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.
 
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.
  
==== <b>Next Roadmap Presentation: TBD, potentially Austin Summit in April 2016</b> ====
+
==== <b>Next Roadmap Presentation: OpenStack Summit in Austin (April 26th, 2016)</b> ====
 +
Session details can be found on the [https://www.openstack.org/summit/austin-2016/summit-schedule/events/9029 OpenStack Summit Schedule]
  
 
=== Disclaimer ===
 
=== Disclaimer ===
Line 11: Line 12:
  
 
=== Previous Roadmap Presentations ===
 
=== Previous Roadmap Presentations ===
October 2015 (Liberty release; Mitaka Design Summit): http://www.openstack.org/assets/tokyo-summit/OpenStack-Roadmap-Mitaka-Update.pptx
+
October 2015 (Liberty release; Mitaka Design Summit): [http://www.openstack.org/assets/tokyo-summit/OpenStack-Roadmap-Mitaka-Update.pptx OpenStack Community Generated Roadmap]
May 2015 (Kilo release; Liberty Design Summit): [http://www.slideshare.net/ShamailXD/a-glimpse-at-the-roadmap-deck-v5-final SlideShare]
+
<br>May 2015 (Kilo release; Liberty Design Summit): [http://www.slideshare.net/ShamailXD/a-glimpse-at-the-roadmap-deck-v5-final SlideShare]
  
Note: Future versions of the roadmap presentation will be stored at [https://www.openstack.org/roadmap]
+
Note: Future versions of the roadmap presentation will be stored at [[https://www.openstack.org/roadmap OpenStack.org Roadmap Page]]
  
 
=== Methodology ===
 
=== Methodology ===
Line 33: Line 34:
 
! Project !! Liaison !! Status !! Additional Comments
 
! Project !! Liaison !! Status !! Additional Comments
 
|-
 
|-
| Nova|| Hugh B.*|| Updated at Liberty FF||  
+
| Nova|| Hugh B.*|| Updated at [http://releases.openstack.org/mitaka/schedule.html Mitaka Release]||  
 
|-
 
|-
| Neutron|| Mike C.*|| Updated at Liberty FF||  
+
| Neutron|| Duane D.*|| Updated at [http://releases.openstack.org/mitaka/schedule.html Mitaka Release]||  
 
|-
 
|-
| Cinder|| Shamail T.*|| Updated at Liberty FF||  
+
| Cinder|| Shamail T.*|| Updated at [http://releases.openstack.org/mitaka/schedule.html Mitaka Release]||  
 
|-
 
|-
| Glance|| Nate Z.*|| Updated at Liberty FF||  
+
| Glance|| Nate Z.*|| Updated at [http://releases.openstack.org/mitaka/schedule.html Mitaka Release]||  
 
|-
 
|-
| Keystone|| Sheena G.*|| Updated at Liberty FF||  
+
| Keystone|| Megan R.*|| Updated at [http://releases.openstack.org/mitaka/schedule.html Mitaka Release]||  
 
|-
 
|-
| Heat|| Kenny J.|| Awaiting update for Liberty FF||  
+
| Heat|| Kenny J.|| Updated at [http://releases.openstack.org/mitaka/schedule.html Mitaka Release]||  
 
|-
 
|-
| Swift|| Phil W.*|| Partially updated at Liberty FF||Need data for M+N
+
| Swift|| Phil W.*|| Updated at [http://releases.openstack.org/mitaka/schedule.html Mitaka Release]||  
 
|-
 
|-
| Trove|| Leong S.|| Awaiting update for Liberty FF||  
+
| Trove|| Anni L.|| Updated at [http://releases.openstack.org/mitaka/schedule.html Mitaka Release]||  
 
|-
 
|-
| Ceilometer|| Krish R.|| Updated at Liberty FF||  
+
| Telemetry|| Krish R.|| Updated at [http://releases.openstack.org/mitaka/schedule.html Mitaka Release]||  
 
|-
 
|-
| Horizon|| Carol B.*|| Updated at Liberty FF||  
+
| Horizon|| Carol B.*|| Updated at [http://releases.openstack.org/mitaka/schedule.html Mitaka Release]||  
 
|-
 
|-
| Ironic|| Shamail T.|| Updated at Liberty FF||  
+
| Ironic|| Hugh B.|| Updated at [http://releases.openstack.org/mitaka/schedule.html Mitaka Release]||  
 
|-
 
|-
| Triple O|| Carol B.|| Updated at Liberty FF||  
+
| Triple O|| Leong|| Updated at [http://releases.openstack.org/mitaka/schedule.html Mitaka Release]||  
 
|-
 
|-
| Sahara|| Shamail T.|| Data Received for Liberty FF||  
+
| Sahara|| Carol B.|| Updated at [http://releases.openstack.org/mitaka/schedule.html Mitaka Release]||  
 
|-
 
|-
| Manila|| Pete C.*|| Awaiting update for Liberty FF||  
+
| Manila|| Pete C.*|| Updated at [http://releases.openstack.org/mitaka/schedule.html Mitaka Release]||  
 
|-
 
|-
| Oslo|| Sheena G.|| Updated at Liberty FF||  
+
| Oslo|| Rocky G.|| Updated at [http://releases.openstack.org/mitaka/schedule.html Mitaka Release]||  
 
|-
 
|-
| OSClient|| Carol B.|| Awaiting update for Liberty FF||  
+
| OSClient|| Megan R.|| Updated at [http://releases.openstack.org/mitaka/schedule.html Mitaka Release]||  
 
|-
 
|-
| Magnum|| Mike C.*|| Updated at Liberty FF||  
+
| Magnum|| Steve G.*|| Updated at [http://releases.openstack.org/mitaka/schedule.html Mitaka Release]||  
 
|-
 
|-
| Kolla|| Carol B.*|| Updated at Liberty FF||  
+
| Kolla|| Carol B.*|| Updated at [http://releases.openstack.org/mitaka/schedule.html Mitaka Release]||  
 
|-
 
|-
| Designate|| Kenny J.|| Awaiting update for Liberty FF||  
+
| Designate|| Kenny J.|| Updated at [http://releases.openstack.org/mitaka/schedule.html Mitaka Release]||  
 
|-
 
|-
| Kuryr|| Shamail T.|| Updated at Liberty FF||
+
| Kuryr|| Shamail T.|| Updated at [http://releases.openstack.org/mitaka/schedule.html Mitaka Release]||
 +
|-
 +
| Rally|| Arkady K.|| Updated at [http://releases.openstack.org/mitaka/schedule.html Mitaka Release]||
 +
|-
 +
| QA || Arkady K.|| Updated at [http://releases.openstack.org/mitaka/schedule.html Mitaka Release]||
 +
|-
 +
| Barbican || Mark B.|| Updated at [http://releases.openstack.org/mitaka/schedule.html Mitaka Release]||
 +
|-
 +
| Murano || Carol B.|| Updated at [http://releases.openstack.org/mitaka/schedule.html Mitaka Release]||
 +
|-
 +
| Docs || Hugh B.|| Updated at [http://releases.openstack.org/mitaka/schedule.html Mitaka Release]||
 +
|-
 +
| RefStack || Rocky G.|| Updated at [http://releases.openstack.org/mitaka/schedule.html Mitaka Release]||
 +
|-
 +
| Stable Release || Rocky G.|| Updated at [http://releases.openstack.org/mitaka/schedule.html Mitaka Release]||
 +
|-
 +
| OS Ansible || Kenny J.|| Updated at [http://releases.openstack.org/mitaka/schedule.html Mitaka Release]||
 
|}
 
|}
  
 
Contact Information
 
Contact Information
 
The best way to contact the roadmap sub-team is to post on the [http://lists.openstack.org/cgi-bin/mailman/listinfo/product-wg Product Working Group Mailing List] and add "[roadmap]" to your subject line.
 
The best way to contact the roadmap sub-team is to post on the [http://lists.openstack.org/cgi-bin/mailman/listinfo/product-wg Product Working Group Mailing List] and add "[roadmap]" to your subject line.

Latest revision as of 05:48, 20 April 2016

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 Austin (April 26th, 2016)

Session details can be found on the OpenStack Summit Schedule

Disclaimer

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

October 2015 (Liberty release; Mitaka Design Summit): OpenStack Community Generated Roadmap
May 2015 (Kilo release; Liberty Design Summit): SlideShare

Note: Future versions of the roadmap presentation will be stored at [OpenStack.org Roadmap Page]

Methodology

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.

Roadmap Refresh Milestones

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.

Project Liaison Status Additional Comments
Nova Hugh B.* Updated at Mitaka Release
Neutron Duane D.* Updated at Mitaka Release
Cinder Shamail T.* Updated at Mitaka Release
Glance Nate Z.* Updated at Mitaka Release
Keystone Megan R.* Updated at Mitaka Release
Heat Kenny J. Updated at Mitaka Release
Swift Phil W.* Updated at Mitaka Release
Trove Anni L. Updated at Mitaka Release
Telemetry Krish R. Updated at Mitaka Release
Horizon Carol B.* Updated at Mitaka Release
Ironic Hugh B. Updated at Mitaka Release
Triple O Leong Updated at Mitaka Release
Sahara Carol B. Updated at Mitaka Release
Manila Pete C.* Updated at Mitaka Release
Oslo Rocky G. Updated at Mitaka Release
OSClient Megan R. Updated at Mitaka Release
Magnum Steve G.* Updated at Mitaka Release
Kolla Carol B.* Updated at Mitaka Release
Designate Kenny J. Updated at Mitaka Release
Kuryr Shamail T. Updated at Mitaka Release
Rally Arkady K. Updated at Mitaka Release
QA Arkady K. Updated at Mitaka Release
Barbican Mark B. Updated at Mitaka Release
Murano Carol B. Updated at Mitaka Release
Docs Hugh B. Updated at Mitaka Release
RefStack Rocky G. Updated at Mitaka Release
Stable Release Rocky G. Updated at Mitaka Release
OS Ansible Kenny J. Updated at Mitaka Release

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.