{"id":8080,"date":"2017-03-18T19:54:10","date_gmt":"2017-03-19T00:54:10","guid":{"rendered":"http:\/\/www.openstack.org\/blog\/?p=8080"},"modified":"2017-03-18T19:54:37","modified_gmt":"2017-03-19T00:54:37","slug":"openstack-developer-mailing-list-digest-20170317","status":"publish","type":"post","link":"https:\/\/www.openstack.org\/blog\/openstack-developer-mailing-list-digest-20170317\/","title":{"rendered":"OpenStack Developer Mailing List Digest March 11-17"},"content":{"rendered":"<h1>SuccessBot Says<\/h1>\n<ul>\n<li>Dims <a href=\"http:\/\/eavesdrop.openstack.org\/irclogs\/#openstack-python3\/#openstack-python3.2017-01-23.log.html\">[1]<\/a>: Nova now has a python35 based CI job in check queue running Tempest tests (everything running on py35)<\/li>\n<li>jaypipes <a href=\"http:\/\/eavesdrop.openstack.org\/irclogs\/#openstack-nova\/#openstack-nova.2017-01-31.log.html\">[2]<\/a>: Finally got a good functional test created that stresses the Ironic and Nova integration and migration from Newton to Ocata.<\/li>\n<li>Lbragstad <a href=\"http:\/\/eavesdrop.openstack.org\/irclogs\/#openstack-keystone\/#openstack-keystone.2017-02-09.log.html\">[3]<\/a>: the OpenStack-Ansible project has a test environment that automates rolling upgrade performance testing<\/li>\n<li>annegentle <a href=\"http:\/\/eavesdrop.openstack.org\/irclogs\/#openstack-dev\/#openstack-dev.2017-02-16.log.html\">[4]<\/a>: Craig Sterrett and the App Dev Enablement WG: New links to more content for the appdev docs <a href=\"https:\/\/developer.openstack.org\/\">[5]<\/a><\/li>\n<li>jlvillal <a href=\"http:\/\/eavesdrop.openstack.org\/irclogs\/#openstack-ironic\/#openstack-ironic.2017-03-16.log.html\">[6]<\/a>: Ironic team completed the multi-node grenade CI job<\/li>\n<li>Tell us yours via OpenStack IRC channels with message \u201c#success &lt;message&gt;\u201d<\/li>\n<\/ul>\n<ul>\n<li>All: [<a href=\"https:\/\/wiki.openstack.org\/wiki\/Successes\">7<\/a>]<\/li>\n<\/ul>\n<h1 class=\"western\">Pike Release Management Communication<\/h1>\n<ul>\n<li>The release liaison is responsible for:\n<ul>\n<li>Coordinating with the release management team.<\/li>\n<li>Validating your team release team requests.<\/li>\n<li>Ensure release cycle deadlines are met.<\/li>\n<li>It&#8217;s encouraged to nominate a release liaison. Otherwise this tasks falls back to the PTL.<\/li>\n<\/ul>\n<\/li>\n<li>Ensure the releaase liaison has time and ability to handle the communication necessary.\n<ul>\n<li>Failing to follow through on a needed process step may block you from meeting deadlines or releasing as our milestones are date-based, not feature-based.<\/li>\n<\/ul>\n<\/li>\n<li>Three primary communication tools:\n<ul>\n<li>Email for announcements and asynchronous communication\n<ul>\n<li>\u201c[release]\u201d topic tag on the openstack-dev mailing list.<\/li>\n<li>This includes the weekly release countdown emails with details on focus, tasks, and upcoming dates.<\/li>\n<\/ul>\n<\/li>\n<li>IRC for time sensitive interactions\n<ul>\n<li>With more than 50 teams, the release team relies on your presence in the freenode #openstack-release channel.<\/li>\n<\/ul>\n<\/li>\n<li>Written documentation for relatively stable information\n<ul>\n<li>The release team has published the schedule for the Pike cycle <a href=\"http:\/\/releases.openstack.org\/pike\/schedule.html\">[8]<\/a><\/li>\n<li>You can add the schedule to your own calendar <a href=\"https:\/\/releases.openstack.org\/schedule.ics\">[9]<\/a><\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n<li>Things to do right now:\n<ul>\n<li>Update your release liaisons <a href=\"https:\/\/wiki.openstack.org\/wiki\/CrossProjectLiaisons#Release_management\">[10]<\/a>.<\/li>\n<li>Make sure your IRC and email address listed in projects.yaml <a href=\"http:\/\/git.openstack.org\/cgit\/openstack\/governance\/tree\/reference\/projects.yaml\">[11]<\/a>.<\/li>\n<\/ul>\n<\/li>\n<li>Update your mail filters to look for \u201c[release]\u201d in the subject line.<\/li>\n<li>Full thread <a href=\"http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2017-March\/113303.html\">[12]<\/a><\/li>\n<\/ul>\n<h1 class=\"western\">OpenStack Summit Boston Schedule Now Live!<\/h1>\n<ul>\n<li>Main conference schedule <a href=\"https:\/\/www.openstack.org\/summit\/boston-2017\/summit-schedule\/\">[13]<\/a><\/li>\n<li>Register now <a href=\"https:\/\/openstacksummit2017boston.eventbrite.com\/\">[14]<\/a><\/li>\n<li>Hotel discount rates for attendees <a href=\"https:\/\/www.openstack.org\/summit\/boston-2017\/travel\/#hotels\">[15]<\/a><\/li>\n<li>Stackcity party <a href=\"https:\/\/www.openstack.org\/summit\/boston-2017\/summit-schedule\/events\/18621\/save-the-date-stackcity-boston\">[16]<\/a><\/li>\n<li>Take the certified OpenStack Administrator exam <a href=\"https:\/\/www.openstack.org\/summit\/boston-2017\/#openstackcoa\">[17]<\/a><\/li>\n<li>City guide of restaurants and must see sites <a href=\"https:\/\/www.openstack.org\/summit\/boston-2017\/boston-city-guide\/\">[18]<\/a><\/li>\n<li>Full thread [<a href=\"http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2017-March\/113669.html\">19]<\/a><\/li>\n<\/ul>\n<h1 class=\"western\">Some Information About the Forum at the Summit in Boston<\/h1>\n<ul>\n<li>\u201cForum\u201d proper\n<ul>\n<li>3 medium sized fishbowl rooms for cross-community discussions.<\/li>\n<li>Selected and scheduled by a committee formed of TC and UC members, facilitated by the Foundation staff members.<\/li>\n<li>Brainstorming for topics <a href=\"http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2017-March\/113115.html\">[20]<\/a><\/li>\n<\/ul>\n<\/li>\n<li>\u201cOn-boarding\u201d rooms\n<ul>\n<li>Two rooms setup classroom style for projects teams and workgroups who want to on-board new team members.<\/li>\n<li>Examples include providing introduction to your codebase for prospective new contributors.<\/li>\n<li>These should not be tradiitonal \u201cproject intro\u201d talks.<\/li>\n<\/ul>\n<\/li>\n<li>Free hacking\/meetup spaces\n<ul>\n<li>Four to five rooms populated with roundtables for ad-hoc discussions and hacking.<\/li>\n<\/ul>\n<\/li>\n<li>Full thread <a href=\"http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2017-March\/thread.html#113459\">[21]<\/a><\/li>\n<\/ul>\n<p class=\"lead\">&nbsp;<\/p>\n<h1 class=\"western\">The Future of the App Catalog<\/h1>\n<ul>\n<li>Created early 2015 as a market place of pre-packaged applications <a href=\"http:\/\/apps.openstack.org\/\">[22]<\/a> that you can deploy using Murano.<\/li>\n<li>This has grown to 45 Glance images, 13 Heat templates and 6 Tosca templates. Otherwise did not pick up a lot of steam.<\/li>\n<li>~30% are just thin wrappers around Docker containers.<\/li>\n<li>Traffic stats show 100 visits per week, 75% of which only read the index page.<\/li>\n<li>In parallel, Docker developed a pretty successful containerized application marketplace (Docker Hub) with hundreds or thousands regularly updated apps.\n<ul>\n<li>Keeping the catalog around makes us look like we are unsuccessfully trying to compete with that ecosystem, while OpenStack is in fact complimentary.<\/li>\n<\/ul>\n<\/li>\n<li>In the past, we have retired projects that were dead upstream.\n<ul>\n<li>The app catalog is however has an active maintenance team.<\/li>\n<li>If we retire the app catalog, it would not be a reflection on that team performance, but that the beta was arguably not successful in build an active market place and a great fit from a strategy perspective.<\/li>\n<\/ul>\n<\/li>\n<li>Two approaches for users today to deploy docker apps in OpenStack:\n<ul>\n<li>Container-native approach using \u201cdocker run\u201d after using Nova or K8s cluster using Magnum.<\/li>\n<li>OpenStack Native approach \u201czun create nginx\u201d.<\/li>\n<\/ul>\n<\/li>\n<li>Full thread <a href=\"http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2017-March\/thread.html#113362\">[23]<\/a><a href=\"http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2017-March\/thread.html#113508\">[24]<\/a><\/li>\n<\/ul>\n<h1 class=\"western\">ZooKeeper vs etcd for Tooz\/DLM<\/h1>\n<ul>\n<li>Devstack defaults to ZooKeeper and is opinionated about it.<\/li>\n<li>Lots of container related projects are using etcd <a href=\"http:\/\/codesearch.openstack.org\/?q=etcd&amp;i=nope&amp;files=devstack\/.*&amp;repos=\">[25]<\/a>, so do we need to avoid both ZooKeeper and etcd?<\/li>\n<li>For things like databases and message queues, it&#8217;s more than time for us to contract on one solution.\n<ul>\n<li>For DLMs ZooKeepers gives us mature\/ featureful angle. Etcd covers the Kubernetes cooperation \/ non-java angle.<\/li>\n<\/ul>\n<\/li>\n<li>OpenStack interacts with DLM&#8217;s via the library Tooz. Tooz today only supports etcd v2, but v3 is planned which would support GRPC.<\/li>\n<li>The OpenStack gate will begin to default to etcd with Tooz.<\/li>\n<li>Full thread <a href=\"http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2017-March\/thread.html#113885\">[26]<\/a><\/li>\n<\/ul>\n<h1 class=\"western\">Small Steps for Go<\/h1>\n<ul>\n<li>An etherpad <a href=\"https:\/\/etherpad.openstack.org\/p\/go-and-containers\">[27]<\/a> has been started to begin tackling the new language requirements <a href=\"https:\/\/governance.openstack.org\/tc\/reference\/new-language-requirements.html\">[28]<\/a> for Go.<\/li>\n<li>An golang-commons repository exists <a href=\"http:\/\/git.openstack.org\/cgit\/openstack\/golang-commons\/\">[29]<\/a><\/li>\n<li>Gopher cloud versus having a golang-client project is being discussed in the etherpad. Regardless we need support for os-client-config.<\/li>\n<li>Full thread <a href=\"http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2017-March\/thread.html#113463\">[30]<\/a><\/li>\n<\/ul>\n<h1 class=\"western\">POST \/api-wg\/news<\/h1>\n<ul>\n<li>Guidelines under review:\n<ul>\n<li>Add API capabilities discovery guideline <a href=\"https:\/\/review.openstack.org\/#\/c\/386555\/\">[31]<\/a><\/li>\n<li>Refactor and re-validate API change guidelines <a href=\"https:\/\/review.openstack.org\/#\/c\/421846\/\">[32]<\/a><\/li>\n<li>Microversions: add next_min_version field in version body <a href=\"https:\/\/review.openstack.org\/#\/c\/446138\/\">[33]<\/a><\/li>\n<li>WIP: microversion architecture archival doc <a href=\"https:\/\/review.openstack.org\/444892\">[34]<\/a><\/li>\n<\/ul>\n<\/li>\n<li>Full thread <a href=\"http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2017-March\/114167.html\">[35]<\/a><\/li>\n<\/ul>\n<h1 class=\"western\">Proposal to Rename Castellan to oslo.keymanager<\/h1>\n<ul>\n<li>Castellan is a python abstraction to different keymanager solutions such as Barbican. Implementations like Vault could be supported, but currently is not.<\/li>\n<li>The rename would emphasize the Castellan is an abstraction layer.\n<ul>\n<li>Similar to oslo.db supporting MySQL and PostgreSQL.<\/li>\n<\/ul>\n<\/li>\n<li>Instead of oslo.keymanager, it can be rolled into the oslo umbrella without a rename. Tooz sets the precedent of this.<\/li>\n<li>Full thread <a href=\"http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2017-March\/thread.html#113863\">[36]<\/a><\/li>\n<\/ul>\n<h1 class=\"western\">Release Countdown for week R-23 and R-22<\/h1>\n<ul>\n<li>Focus:\n<ul>\n<li>Specification approval and implementation for priority features for this cycle.<\/li>\n<\/ul>\n<\/li>\n<li>Actions:\n<ul>\n<li>Teams should research how they can meet the Pike release goals <a href=\"https:\/\/governance.openstack.org\/tc\/goals\/pike\/index.html\">[37]<\/a><a href=\"https:\/\/governance.openstack.org\/tc\/goals\/\">[38]<\/a>.<\/li>\n<li>Teams that want to change their release model should do so before end of Pike-1 <a href=\"http:\/\/git.openstack.org\/cgit\/openstack\/releases\/tree\/deliverables\/pike\">[39]<\/a>.<\/li>\n<\/ul>\n<\/li>\n<li>Upcoming Deadlines and Dates\n<ul>\n<li>Boston Forum topic formal submission period: March 20 &#8211; April 2<\/li>\n<li>Pike-1 milestone: April 13 (R-20 week)<\/li>\n<li>Forum at OpenStack Summit in Boston: May 8-11<\/li>\n<\/ul>\n<\/li>\n<li>Full thread <a href=\"http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2017-March\/113691.html\">[40]<\/a><\/li>\n<\/ul>\n<h1 class=\"western\">Deployment Working Group<\/h1>\n<ul>\n<li>Mission: To collaborate on best practices for deploying and configuring OpenStack in production environments.<\/li>\n<li>Examples:\n<ul>\n<li>OpenStack Ansible and Puppet OpenStack have been collaborating on Continuous Integration scenarios but also on Nova upgrades orchestration<\/li>\n<li>TripleO and Kolla share the same tool for container builds.<\/li>\n<li>TripleO and Fuel share the same Puppet OpenStack modules.<\/li>\n<li>OpenStack and Kubernetes are interested in collaborating on configuration management.<\/li>\n<li>Most of tools want to collect OpenStack parameters for configuration management in a common fashion.<\/li>\n<\/ul>\n<\/li>\n<li>Wiki <a href=\"https:\/\/wiki.openstack.org\/wiki\/Deployment\">[41]<\/a> has been started to document how the group will work together. Also an etherpad <a href=\"https:\/\/etherpad.openstack.org\/p\/deployment-pike\">[42]<\/a> for brainstorming.<\/li>\n<\/ul>\n<p>&nbsp;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>SuccessBot Says Dims [1]: Nova now has a python35 based CI job in check queue running Tempest tests (everything running on py35) jaypipes [2]: Finally got a good functional test created that stresses the Ironic and Nova integration and migration from Newton to Ocata. Lbragstad [3]: the OpenStack-Ansible project has a test environment that automates&#8230;  <a href=\"https:\/\/www.openstack.org\/blog\/openstack-developer-mailing-list-digest-20170317\/\" class=\"more-link\" title=\"Read OpenStack Developer Mailing List Digest March 11-17\">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\/8080"}],"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=8080"}],"version-history":[{"count":3,"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/posts\/8080\/revisions"}],"predecessor-version":[{"id":8083,"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/posts\/8080\/revisions\/8083"}],"wp:attachment":[{"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/media?parent=8080"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/categories?post=8080"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/tags?post=8080"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}