{"id":6351,"date":"2014-07-18T14:56:31","date_gmt":"2014-07-18T19:56:31","guid":{"rendered":"http:\/\/www.openstack.org\/blog\/?p=6351"},"modified":"2014-07-18T14:56:31","modified_gmt":"2014-07-18T19:56:31","slug":"openstack-community-weekly-newsletter-july-11-18","status":"publish","type":"post","link":"https:\/\/www.openstack.org\/blog\/openstack-community-weekly-newsletter-july-11-18\/","title":{"rendered":"OpenStack Community Weekly Newsletter (July 11 – 18)"},"content":{"rendered":"

DefCore Update: Input Request for Havana Capabilities<\/span><\/a><\/h3>\n

As part of our community\u2019s commitment to interoperability, the OpenStack Board of Directors has been working to make sure that \u201cdownstream\u201d 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 (his DefCore blog<\/a>) and Joshua McKenty (his post<\/a>). You can read more about the committee history and rationale in Mark Collier\u2019s blog post<\/a>. <\/span>The next deadlines are: OSCON on July 21, 11:30 am PDT<\/a> and the Board Meeting on July 22<\/span>nd<\/span>.<\/span><\/p>\n

And the K cycle will be named… Kilo !<\/span><\/a><\/h3>\n

The results of the poll are just in, and the winner proposal is “Kilo”. “k” is the unit symbol for “kilo”, a SI unit prefix (derived from the Greek word \u03c7\u03af\u03bb\u03b9\u03bf\u03b9 which means “thousand”). “Kilo” is often used as a shorthand for “kilogram”, and the kilogram is the last SI base unit to be tied to a reference artifact (stored near Paris in the Pavillon de Breteuil in S\u00e8vres).<\/p>\n

Five Days + Twelve Writers + One Book Sprint = One Excellent Book on OpenStack Architecture<\/span><\/a><\/h3>\n

A<\/span> dozen OpenStack experts and writers from companies across the OpenStack ecosystem gathered at VMware\u2019s Palo Alto campus for the OpenStack Architecture Design Guide book sprint. The intent was to deliver a completed book <\/span>aimed architects and evaluators, <\/span>on designing OpenStack clouds \u2014 in just five days.<\/span><\/p>\n

Only developers should file specifications and blueprints<\/span><\/a><\/h3>\n

If you try to solve a problem with the wrong tool you\u2019re likely going to have a frustrating experience. OpenStack <\/span>developers<\/span> use blueprints define the roadmap for the various projects, the specifications attached to a blueprint are used to discuss the implementation details before code is submitted for review.<\/span> Operators and users in general don\u2019t need to dive in the details of how OpenStack developers organize their work and definitely should never be asked to use tools designed for and by developers.<\/p>\n

Third Party CI group formation and minutes<\/h3>\n

At this week’s meeting the Third-Party group continues to discuss documentation patches, including a new terminology proposal, as well as CI system naming, logging and test timing. There was also a summary review of the current state of Neutron driver CI rollout. Anyone deploying a third-party test system or interested in easing third-party involvement is welcome to attend the meetings. <\/span>Minutes of <\/span>ThirdPart<\/span>y meetings<\/span><\/a> are carefully logged.<\/span><\/p>\n

The Road To Paris 2014 \u2013 Deadlines and Resources<\/h2>\n