{"id":7634,"date":"2016-02-13T02:46:47","date_gmt":"2016-02-13T08:46:47","guid":{"rendered":"http:\/\/www.openstack.org\/blog\/?p=7634"},"modified":"2016-02-13T02:46:47","modified_gmt":"2016-02-13T08:46:47","slug":"openstack-developer-mailing-list-digest-20160212","status":"publish","type":"post","link":"https:\/\/www.openstack.org\/blog\/openstack-developer-mailing-list-digest-20160212\/","title":{"rendered":"OpenStack Developer Mailing List Digest Feb 7-12"},"content":{"rendered":"<h1>SuccessBot Says<\/h1>\n<ul>\n<li>dhellmann: [1] is live with release history and upcoming release schedules.<\/li>\n<li>ttx:\u00a0 Governance changes are now announced in #openstack-dev, to increase general awareness about them!<\/li>\n<li>jklare: Just merged the first batch of opentack-chef cookbook patches for the Mitaka cycle! 4.229 lines of code refactored and 18.678 lines removed!<\/li>\n<li>johnthetubaguy: Nova subteams starting to look after themselves, and effectively reporting their progress to the wider community<\/li>\n<li>All: <a href=\"https:\/\/wiki.openstack.org\/wiki\/Successes\">https:\/\/wiki.openstack.org\/wiki\/Successes<\/a><\/li>\n<\/ul>\n<h1>Dropping KEYSTONE_CATALOG_BACKEND &#8211; Plus Update Your Devstack Plugins<\/h1>\n<ul>\n<li>Devstack has some half baked support for Keystone templated service catalog.<\/li>\n<li>In an effort to clean up parts of Devstack, we&#8217;re dropping that [2].<\/li>\n<li>This breaks everyone&#8217;s Devstack plugin that references the KEYSTONE_CATALOG_BACKEND variable.<\/li>\n<li>This variable will be kept around until Newton development opens up.<\/li>\n<li>Full thread: <a href=\"http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2016-February\/086272.html\">http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2016-February\/086272.html<\/a><\/li>\n<\/ul>\n<h1>All Hail the New Per-region PyPI, wheel and APT Mirrors<\/h1>\n<ul>\n<li>We have new AFS-based consistent per-region mirrors of PyPI and API repositories, with additional wheel repositories containing pre-built wheels for all the modules in global-requirements.<\/li>\n<li>You should not notice a difference, except jobs should be a bit faster and more reliable.<\/li>\n<li>Full thread: <a href=\"http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2016-February\/086295.html\">http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2016-February\/086295.html<\/a><\/li>\n<\/ul>\n<h1>Release countdown for week R-7, Feb 15-19<\/h1>\n<ul>\n<li>Focus: Project teams should be focusing on wrapping up new feature work in all libraries.<\/li>\n<li>Release Actions:\n<ul>\n<li>We will be strictly enforcing the library release freeze before Mitaka-3 in 2 weeks.<\/li>\n<li>Review client libraries, integration libraries, and any other libraries managed by your team, and ensure recent changes have been released.<\/li>\n<li>Ensure global-requirements and constraints lists are up to date, with accurate minimum versions, and exclusions.<\/li>\n<li>Projects using cycle-with-intermediary release model need to produce intermediate releases. See Thierry&#8217;s emails for details [3].<\/li>\n<li>Review stable\/liberty branches and submit patches to openstack\/releases if you want them.<\/li>\n<\/ul>\n<\/li>\n<li>Important Dates\n<ul>\n<li>Final release for\u00a0 non-client libraries: Feb 24<\/li>\n<li>Final release for client libraries: Mar 2<\/li>\n<li>Mitaka 3: Feb 29-Mar 4 (includes feature freeze and soft string freeze)<\/li>\n<\/ul>\n<\/li>\n<li>Full thread: <a href=\"http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2016-February\/086362.html\">http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2016-February\/086362.html<\/a><\/li>\n<\/ul>\n<h1>Why WADL When You Can Swagger<\/h1>\n<ul>\n<li>Continuing from previous update [4].<\/li>\n<li>Every build of the api-site is now running fairy-slipper to migrate from WADL to Swagger.\n<ul>\n<li>Those migrated Swagger files are copied to [5].<\/li>\n<\/ul>\n<\/li>\n<li>Not all files migrate smoothly. We&#8217;d love to get teams looking at these migrated files. Thank you to those who have already submitted fixes!\n<ul>\n<li>If you see a problem in the original WADL when viewing [5], log it [7].<\/li>\n<li>If you see a problem with the migration tool, log it [8].<\/li>\n<\/ul>\n<\/li>\n<li>The Infra team is reviewing a specification [6] so that we can serve API information from developer.openstack.org.<\/li>\n<li>You can hop onto #openstack-doc or #openstack-sdks to ask nick annegentle<\/li>\n<li>Full thread: <a href=\"http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2016-February\/086467.html\">http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2016-February\/086467.html<\/a><\/li>\n<\/ul>\n<h1>Tenant VS. Project<\/h1>\n<ul>\n<li>Sean Dague brings up that OpenStack&#8217;s use of tenant vs. project. Which are we transitioning to?<\/li>\n<li>Keystone is working towards allowing project_id in the service catalog [9].<\/li>\n<li>Neutron is transitioning to project_id now.<\/li>\n<li>The current Ansible OpenStack modules are using project [10].<\/li>\n<li>OSLO Logging\/Context are using project.<\/li>\n<li>Full thread: <a href=\"http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2016-February\/086396.html\">http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2016-February\/086396.html<\/a><\/li>\n<\/ul>\n<h1>Proposal: Separate Design Summits From OpenStack Conferences<\/h1>\n<ul>\n<li>The OpenStack design summits originally started out as working events.<\/li>\n<li>The OpenStack summits growing more marketing and sales focus, the contributors attending are often unfocused.<\/li>\n<li>Some contributors submit talks for the conference, because their company says it&#8217;s the only way for them to attend the conference. Part of the reason for this is the cost of attending.<\/li>\n<li>Thierry Carrez (who helps organize the design summit) explains that he has been working a solution for separation of the summit and the conference himself, and the Foundation is finalizing a strawman proposal that will be pushed to the community for comments soon.<\/li>\n<li>Full thread: <a href=\"http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2016-February\/086007.html\">http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2016-February\/086007.html<\/a><\/li>\n<\/ul>\n<p class=\"lead\">[1] &#8211; <a href=\"http:\/\/releases.openstack.org\">http:\/\/releases.openstack.org<\/a><br \/>\n[2] &#8211; <a href=\"https:\/\/review.openstack.org\/#\/c\/278333\">https:\/\/review.openstack.org\/#\/c\/278333<\/a><br \/>\n[3] &#8211; <a href=\"http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2016-February\/086152.html\">http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2016-February\/086152.html<\/a><br \/>\n[4] &#8211; <a href=\"http:\/\/www.openstack.org\/blog\/2016\/01\/openstack-developer-mailing-list-digest-january-9-15\/\">http:\/\/www.openstack.org\/blog\/2016\/01\/openstack-developer-mailing-list-digest-january-9-15\/<\/a><br \/>\n[5] &#8211; <a href=\"http:\/\/developer.openstack.org\/draft\/swagger\">http:\/\/developer.openstack.org\/draft\/swagger<\/a><br \/>\n[6] &#8211; <a href=\"https:\/\/review.openstack.org\/#\/c\/276484\/\">https:\/\/review.openstack.org\/#\/c\/276484\/<\/a><br \/>\n[7] &#8211; <a href=\"https:\/\/bugs.launchpad.net\/openstack-api-site\">https:\/\/bugs.launchpad.net\/openstack-api-site<\/a><br \/>\n[8] &#8211; <a href=\"https:\/\/bugs.launchpad.net\/openstack-doc-tools\">https:\/\/bugs.launchpad.net\/openstack-doc-tools<\/a><br \/>\n[9] &#8211; <a href=\"https:\/\/review.openstack.org\/#\/c\/279576\/\">https:\/\/review.openstack.org\/#\/c\/279576\/<\/a><br \/>\n[10] &#8211; <a href=\"http:\/\/docs.ansible.com\/ansible\/list_of_cloud_modules.html#openstack\">http:\/\/docs.ansible.com\/ansible\/list_of_cloud_modules.html#openstack<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>SuccessBot Says dhellmann: [1] is live with release history and upcoming release schedules. ttx:\u00a0 Governance changes are now announced in #openstack-dev, to increase general awareness about them! jklare: Just merged the first batch of opentack-chef cookbook patches for the Mitaka cycle! 4.229 lines of code refactored and 18.678 lines removed! johnthetubaguy: Nova subteams starting to&#8230;  <a href=\"https:\/\/www.openstack.org\/blog\/openstack-developer-mailing-list-digest-20160212\/\" class=\"more-link\" title=\"Read OpenStack Developer Mailing List Digest Feb 7-12\">Read more &raquo;<\/a><\/p>\n","protected":false},"author":82,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[1],"tags":[],"_links":{"self":[{"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/posts\/7634"}],"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\/82"}],"replies":[{"embeddable":true,"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/comments?post=7634"}],"version-history":[{"count":4,"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/posts\/7634\/revisions"}],"predecessor-version":[{"id":7638,"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/posts\/7634\/revisions\/7638"}],"wp:attachment":[{"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/media?parent=7634"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/categories?post=7634"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/tags?post=7634"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}