{"id":7915,"date":"2016-10-14T12:58:27","date_gmt":"2016-10-14T17:58:27","guid":{"rendered":"http:\/\/www.openstack.org\/blog\/?p=7915"},"modified":"2016-10-14T12:58:47","modified_gmt":"2016-10-14T17:58:47","slug":"openstack-developer-mailing-list-digest-20161014","status":"publish","type":"post","link":"https:\/\/www.openstack.org\/blog\/openstack-developer-mailing-list-digest-20161014\/","title":{"rendered":"OpenStack Developer Mailing List Digest October 8-14"},"content":{"rendered":"<h1 class=\"p1\"><b>SuccessBot Says<\/b><\/h1>\n<ul>\n<li class=\"li5\"><span class=\"s1\">loquacities: Newton docs are live on docs.openstack.org! Way to go docs team \\o\/<\/span><\/li>\n<li class=\"li5\"><span class=\"s1\">dhellmann: OpenStack Newton is officially released!<\/span><\/li>\n<li class=\"li5\"><span class=\"s1\">tristanC: 6 TC members elected for Ocata <a href=\"http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2016-October\/105299.html\"><span class=\"s3\">[1]<\/span><\/a>.<\/span><\/li>\n<li class=\"li5\"><span class=\"s1\">dulek: Cinder gate is now voting on basic rolling upgrades support. One step closer to get assert:supports-rolling-upgrade tag. \ud83d\ude42<\/span><\/li>\n<li class=\"li5\"><span class=\"s1\"><a href=\"https:\/\/wiki.openstack.org\/wiki\/Successes\">More<\/a><\/span><\/li>\n<\/ul>\n<h1 class=\"p4\"><span class=\"s1\"><b>Thoughts on the TC Election Process<\/b><\/span><\/h1>\n<ul>\n<li class=\"li5\"><span class=\"s1\">When deciding to run, candidates write a long thoughtful essay on their reasons for wanting to serve on the TC.<\/span>\n<ul>\n<li class=\"li5\"><span class=\"s1\">It is rare for anyone to ask follow-up question, or to challenge the candidates to explain their position more definitively.<\/span><\/li>\n<li class=\"li5\"><span class=\"s1\">Some people pick by names they are most familiar with and don\u2019t read those candidacy posts.<\/span><\/li>\n<li class=\"li5\"><span class=\"s1\">It is believed that it\u2019s rare for someone who hasn\u2019t been a PTL of a large project to be elected.<\/span><\/li>\n<li class=\"li5\"><span class=\"s1\">An example of implicit bias, blind auditions for musical orchestras radically changing the selection results <a href=\"http:\/\/blog.leafe.com\/bias\/\"><span class=\"s3\">[2]<\/span><\/a>.<\/span><\/li>\n<\/ul>\n<\/li>\n<li class=\"li5\"><span class=\"s1\">Proposal: have candidates self-nominate, but instead of a long candidacy letter, just state their interests in serving.<\/span>\n<ul>\n<li class=\"li5\"><span class=\"s1\">After nominations close, the election officials will assign each candidate with a<span class=\"Apple-converted-space\">\u00a0 <\/span>non-identifying label (e.g. random number).<\/span><\/li>\n<li class=\"li5\"><span class=\"s1\">Candidates will post their thoughts and positions and respond to questions from people.<\/span><\/li>\n<li class=\"li5\"><span class=\"s1\">Candidacy essay would be posted in the campaign period, instead of the nomination period. This will exclude biographical information.<\/span><\/li>\n<li class=\"li5\"><span class=\"s1\">Perhaps candidates can forward their responses to election officials, who will post them for the candidates and identify only by candidate number.<\/span><\/li>\n<li class=\"li5\"><span class=\"s1\">The voting form will only list the candidates\u2019 numbers.<\/span><\/li>\n<\/ul>\n<\/li>\n<li class=\"li5\"><span class=\"s1\">Thoughts on the proposal:<\/span>\n<ul>\n<li class=\"li5\"><span class=\"s1\">Not allowing people to judge peoples\u2019 character introduces a fraud incentive. You can tell friends your number secretly. Their implicit bias will make them think this is morally ok, and make them more likely to vote for you.<\/span><\/li>\n<li class=\"li5\"><span class=\"s1\">It can be important to identify candidates. For some people, there\u2019s a difference in what they say, and what they end up doing when left calling the shots.<\/span><\/li>\n<li class=\"li5\"><span class=\"s1\">Familiarity doesn\u2019t necessarily equal bias. Trust is not bias.<\/span><\/li>\n<li class=\"li5\"><span class=\"s1\">A good example [2] of needing to know the speaker and words came out of the thread. Also a reason why anonymous elections for leaders are a bad idea and favor native English speakers.<\/span><\/li>\n<\/ul>\n<\/li>\n<li class=\"li5\"><span class=\"s1\">We need several things:<\/span>\n<ul>\n<li class=\"li5\"><span class=\"s1\">Allow time between the nomination and the voting. Some candidates don\u2019t announce until the last day or two. This doesn\u2019t allow much time to get to know them.<\/span><\/li>\n<li class=\"li5\"><span class=\"s1\">How to deal with timezone differences. One candidate may post an answer early and get more reaction.<\/span><\/li>\n<li class=\"li5\"><span class=\"s1\">Reduce the effect of incumbency.<\/span><\/li>\n<\/ul>\n<\/li>\n<li class=\"li5\"><span class=\"s1\">The comparison of orchestra auditions was brought up a couple of cycles ago as well, but could be a bad comparison. The job being asked of people was performing their instrument, and it turns out a lot of things not having to do with performing their instrument were biasing the results.<\/span>\n<ul>\n<li class=\"li5\"><span class=\"s1\">The job of the TC is:<\/span>\n<ul>\n<li class=\"li5\"><span class=\"s1\">Putting the best interests of OpenStack at heart.<\/span><\/li>\n<li class=\"li5\"><span class=\"s1\">Be effective in working with a diverse set of folks in our community to get things done.<\/span><\/li>\n<li class=\"li5\"><span class=\"s1\">To find areas of friction and remove them.<\/span><\/li>\n<li class=\"li5\"><span class=\"s1\">Help set the overall direction for the project that community accepts.<\/span><\/li>\n<\/ul>\n<\/li>\n<li class=\"li5\"><span class=\"s1\">Writing a good candidacy email isn\u2019t really good representation of those abilities. It\u2019s the measure of writing a good candidacy email, in English.<\/span><\/li>\n<\/ul>\n<\/li>\n<li><span class=\"s1\">Sean Dague hopes that when voters vote in the election that they are taking the reputation of individuals into account.<\/span>\n<ul>\n<li class=\"li5\"><span class=\"s1\">Look at the work they did across all of OpenStack.<\/span><\/li>\n<li class=\"li5\"><span class=\"s1\">How they got consensus on items.<\/span><\/li>\n<li class=\"li5\"><span class=\"s1\">What efforts they are able to get folks to rally around and move forward.<\/span><\/li>\n<li class=\"li5\"><span class=\"s1\">When they get stuck and get unstuck.<\/span><\/li>\n<li class=\"li5\"><span class=\"s1\">When they ask for help and\/or admit they\u2019re out of their element.<\/span><\/li>\n<li class=\"li5\"><span class=\"s1\">How they help new folks.<\/span><\/li>\n<li class=\"li5\"><span class=\"s1\">How they work with long timers.<\/span><\/li>\n<\/ul>\n<\/li>\n<li class=\"li5\">\n<ul>\n<li class=\"li5\"><span class=\"s1\">It\u2019s easy to dismiss it as a popularity contest, however, this is about evaluating the plausible promise that the individuals put forward. Not just ideas they have, but how likely they are to be able to bring them to fruition.<\/span><\/li>\n<\/ul>\n<\/li>\n<li class=\"li5\"><span class=\"s1\"><a href=\"http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2016-October\/thread.html#104964\">Full thread<\/a><\/span><\/li>\n<\/ul>\n<h1 class=\"p4\"><span class=\"s1\"><b>API Workgroup News<\/b><\/span><\/h1>\n<ul>\n<li class=\"li5\"><span class=\"s1\">API usability tests being conducted at the Barcelona summit <a href=\"https:\/\/wiki.openstack.org\/wiki\/UX#Participate_in_a_usability_study_being_conducted_at_the_Barcelona_Summit.21\"><span class=\"s3\">[3]<\/span><\/a>.<\/span><\/li>\n<li class=\"li5\"><span class=\"s1\">Two lively discussions <a href=\"http:\/\/eavesdrop.openstack.org\/meetings\/api_wg\/\"><span class=\"s3\">[4]<\/span><\/a>:<\/span>\n<ul>\n<li class=\"li5\"><span class=\"s1\">Collecting and improving error messages across OpenStack.<\/span><\/li>\n<li class=\"li5\"><span class=\"s1\">Request semantics with regards to GET and body processing.<\/span><\/li>\n<\/ul>\n<\/li>\n<li class=\"li5\"><span class=\"s1\">New guidelines:<\/span>\n<ul>\n<li class=\"li5\"><span class=\"s1\">Add a warning about JSON expectations <a href=\"https:\/\/review.openstack.org\/#\/c\/364460\/\"><span class=\"s3\">[5]<\/span><\/a>.<\/span><\/li>\n<\/ul>\n<\/li>\n<li class=\"li5\"><span class=\"s1\">Guidelines currently under review:<\/span>\n<ul>\n<li class=\"li5\"><span class=\"s1\">Specify time intervals based filtering queries <a href=\"https:\/\/review.openstack.org\/#\/c\/383862\/\"><span class=\"s3\">[6]<\/span><\/a>.<\/span><\/li>\n<\/ul>\n<\/li>\n<li class=\"li5\"><span class=\"s1\"><a href=\"http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2016-October\/105675.html\">Full thread<\/a><\/span><\/li>\n<\/ul>\n<h1 class=\"p4\"><span class=\"s1\"><b>Project Teams Gathering from the Ops Perspective<\/b><\/span><\/h1>\n<ul>\n<li class=\"li5\"><span class=\"s1\">The first PTG will be held February 20-24 in Atlanta, GA at the downtown Sheraton hotel.<\/span><\/li>\n<li class=\"li5\"><span class=\"s1\">Tickets are $100.<\/span><\/li>\n<li class=\"li5\"><span class=\"s1\">Group rate is $185\/night.<\/span><\/li>\n<li class=\"li5\"><span class=\"s1\">Registration will go live in the next couple of weeks.<\/span><\/li>\n<li class=\"li5\"><span class=\"s1\">Horizontal\/cross project teams will meet Monday and Tuesday.<\/span><\/li>\n<li class=\"li5\"><span class=\"s1\">Vertical projects will meet Wednesday through Friday.<\/span><\/li>\n<li class=\"li5\"><span class=\"s1\">There\u2019s a lot of great planning happening around the PTG planning, however, it\u2019s going take some time for operators to figure it out.<\/span><\/li>\n<li class=\"li5\"><span class=\"s1\">Tom Fifield gives some notes for the operators:<\/span>\n<ul>\n<li class=\"li5\"><span class=\"s1\">Check out the diagram on the PTG site <a href=\"https:\/\/www.openstack.org\/ptg\"><span class=\"s3\">[7]<\/span><\/a>.<\/span>\n<ul>\n<li class=\"li5\"><span class=\"s1\">We\u2019re finally acknowledging a release cycle starts with planning. Now we\u2019ll be finalizing a release, while planning another.<\/span><\/li>\n<li class=\"li5\"><span class=\"s1\">This puts the summit at the right place to get feedback and decent ideas from users.<\/span><\/li>\n<\/ul>\n<\/li>\n<li class=\"li5\"><span class=\"s1\">The OpenStack summit is the place the entire community gets together.<\/span>\n<ul>\n<li class=\"li5\"><span class=\"s1\">The PTG doesn\u2019t mean the summit becomes a marketing thing. The summit can also include:<\/span>\n<ul>\n<li class=\"li5\"><span class=\"s1\">Pre-spec brainstorming<\/span><\/li>\n<li class=\"li5\"><span class=\"s1\">Feedback with users<\/span><\/li>\n<li class=\"li5\"><span class=\"s1\">Be involved in strategic direction.<\/span><\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n<li class=\"li5\"><span class=\"s1\">Don\u2019t expect Ops at the PTG<\/span>\n<ul>\n<li class=\"li5\"><span class=\"s1\">The PTG has been designed for space to get stuff done. Unless a user is deep in code, they won\u2019t be there. If you want feedback from users, use the summit.<\/span><\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n<li><span class=\"s1\">For ops-focused teams like Kolla, participating at OpenStack summits and Ops mid cycles are essential. Not everyone has to go to every event though. These teams should organize who is going to what events.<\/span><\/li>\n<li class=\"li5\"><span class=\"s1\">If you\u2019re going to the summit in Barcelona, Thierry and Erin from the OpenStack Foundation will be hosting informational presentation on the PTG <a href=\"https:\/\/www.openstack.org\/summit\/barcelona-2016\/summit-schedule\/events\/17383\/project-teams-gathering-101\"><span class=\"s3\">[8]<\/span><\/a>.<\/span><\/li>\n<li class=\"li5\"><span class=\"s1\"><a href=\"http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2016-October\/thread.html#105524\">Full thread<\/a><\/span><\/li>\n<\/ul>\n<h1 class=\"p4\"><span class=\"s1\"><b>Next PTL\/TC Elections Timeframes<\/b><\/span><\/h1>\n<ul>\n<li class=\"li5\"><span class=\"s1\">At the last TC meeting, TC members discussed future election period, with consideration of the OpenStack Summit and Project Teams Gathering.<\/span><\/li>\n<li class=\"li5\"><span class=\"s1\">The TC charter which uses \u201cDesign Summit\u201d and \u201cSummit\u201d interchangeably is no longer valid and requires change.<\/span>\n<ul>\n<li class=\"li5\"><span class=\"s1\">There was a focus on limiting the impact change to avoid the need to modify the Foundation bylaws <a href=\"https:\/\/review.openstack.org\/#\/c\/385951\/\"><span class=\"s3\">[9]<\/span><\/a>.<\/span><\/li>\n<li class=\"li5\"><span class=\"s1\">PTL elections would continue to be organized around development cycle boundaries.<\/span><\/li>\n<li class=\"li5\"><span class=\"s1\">TC elections would continue to be organized relative to OpenStack Summit dates.<\/span><\/li>\n<\/ul>\n<\/li>\n<li class=\"li5\"><span class=\"s1\"><a href=\"http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2016-October\/105715.html\">Full thread<\/a><\/span><\/li>\n<\/ul>\n<h1 class=\"p4\"><span class=\"s1\"><b>Running Non-Devstack Jobs in Python Projects<\/b><\/span><\/h1>\n<ul>\n<li class=\"li5\"><span class=\"s1\">Devstack is the common tool to deploy OpenStack in CI environments.<\/span>\n<ul>\n<li class=\"li5\"><span class=\"s1\">However, it doesn\u2019t deploy OpenStack in production versus tools like Kolla, Fuel, TripleO, etc.<\/span><\/li>\n<\/ul>\n<\/li>\n<li class=\"li5\"><span class=\"s1\">Things might (and did) break when deploying OpenStack outside of Devstack:<\/span>\n<ul>\n<li class=\"li5\"><span class=\"s1\">SSL was not tested. Some projects still don\u2019t test with SSL enabled.<\/span><\/li>\n<li class=\"li5\"><span class=\"s1\">IPv6 is not tested everywhere.<\/span><\/li>\n<li class=\"li5\"><span class=\"s1\">Production scenarios with HA (HAproxy and\/or Pacemaker) are not tested.<\/span><\/li>\n<\/ul>\n<\/li>\n<li class=\"li5\"><span class=\"s1\">Proposal:<\/span>\n<ul>\n<li class=\"li5\"><span class=\"s1\">This is not about removing Devstack. The idea is to add more coverage in an interactive way.<\/span><\/li>\n<li class=\"li5\"><span class=\"s1\">Projects like TripleO and Heat have been added as CI jobs in the experimental pipeline.<\/span><\/li>\n<li class=\"li5\"><span class=\"s1\">A draft document about increasing coverage in different projects <a href=\"https:\/\/docs.google.com\/spreadsheets\/d\/1bLg-uEGrQXyRZ-FuR6pf1WT4XN0-6MrlfqEShI7xMxg\/edit#gid=0\"><span class=\"s3\">[10]<\/span><\/a>.<\/span><\/li>\n<\/ul>\n<\/li>\n<li class=\"li5\"><span class=\"s1\">Finding a balance between enough testing and overusing infra resources is tricky.<\/span>\n<ul>\n<li class=\"li5\"><span class=\"s1\">Also anything that\u2019s more complicated than unit tests has &gt; 0% chance of failure.<\/span><\/li>\n<\/ul>\n<\/li>\n<li class=\"li5\"><span class=\"s1\">Another proposal:<\/span>\n<ul>\n<li class=\"li5\"><span class=\"s1\">Running periodic testing and moving forward reference hashes everyday if tests pass.<\/span>\n<ul>\n<li class=\"li5\"><span class=\"s1\">Allows deployment tools to move forward automatically.<\/span><\/li>\n<li class=\"li5\"><span class=\"s1\">Quite close to master, but not tightly coupled into every change.<\/span><\/li>\n<li class=\"li5\"><span class=\"s1\">This is pretty much what the OpenStack-Ansible project does for its \u201cintegrated build\u201d.<\/span><\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n<li class=\"li5\"><span class=\"s1\"><a href=\"http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2016-October\/thread.html#105696\">Full thread<\/a><\/span><\/li>\n<\/ul>\n<p class=\"lead\">&nbsp;<\/p>\n<p class=\"p5\"><span class=\"s1\">[1] &#8211; <a href=\"http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2016-October\/105299.html\"><span class=\"s3\">http:\/\/lists.openstack.org\/pipermail\/openstack-dev\/2016-October\/105299.html<\/span><\/a><\/span><\/p>\n<p class=\"p5\"><span class=\"s1\">[2] &#8211; <a href=\"http:\/\/blog.leafe.com\/bias\/\"><span class=\"s3\">http:\/\/blog.leafe.com\/bias\/<\/span><\/a><\/span><\/p>\n<p class=\"p5\"><span class=\"s1\">[3] &#8211; <a href=\"https:\/\/wiki.openstack.org\/wiki\/UX#Participate_in_a_usability_study_being_conducted_at_the_Barcelona_Summit.21\"><span class=\"s3\">https:\/\/wiki.openstack.org\/wiki\/UX#Participate_in_a_usability_study_being_conducted_at_the_Barcelona_Summit.21<\/span><\/a><\/span><\/p>\n<p class=\"p5\"><span class=\"s1\">[4] &#8211; <a href=\"http:\/\/eavesdrop.openstack.org\/meetings\/api_wg\/\"><span class=\"s3\">http:\/\/eavesdrop.openstack.org\/meetings\/api_wg\/<\/span><\/a><\/span><\/p>\n<p class=\"p5\"><span class=\"s1\">[5] &#8211; <a href=\"https:\/\/review.openstack.org\/#\/c\/364460\/\"><span class=\"s3\">https:\/\/review.openstack.org\/#\/c\/364460\/<\/span><\/a><\/span><\/p>\n<p class=\"p5\"><span class=\"s1\">[6] &#8211; <a href=\"https:\/\/review.openstack.org\/#\/c\/383862\/\"><span class=\"s3\">https:\/\/review.openstack.org\/#\/c\/383862\/<\/span><\/a><\/span><\/p>\n<p class=\"p5\"><span class=\"s1\">[7] &#8211; <a href=\"https:\/\/www.openstack.org\/ptg\"><span class=\"s3\">https:\/\/www.openstack.org\/ptg<\/span><\/a><\/span><\/p>\n<p class=\"p5\"><span class=\"s1\">[8] &#8211; <a href=\"https:\/\/www.openstack.org\/summit\/barcelona-2016\/summit-schedule\/events\/17383\/project-teams-gathering-101\"><span class=\"s3\">https:\/\/www.openstack.org\/summit\/barcelona-2016\/summit-schedule\/events\/17383\/project-teams-gathering-101<\/span><\/a><\/span><\/p>\n<p class=\"p5\"><span class=\"s1\">[9] &#8211; <a href=\"https:\/\/review.openstack.org\/#\/c\/385951\/\"><span class=\"s3\">https:\/\/review.openstack.org\/#\/c\/385951\/<\/span><\/a><\/span><\/p>\n<p class=\"p5\"><span class=\"s1\">[10] &#8211; <a href=\"https:\/\/docs.google.com\/spreadsheets\/d\/1bLg-uEGrQXyRZ-FuR6pf1WT4XN0-6MrlfqEShI7xMxg\/edit#gid=0\"><span class=\"s3\">https:\/\/docs.google.com\/spreadsheets\/d\/1bLg-uEGrQXyRZ-FuR6pf1WT4XN0-6MrlfqEShI7xMxg\/edit#gid=0<\/span><\/a><\/span><\/p>\n","protected":false},"excerpt":{"rendered":"<p>SuccessBot Says loquacities: Newton docs are live on docs.openstack.org! Way to go docs team \\o\/ dhellmann: OpenStack Newton is officially released! tristanC: 6 TC members elected for Ocata [1]. dulek: Cinder gate is now voting on basic rolling upgrades support. One step closer to get assert:supports-rolling-upgrade tag. \ud83d\ude42 More Thoughts on the TC Election Process&#8230;  <a href=\"https:\/\/www.openstack.org\/blog\/openstack-developer-mailing-list-digest-20161014\/\" class=\"more-link\" title=\"Read OpenStack Developer Mailing List Digest October 8-14\">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\/7915"}],"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=7915"}],"version-history":[{"count":4,"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/posts\/7915\/revisions"}],"predecessor-version":[{"id":7919,"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/posts\/7915\/revisions\/7919"}],"wp:attachment":[{"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/media?parent=7915"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/categories?post=7915"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/tags?post=7915"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}