{"id":7804,"date":"2016-06-24T22:54:54","date_gmt":"2016-06-25T03:54:54","guid":{"rendered":"http:\/\/www.openstack.org\/blog\/?p=7804"},"modified":"2016-06-24T22:54:54","modified_gmt":"2016-06-25T03:54:54","slug":"openstack-developer-mailing-list-digest-20160624","status":"publish","type":"post","link":"https:\/\/www.openstack.org\/blog\/openstack-developer-mailing-list-digest-20160624\/","title":{"rendered":"OpenStack Developer Mailing List Digest June 18-24"},"content":{"rendered":"<h1 class=\"western\">Status of the OpenStack Port to Python 3<\/h1>\n<ul>\n<li>The only projects not ported to Python 3 yet:\n<ul>\n<li>Nova (76%)<\/li>\n<li>Trove (42%)<\/li>\n<li>Swift (0%)<\/li>\n<\/ul>\n<\/li>\n<li>Number of projects already ported:\n<ul>\n<li>19 Oslo Libraries<\/li>\n<li>4 development tools<\/li>\n<li>22 OpenStack Clients<\/li>\n<li>6 OpenStack Libraries (os-brick, taskflow, etc)<\/li>\n<li>12 OpenStack services approved by the TC<\/li>\n<li>17 OpenStack services (not approved by the TC)<\/li>\n<\/ul>\n<\/li>\n<li>Raw total: 80 projects<\/li>\n<li>Technical Committee member Doug Hellmann would like the community to set a goal for Ocata to have Python 3 functional tests running for all projects.<\/li>\n<li>Dropping support for Python 2 would be nice, but is a big step and shouldn&#8217;t distract from the goals of getting the remaining things to support Python 3.\n<ul>\n<li>Keep in mind OpenStack on PyPy which is using Python 2.7.<\/li>\n<\/ul>\n<\/li>\n<li><a href=\"http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2016-June\/thread.html#97930\">Full thread<\/a><\/li>\n<\/ul>\n<h1 class=\"western\">Proposal: Architecture Working Group<\/h1>\n<ul>\n<li>OpenStack is a big system that we have debated what it actually is <a href=\"http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2016-May\/095452.html\">[1]<\/a>.<\/li>\n<li>We want to be able to point to something and proud tell people \u201cthis is what we designed and implemented.\u201d\n<ul>\n<li>For individual projects this is possible. Neutron can talk about their agents and drivers. Nova can talk about conductors that handle communication with compute nodes.<\/li>\n<li>When we talk about how they interact with each other, it&#8217;s a coincidental mash of de-facto standards and specs. They don&#8217;t help someone make decisions when refactoring or adding on to the system.<\/li>\n<\/ul>\n<\/li>\n<li>Oslo and cross-project initiatives have brought some peace and order to implementation, but not the design process.\n<ul>\n<li>New ideas start largely in the project where they are needed most, and often conflict with similar decisions and ideas in other projects.<\/li>\n<li>When things do come to a head these things get done in a piecemeal fashion, where it&#8217;s half done here, 1\/3 over there, \u00bc there, \u00be over there.<\/li>\n<li>Maybe nova-compute should be isolated from Nova with an API Nova, Cinder and Neutron can talk to.<\/li>\n<li>Maybe we should make the scheduler cross-project aware and capable of scheduling more than just Nova.<\/li>\n<li>Maybe experimental groups should look at how some of this functionality could perhaps be delegated to non-OpenStack projects.<\/li>\n<\/ul>\n<\/li>\n<li>Clint Byrum would like to propose the creation of an Architecture Working Group.\n<ul>\n<li>A place for architects to share their designs and gain support across projects to move forward and ratify architectural decisions.<\/li>\n<li>The group being largely seniors at companies involved and if done correctly can help prioritize this work by advocating for people\/fellow engineers to actually make it &#8216;real&#8217;.<\/li>\n<\/ul>\n<\/li>\n<li>How to get inovlved:\n<ul>\n<li>Bi-weekly IRC meeting at a time convenient for the most interested individuals.<\/li>\n<li>#openstack-architecture channel<\/li>\n<li>Collaborate on the openstack-specs repo.<\/li>\n<li>Clint is working on a first draft to submit for review next week.<\/li>\n<\/ul>\n<\/li>\n<li><a href=\"http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2016-June\/thread.html#97668\">Full thread<\/a><\/li>\n<\/ul>\n<h1 class=\"western\">Release Countdown for Week R-15, Jun 20-24<\/h1>\n<ul>\n<li>Focus:\n<ul>\n<li>Teams should be working on new feature development and bug fixes.<\/li>\n<\/ul>\n<\/li>\n<li>General Notes:\n<ul>\n<li>Members of the release team will be traveling next week. This will result in delays in releases. Plan accordingly.<\/li>\n<\/ul>\n<\/li>\n<li>Release Actions:\n<ul>\n<li>Official independent projects should file information about historical releases using the openstack\/releases repository so the team pages on release.openstack.org are up to date.<\/li>\n<li>Review stable\/liberity and stable\/mitaka branches for needed releases.<\/li>\n<\/ul>\n<\/li>\n<li>Important Dates:\n<ul>\n<li>Newton 2 milestone, July 14<\/li>\n<li>\n<p align=\"left\" class=\"lead\">Newton release schedule <a href=\"http:\/\/releases.openstack.org\/newton\/schedule.html\">[2]<\/a><\/p>\n<\/li>\n<\/ul>\n<\/li>\n<li>\n<p align=\"left\"><a href=\"http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2016-June\/098067.html\">Full thread<\/a><\/p>\n<\/li>\n<\/ul>\n<h1 class=\"western\">Placement API WSGI Code \u2013 Let&#8217;s Just Use Flask<\/h1>\n<ul>\n<li>Maybe it&#8217;s better to use one of the WSGI frameworks used by the other OpenStack projects, instead of going in a completely new direction.\n<ul>\n<li>It will easier for other OpenStack contributors to become familiar with the new API placement API endpoint code if it uses Flask.<\/li>\n<li>Flask has a very strong community and does stuff well that the OpenStack community could stop worrying about.<\/li>\n<\/ul>\n<\/li>\n<li>The amount of WSGI glue above Routes\/Paste is pretty minimal in comparison to using a full web framework.\n<ul>\n<li>Template and session handling are things we don&#8217;t need. We&#8217;re a REST service, not web application.<\/li>\n<\/ul>\n<\/li>\n<li>Which frameworks are in use in Mitaka:\n<ul>\n<li>Falcon: 4 projects<\/li>\n<li>Custom + routes: 12 projects<\/li>\n<li>Pecan: 12 projects<\/li>\n<li>Flask: 2 projects<\/li>\n<li>web.py: 1 project<\/li>\n<\/ul>\n<\/li>\n<li><a href=\"http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2016-June\/thread.html#97808\">Full thread<\/a><\/li>\n<\/ul>\n<p>[1] &#8211; <a href=\"http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2016-May\/095452.html\">http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2016-May\/095452.html<\/a><\/p>\n<p>[2] &#8211; <a href=\"http:\/\/releases.openstack.org\/newton\/schedule.html\">http:\/\/releases.openstack.org\/newton\/schedule.html<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Status of the OpenStack Port to Python 3 The only projects not ported to Python 3 yet: Nova (76%) Trove (42%) Swift (0%) Number of projects already ported: 19 Oslo Libraries 4 development tools 22 OpenStack Clients 6 OpenStack Libraries (os-brick, taskflow, etc) 12 OpenStack services approved by the TC 17 OpenStack services (not approved&#8230;  <a href=\"https:\/\/www.openstack.org\/blog\/openstack-developer-mailing-list-digest-20160624\/\" class=\"more-link\" title=\"Read OpenStack Developer Mailing List Digest June 18-24\">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\/7804"}],"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=7804"}],"version-history":[{"count":3,"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/posts\/7804\/revisions"}],"predecessor-version":[{"id":7808,"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/posts\/7804\/revisions\/7808"}],"wp:attachment":[{"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/media?parent=7804"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/categories?post=7804"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/tags?post=7804"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}