{"id":6331,"date":"2014-07-14T11:24:06","date_gmt":"2014-07-14T16:24:06","guid":{"rendered":"http:\/\/www.openstack.org\/blog\/?p=6331"},"modified":"2014-07-14T11:24:06","modified_gmt":"2014-07-14T16:24:06","slug":"defcore-update-input-request-for-havana-capabilities","status":"publish","type":"post","link":"https:\/\/www.openstack.org\/blog\/defcore-update-input-request-for-havana-capabilities\/","title":{"rendered":"DefCore Update: Input Request for Havana Capabilities"},"content":{"rendered":"<p class=\"lead\">As part of our community&#8217;s commitment to interoperability, the OpenStack Board of Directors has been working to make sure that &#8220;downstream&#8221; OpenStack-branded commercial products offer the same baseline functionality and include the same upstream, community-developed code. The work to define these required core capabilities and code has been led by the DefCore Committee co-chaired by Rob Hirschfeld (<a href=\"http:\/\/robhirschfeld.com\/?s=defcore&amp;submit=Search\">his DefCore blog<\/a>) and Joshua McKenty (<a href=\"http:\/\/www.pistoncloud.com\/2014\/05\/openstack-defcore-review-time\/\">his post<\/a>). \u00a0You can read more about the committee history and rationale in Mark Collier&#8217;s <a href=\"http:\/\/www.openstack.org\/blog\/2014\/01\/openstack-commitment-to-interoperability\/\">blog post<\/a>.<\/p>\n<p>The <a href=\"https:\/\/wiki.openstack.org\/wiki\/Governance\/DefCoreCommittee\">DefCore Committee<\/a> has introduced two key concepts that will be used to define the standard requirements across commercial products: <a href=\"https:\/\/wiki.openstack.org\/wiki\/Governance\/CoreCriteria\">Capabilities<\/a> and Designated Sections. Capabilities represent the functionality that is exposed by an OpenStack-based cloud through APIs, which can be tested and reported on\u2014for instance starting or stopping a virtual server. Designated sections are portions of upstream code from various OpenStack projects that are required in addition to the API-based capabilities. These requirements can change with each OpenStack release, and the DefCore committee has started with the Havana release to create an &#8220;advisory&#8221; set of requirements. \u00a0After community review on Havana, the Board will repeat the process for Icehouse requirements and then enforce those for the commercial trademark license programs.<\/p>\n<p><b>Get Involved<\/b>: Next week, the DefCore Committee will host two meetings for community input on the Capabilities they&#8217;ve scoped for the Havana release. The meetings will take place Wednesday, July 16, at 8 am PDT (1500 UTC) and 6 pm PDT (0100 UTC on July 17) to accommodate as many time zones as possible. You can reference the DefCore Committee&#8217;s <a href=\"https:\/\/docs.google.com\/spreadsheet\/ccc?key=0Av62KoL8f9kAdFo4V1ZLUFM0OHlrRnFpQUkxSHJ5QWc&amp;usp=drive_web#gid=6\">current proposal<\/a>, and join the meetings using the links on the following page:<\/p>\n<ul>\n<li>July 16, 8 am PDT\/1500 UTC: <a href=\"https:\/\/etherpad.openstack.org\/p\/DefCoreLighthouse.4\">https:\/\/etherpad.openstack.org\/p\/DefCoreLighthouse.4<\/a><\/li>\n<li>July 16, 6 pm PDT\/0100 UTC July 17: <a href=\"https:\/\/etherpad.openstack.org\/p\/DefCoreLighthouse.4\">https:\/\/etherpad.openstack.org\/p\/DefCoreLighthouse.4<\/a><\/li>\n<li>OSCON on July 21, 11:30 am PDT: <a href=\"http:\/\/www.oscon.com\/oscon2014\/public\/schedule\/detail\/37014\">http:\/\/www.oscon.com\/oscon2014\/public\/schedule\/detail\/37014<\/a><\/li>\n<\/ul>\n<p>After getting community input, the DefCore Committee plans to bring the proposed Havana Capabilities to the Board for approval at the next face-to-face meeting, taking place July 22nd in Portland, OR. \u00a0If approved, focus will then shift to the Designated Sections for Havana.<\/p>\n<p>If you&#8217;d like to catch up on the work the Committee has been doing since the OpenStack Summit Atlanta, the following links contain the notes from their recent meetings:<\/p>\n<p><a href=\"https:\/\/etherpad.openstack.org\/p\/DefCoreLighthouse.1\">https:\/\/etherpad.openstack.org\/p\/DefCoreLighthouse.1<br \/>\n<\/a><a href=\"https:\/\/etherpad.openstack.org\/p\/DefCoreLighthouse.2\">https:\/\/etherpad.openstack.org\/p\/DefCoreLighthouse.2<br \/>\n<\/a><a href=\"https:\/\/etherpad.openstack.org\/p\/DefCoreLighthouse.F2F\">https:\/\/etherpad.openstack.org\/p\/DefCoreLighthouse.F2F<br \/>\n<\/a><a href=\"https:\/\/etherpad.openstack.org\/p\/DefCoreLighthouse.3\">https:\/\/etherpad.openstack.org\/p\/DefCoreLighthouse.3<\/a><\/p>\n<p>&nbsp;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>As part of our community&#8217;s commitment to interoperability, the OpenStack Board of Directors has been working to make sure that &#8220;downstream&#8221; OpenStack-branded commercial products offer the same baseline functionality and include the same upstream, community-developed code. The work to define these required core capabilities and code has been led by the DefCore Committee co-chaired by&#8230;  <a href=\"https:\/\/www.openstack.org\/blog\/defcore-update-input-request-for-havana-capabilities\/\" class=\"more-link\" title=\"Read DefCore Update: Input Request for Havana Capabilities\">Read more &raquo;<\/a><\/p>\n","protected":false},"author":41,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[3,1],"tags":[],"_links":{"self":[{"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/posts\/6331"}],"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\/41"}],"replies":[{"embeddable":true,"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/comments?post=6331"}],"version-history":[{"count":4,"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/posts\/6331\/revisions"}],"predecessor-version":[{"id":6335,"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/posts\/6331\/revisions\/6335"}],"wp:attachment":[{"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/media?parent=6331"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/categories?post=6331"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/tags?post=6331"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}