{"id":8093,"date":"2017-05-07T09:17:00","date_gmt":"2017-05-07T14:17:00","guid":{"rendered":"http:\/\/www.openstack.org\/blog\/?p=8093"},"modified":"2017-05-07T09:17:41","modified_gmt":"2017-05-07T14:17:41","slug":"openstack-developer-mailing-list-digest-20170507","status":"publish","type":"post","link":"https:\/\/www.openstack.org\/blog\/openstack-developer-mailing-list-digest-20170507\/","title":{"rendered":"OpenStack Developer Mailing List Digest April 29 &#8211; May 5"},"content":{"rendered":"<h2><b>POST \/api-wg\/news<\/b><\/h2>\n<ul>\n<li>Newly Published Guidelines\n<ul>\n<li>Create a set of API interoperability guidelines <a href=\"https:\/\/review.openstack.org\/#\/c\/421846\/\">1<\/a><\/li>\n<\/ul>\n<\/li>\n<li>Guidelines Current Under Review\n<ul>\n<li>Microversions: add next<i>min<\/i>version field in version body <a href=\"https:\/\/review.openstack.org\/#\/c\/446138\/\">2<\/a><\/li>\n<li>A suite of five documents about version discovery <a href=\"https:\/\/review.openstack.org\/#\/c\/459405\/\">3<\/a><\/li>\n<li>Support for historical service type aliases <a href=\"https:\/\/review.openstack.org\/#\/c\/460654\/3\">4<\/a><\/li>\n<li>WIP: microversion architecture archival document <a href=\"https:\/\/review.openstack.org\/444892\">5<\/a><\/li>\n<\/ul>\n<\/li>\n<li>Full thread: <a href=\"http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2017-May\/116374.html\">6<\/a><\/li>\n<\/ul>\n<h2><b>Release countdown for week R-16 and R-15 May 8-9<\/b><\/h2>\n<ul>\n<li>Focus:\n<ul>\n<li>Pike feature development and completion of release goals.<\/li>\n<li>Team members attending the Forum at the Boston summit should be focused in requirements gathering and collecting feedback from other parts of the community.<\/li>\n<\/ul>\n<\/li>\n<li>Actions:\n<ul>\n<li>Some projects still need to do Ocata stable point release.\n<ul>\n<li>aodh<\/li>\n<li>barbican<\/li>\n<li>congress<\/li>\n<li>designate<\/li>\n<li>freezer<\/li>\n<li>glance<\/li>\n<li>keystone<\/li>\n<li>manila<\/li>\n<li>mistral<\/li>\n<li>sahara<\/li>\n<li>searchlight<\/li>\n<li>tricircle<\/li>\n<li>trove<\/li>\n<li>zaqar<\/li>\n<\/ul>\n<\/li>\n<li>Projects following intermediary-release models and haven\u2019t done any:\n<ul>\n<li>aodh<\/li>\n<li>bitfrost<\/li>\n<li>ceilometer<\/li>\n<li>cloud kitty[-dashboard]<\/li>\n<li>ironic-python-agent<\/li>\n<li>karbor[-dashboard]<\/li>\n<li>magnum[-ui]<\/li>\n<li>murano-agent<\/li>\n<li>panko<\/li>\n<li>senlin-dashboard<\/li>\n<li>solum[-dashboard]<\/li>\n<li>tacker[-dashboard]<\/li>\n<li>virtage[-dashboard]<\/li>\n<\/ul>\n<\/li>\n<li>Independent projects that have not published anything for 2017:\n<ul>\n<li>solum<\/li>\n<li>bandit<\/li>\n<li>syntribos<\/li>\n<\/ul>\n<\/li>\n<li>Upcoming deadlines and dates:\n<ul>\n<li>Forum at OpenStack Summit in Boston: May 8-11<\/li>\n<li>Pike-2 milestone 2: June 8<\/li>\n<\/ul>\n<\/li>\n<li>Full thread: <a href=\"http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2017-May\/116401.html\">7<\/a><\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<h2><b>OpenStack moving both too fast and too slow at the same time<\/b><\/h2>\n<ul>\n<li>Drew Fisher makes the observation that the user survey <a href=\"https:\/\/www.openstack.org\/assets\/survey\/April2017SurveyReport.pdf\">8<\/a> shows the same issue time and time again on page 18-19.\n<ul>\n<li>Things move too fast<\/li>\n<li>No LTS release<\/li>\n<li>Upgrades are scary for anything that isn\u2019t N-1 \u2190N\n<ul>\n<li>The OpenStack community has reasonable testing in place to ensure that N-1 \u2190N upgrades work.<\/li>\n<li>Page 18: &#8220;Most large customers move slowly and thus are running older versions, which are EOL upstream sometimes before they even deploy them.&#8221;<\/li>\n<li>We\u2019re unlikely to add more stable releases or work on them longer because:<\/li>\n<\/ul>\n<\/li>\n<li>We need more people to do the work. It has been difficult to attract contributors to this area.<\/li>\n<li>Find a way to do that work that doesn\u2019t hurt our ability to work on master.<\/li>\n<\/ul>\n<\/li>\n<li>We need older versions of the deployment platforms available in our CI to run automated tests.\n<ul>\n<li>Supported version of development tools setup tools and pip.<\/li>\n<li>Supported versions of the various libraries and system-level dependencies like libvirt.<\/li>\n<\/ul>\n<\/li>\n<li>OpenStack started with no stable branches, where we were producing releases and ensuring that updates vaguely worked with N-1 \u2190N.<\/li>\n<li>Distributions maintained their own stable branches.\n<ul>\n<li>It was suggested instead of doing duplicate effort, to share a stable branch.\n<ul>\n<li>The involvement of distribution packagers became more limited.<\/li>\n<li>Today it\u2019s just one person, who is currently seeking employment.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n<li>Maintaining stable branches has a cost.\n<ul>\n<li>Complex to ensure that stable branches actually keep working.<\/li>\n<li>Availability of infrastructure resources.<\/li>\n<\/ul>\n<\/li>\n<li>OpenStack became more stable, so the demand for longer-term maintenance became stronger.\n<ul>\n<li>People expect upstream to provide it, not realizing that upstream is made of people employed by various organizations, and apparently this isn\u2019t of interest to fund.<\/li>\n<\/ul>\n<\/li>\n<li>Current stable branch model is kind of useless in only supporting stable branches for one year. Two potential outcomes:\n<ul>\n<li>The OpenStack community still thinks there is a lot of value in doing this work upstream, in which organizations should invest resources in making that happen.<\/li>\n<li>The OpenStack community thinks this is better handled downstream, and we should get rid of them completely.<\/li>\n<\/ul>\n<\/li>\n<li>For people attending the summit, there will be an on-boarding session for the stable team <a href=\"https:\/\/www.openstack.org\/summit\/boston-2017\/summit-schedule\/events\/18694\/infraqarelease-mgmtregsstable-project-onboarding\">9<\/a><\/li>\n<li>Matt Riedemann did a video <a href=\"https:\/\/www.openstack.org\/videos\/video\/openstack-stable-what-it-actually-means-to-maintain-stable-branches\">10<\/a> ether pad <a href=\"https:\/\/etherpad.openstack.org\/p\/stable-branch-eol-policy-newton\">11<\/a> and slides <a href=\"https:\/\/docs.google.com\/presentation\/d\/1k0mCHwRZ3_Z8zJw_WilsuTYYqnUDlY2PkgVJLz_xVQc\/edit?usp=sharing\">12<\/a> on the stable work. In the end, it was determined the cost of doing it didn\u2019t justify the dream on, lack of resources to do it.<\/li>\n<li>Full thread: <a href=\"http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2017-May\/thread.html#116298\">13<\/a><\/li>\n<\/ul>\n<p class=\"lead\">&nbsp;<\/p>\n<p>[1] &#8211; <a href=\"https:\/\/review.openstack.org\/#\/c\/421846\/\">https:\/\/review.openstack.org\/#\/c\/421846\/<\/a><\/p>\n<p>[2] &#8211; <a href=\"https:\/\/review.openstack.org\/#\/c\/446138\/\">https:\/\/review.openstack.org\/#\/c\/446138\/<\/a><\/p>\n<p>[3] &#8211; <a href=\"https:\/\/review.openstack.org\/#\/c\/459405\/\">https:\/\/review.openstack.org\/#\/c\/459405\/<\/a><\/p>\n<p>[4] &#8211; <a href=\"https:\/\/review.openstack.org\/#\/c\/460654\/3\">https:\/\/review.openstack.org\/#\/c\/460654\/3<\/a><\/p>\n<p>[5] &#8211; <a href=\"https:\/\/review.openstack.org\/444892\">https:\/\/review.openstack.org\/444892<\/a><\/p>\n<p>[6]\u00a0 &#8211; <a href=\"http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2017-May\/116374.html\">http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2017-May\/116374.html<\/a><\/p>\n<p>[7] &#8211; <a href=\"http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2017-May\/116401.html\">http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2017-May\/116401.html<\/a><\/p>\n<p>[8] &#8211; <a href=\"https:\/\/www.openstack.org\/assets\/survey\/April2017SurveyReport.pdf\">https:\/\/www.openstack.org\/assets\/survey\/April2017SurveyReport.pdf<\/a><\/p>\n<p>[9] &#8211; <a href=\"https:\/\/www.openstack.org\/summit\/boston-2017\/summit-schedule\/events\/18694\/infraqarelease-mgmtregsstable-project-onboarding\">https:\/\/www.openstack.org\/summit\/boston-2017\/summit-schedule\/events\/18694\/infraqarelease-mgmtregsstable-project-onboarding<\/a><\/p>\n<p>[10] &#8211; <a href=\"https:\/\/www.openstack.org\/videos\/video\/openstack-stable-what-it-actually-means-to-maintain-stable-branches\">https:\/\/www.openstack.org\/videos\/video\/openstack-stable-what-it-actually-means-to-maintain-stable-branches<\/a><\/p>\n<p>[11] &#8211; <a href=\"https:\/\/etherpad.openstack.org\/p\/stable-branch-eol-policy-newton\">https:\/\/etherpad.openstack.org\/p\/stable-branch-eol-policy-newton<\/a><\/p>\n<p>[12] &#8211; <a href=\"https:\/\/docs.google.com\/presentation\/d\/1k0mCHwRZ3_Z8zJw_WilsuTYYqnUDlY2PkgVJLz_xVQc\/edit?usp=sharing\">https:\/\/docs.google.com\/presentation\/d\/1k0mCHwRZ3_Z8zJw_WilsuTYYqnUDlY2PkgVJLz_xVQc\/edit?usp=sharing<\/a><\/p>\n<p>[13] &#8211;\u00a0<a href=\"http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2017-May\/thread.html#116298\">http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2017-May\/thread.html#116298<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>POST \/api-wg\/news Newly Published Guidelines Create a set of API interoperability guidelines 1 Guidelines Current Under Review Microversions: add nextminversion field in version body 2 A suite of five documents about version discovery 3 Support for historical service type aliases 4 WIP: microversion architecture archival document 5 Full thread: 6 Release countdown for week R-16&#8230;  <a href=\"https:\/\/www.openstack.org\/blog\/openstack-developer-mailing-list-digest-20170507\/\" class=\"more-link\" title=\"Read OpenStack Developer Mailing List Digest April 29 &#8211; May 5\">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\/8093"}],"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=8093"}],"version-history":[{"count":3,"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/posts\/8093\/revisions"}],"predecessor-version":[{"id":8096,"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/posts\/8093\/revisions\/8096"}],"wp:attachment":[{"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/media?parent=8093"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/categories?post=8093"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/tags?post=8093"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}