Jump to: navigation, search


The OpenStack Technical Committee is one of the governing bodies of the OpenStack project. You can find more information about it, such as the list of its current members or its governance charter, on the OpenStack TC governance website at https://governance.openstack.org/tc/ . It meets weekly in an open meeting in the #openstack-meeting IRC channel on Freenode. See the governance website for details on how to propose governance changes.

Current proposals

Status last updated: May 26, 2017


  • Technical Committee vision [1] (gothicmindfood, johnthetubaguy, cdent, dtroyer)
  • Introduce assert:supports-api-interoperability tag [2] (mtreinish, sdague)
    • Status: Needs another patchset
    • Next step: mtreinish to address dhellmann's comments
  • Describe what upstream support means [3] (johnthetubaguy)
    • Status: New revision needed
    • Next step: johnthetubaguy to update it next week-ish
  • Introduce Top 5 help wanted list [4] (ttx, dims)
    • Status: Should propose a follow-up patch to frame the discussion
    • Next step: ttx to post one example follow-up patch
  • Etcd as a base service [5] (dims)
    • Status: Majority reached on May 26. To be approved on May 31

New project teams

  • Add Stackube project team [6] (dims, ttx)
    • Status: Frozen until the project is set up as a hosted project and openly collaborates there for some time
    • Next step: Setting up openstack/stackube as an OpenStack-hosted project (dims to mentor them through the steps)
  • Add Gluon project team [7] (?)
    • Status: Frozen while Gluon discusses further integration opportunities with Neutron
    • Next step: This prospective team needs a TC sponsor/mentor to help them through the steps. Any volunteer ?


  • postgresql support in OpenStack -- two alternative solutions:
  • Culling projects that are not going anywhere (ttx, ?)
    • Status: brainstorming

Inclusion & Diversity

  • How to propose changes: do not mention meetings [10] (ttx)
    • Status: Majority reached on May 29. To be approved on Jun 1st
  • Decisions should be globally inclusive [11] (johnthetubaguy)
    • Status: New revision needed
    • Next step: johnthetubaguy to update it
  • Document voting process for `formal-vote` patches [12] (flaper87)
    • Status: 2/3 majority reached on May 29. To be approved on Jun 1st
  • Drop Technical Committee meetings [13] (flaper87)
    • Status: New revision needed
    • Next step: flaper87 to update it
  • Office hours -- two patches:
    • Introduce office hours [14] (ttx)
    • Establish a #openstack-tc water cooler channel [15] (dims)
    • Status: Voting in progress
  • Workgroups should not be UC or TC-side, should always be both (mrhillsman, ttx)
    • Status: brainstorming


  • Add etherpad link with detailed steps to split-tempest-plugins goal [16]
    • Status: Just further documentation for the split-tempest-plugins goal. Voting in progress.
  • Queens goal: discovery alignment (two options):
    • Add Queens goal to add collection links [17]
    • Add Queens Goal for full discovery alignment [18]
    • Status: Needs a ML thread
    • Next step: mordred to raise a ML thread about those two options


  • Support "Driver teams" [19] [20] [21] [22] (dhellmann)
    • Status: Frozen while thingee works on driver discoverability
  • networking-cisco project team addition [23] (thingee)
    • Status: Blocked until driver teams are a thing
    • Next step: thingee to reach out to networking-cisco folks to check how much discoverability solves their issue
  • Policy on binary images publication (dhellmann)

Next Meeting

  • Date: June 6th
  • Chair: tbd


  • Declare the current state of Postgresql in OpenStack
    • Declare plainly the current state of Posgresql in OpenStack [24]
    • Document lack of postgresql support [25]
  • Open discussion

Apologies for Absence

  • tbd

Past meetings logs

Logs of past TC meetings can be accessed at: http://eavesdrop.openstack.org/meetings/tc