{"id":6081,"date":"2014-06-11T16:29:07","date_gmt":"2014-06-11T21:29:07","guid":{"rendered":"http:\/\/www.openstack.org\/blog\/?p=6081"},"modified":"2014-06-12T13:11:18","modified_gmt":"2014-06-12T18:11:18","slug":"openstack-technical-committee-update","status":"publish","type":"post","link":"https:\/\/www.openstack.org\/blog\/openstack-technical-committee-update\/","title":{"rendered":"OpenStack Technical Committee Update"},"content":{"rendered":"

The OpenStack Technical Committee (TC) meets weekly<\/a>. During the meeting on 2014-06-03, one of the topics we discussed was the relatively low turnout for the TC election as compared to the PTL elections. The most productive thing to come out of that discussion was that we needed to do a better job of communicating what the TC is working on and why it is important. As a result, we will be posting regular updates about the TC to the OpenStack blog. This first post will likely be a bit longer as it’s important to set up some of the context for the things we are currently discussing.<\/p>\n

How the TC was formed is described in the history of OpenStack open source project governance<\/a>\u00a0 by the current\u00a0chair of the TC, Thierry Carrez.<\/p>\n

Openness<\/h1>\n

Open governance is an important value held by OpenStack and the TC wants to be\u00a0as open as possible. In addition to these regular updates, you can find the\u00a0details of everything we do in a few other places. The archives of the openstack-tc mailing\u00a0list<\/a> are open. Our weekly IRC meetings are public and\u00a0logged<\/a>.<\/p>\n

All project governance work is managed in a\u00a0git repository<\/a>\u00a0and changes are reviewed in gerrit in the same way that we review code.\u00a0Everyone that is interested is invited to comment on proposed governance\u00a0changes. You can find a list of changes under review\u00a0here<\/a>.\u00a0You can find a list of previously approved changes and the discussions that\u00a0happened on their reviews\u00a0here<\/a>.<\/p>\n

Project Incubation and Graduation Requirements<\/h1>\n

One of the responsibilities of the TC is to manage the set of projects that are\u00a0included in the OpenStack integrated release. New projects may apply to be\u00a0incubated. Incubated projects will later be reviewed for graduation from\u00a0incubation. A graduated project is a part of the integrated release.<\/p>\n

As OpenStack has grown, it became clear that we needed to be much more clear\u00a0around our expectations of projects for incubation and graduation. Over the\u00a0last year we worked to formalize these expectations in a document in the\u00a0governance repository. We approved the first version of this document on\u00a0December 2, 2013. We have been updating it ever since as more issues need to be\u00a0clarified. You can find the latest version of that document in the Governance git repository<\/a>.<\/p>\n

Toward the end of the Icehouse development cycle, we started a process of going\u00a0through all projects already in the integrated release and evaluating them\u00a0against this criteria. For any project that has gaps against these\u00a0expectations, we require that the PTL present a plan for addressing these gaps\u00a0during the Juno cycle.<\/p>\n

Glance<\/h1>\n

The latest project review was for Glance, during the TC meeting on 2014-06-10.\u00a0The only\u00a0gap found for Glance was around tempest test coverage.\u00a0Specifically, Tempest does not cover uploading a real binary image to Glance.\u00a0The Glance PTL will now come up with a plan to address this gap and the TC\u00a0will review progress against this plan throughout the Juno cycle.<\/p>\n

We actually spent quite a bit of this meeting talking about Glance. The most\u00a0controversial topic is around the proposal to increase its scope. Glance is\u00a0currently focused on disk images. There is a proposal<\/a> against the governance\u00a0repository to expand its scope to cover a more general definition of artifacts.\u00a0The particular use cases that inspired this direction for Glance is the desire\u00a0to store things like Heat or Murano templates. In the end, there seems to be\u00a0broad support for the general direction proposed. We still have some work to do\u00a0to get the wording of the mission statement in a form that everyone is\u00a0comfortable with.<\/p>\n

Finally, the Glance project brought an important cross-project API consistency\u00a0question to the TC. Specifically, they have an alternative method for how they\u00a0would like to expose actions through their API which is different from how Nova\u00a0does it currently, for example. There was support for the specific proposal.\u00a0However, it raises the larger question about how we go about best working toward\u00a0cross project API consistency. We would love to have someone lead an effort to\u00a0create a cross-project API style guide for OpenStack, but it’s unclear who will\u00a0do it and exactly who would review and approve the content. I expect this to be\u00a0an ongoing discussion.<\/p>\n

You can find the full mailing list thread that spawned this API discussion in the archives starting in May<\/a> and continuing in June<\/a>.<\/p>\n

Designate<\/h1>\n

Another project that has received a lot of attention recently is Designate,\u00a0which provides DNS as a Service for OpenStack. This is a sorely needed feature\u00a0for OpenStack deployments so I’m very happy to see the progress made in this\u00a0area.<\/p>\n

The project recently\u00a0applied for incubation<\/a>. This is actually the second time that Designate has\u00a0applied for incubation. The\u00a0first time<\/a>\u00a0was one year ago, in June of 2013. After the first application, the TC\u00a0concluded that it was a bit too early to incubate the project. There were\u00a0various concerns, but the primary one was the level of involvement in the\u00a0project, in terms of individuals and separate companies.<\/p>\n

Designate has matured a good bit over the last year and I’m proud to announce that\u00a0the application has been approved. Designate is now an incubated project!<\/p>\n

The earliest Designate will be included in the integrated\u00a0release would be the K release. Given that we’re already well into the Juno\u00a0cycle, the L release seems more realistic. This is a topic that the TC would\u00a0revisit at the end of the Juno development cycle.<\/p>\n

Future Updates<\/h1>\n

We want to make these updates from the TC as useful as possible. If you have\u00a0any comments or suggestions, please let us know!<\/p>\n","protected":false},"excerpt":{"rendered":"

The OpenStack Technical Committee (TC) meets weekly. During the meeting on 2014-06-03, one of the topics we discussed was the relatively low turnout for the TC election as compared to the PTL elections. The most productive thing to come out of that discussion was that we needed to do a better job of communicating what… Read more »<\/a><\/p>\n","protected":false},"author":69,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[7,3,28],"tags":[500,209,516,501,499,377],"_links":{"self":[{"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/posts\/6081"}],"collection":[{"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/users\/69"}],"replies":[{"embeddable":true,"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/comments?post=6081"}],"version-history":[{"count":6,"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/posts\/6081\/revisions"}],"predecessor-version":[{"id":6091,"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/posts\/6081\/revisions\/6091"}],"wp:attachment":[{"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/media?parent=6081"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/categories?post=6081"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/tags?post=6081"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}