- Release schedule clarification after Ocata 
- Nova placement/resource providers 
- Stuart McLaren stepping down from glance core 
Allowing Teams Based on Vendor-specific Drivers (cont) 
- Narrowed down options at last TC meeting to following :
- Soft black (option 2): default option, had no negative feedback, represents the current status quo
- Soft white (option 4): had some positive feedback, folks liked it’s simple solution
- Grey (option 5): had the most positive feedback, but also the least amount of detail
- Other options’ patches are being abandoned
- Leaning towards an amended version of the ‘Grey’ proposal 
Community Goals for Pike (cont.) 
- Need feedback 
- Keep using openstack/governance for documenting goals
- Make sure to include guides
- Consider prioritization as it may not be possible to complete all the goals in the release
- Think about splitting larger goals to things that can be accomplished in a single release
- Involving users/operators through the Product WG and start face to face discussions on the Forums
Python changes in OpenStack CI 
- Python3.4 on a Trusty VM for older branches: stable/liberty and stable/mitaka
- Python3.5 on a Xenial VM for newer branches: stable/newton and master
- Python3.4 testing is disabled for these
- Projects should enable voting for Python3.5 jobs or add them if they don’t exist yet
- Projects should remove Python3.4 jobs if they run only on master
Golang Technical Requirements 
- Activities to adopt Go into OpenStack are ongoing
- Areas need more discussion
- Common Libraries
- Dependency Management
- Candidates are govendor, glide and godep
- Release Deliverables
- Tags and/or build artifacts?
- AUTHORS and ChangeLog files can be autogenerated
- Oaktree has golang bindings and contains generated files
Upgrade readiness check in Nova 
- New, separate service
- Checks the system state and indicates how much it is ready to start the Ocata upgrade (success, warning, error)
Self-service branch management 
- Through openstack/releases repo
- Specify your needs in a patch  and the rest is automated after it’s merged
- New stable branch creation is best to happen close to the end of the cycle, when the bug fixing and stabilization activities are slowing down
Architectural discussion about nova-compute interactions 
- How do Nova, Neutron and Cinder interact with nova-compute
- Should nova-compute become a standalone shared service? 
- Nova placement/resource providers update with some discussions on aggregates and API 
- New Nova core reviewer: Stephen Finucane 
- Project mascots are all around the mailing list, search for “logo” in the subject to find them
- Status update on unsupported Ironic drivers 
- The DefCore Committee is now called Interop Working Group 
Creating a New IRC Meeting Room 
- Create a new channel: #openstack-meeting-5
- Generally recommend project teams to use the meeting channels on Freenode
- Let projects use their channels for the meetings, but only if the channel is logged
- As a next step limit the official meeting rooms for official projects and have non-official projects using their own IRC channels
Neutron Trunk port feature
- Clarifying some usability aspects 
- Performance measurements 
Ocata Bugsmash Day 
- Thanks to Huawei and Intel and all the attendees to make it happen
- Let’s keep the tradition and grow the event further if we can
PTG Travel Support Program 
- Deadline of the first phase is this week
- Phase two deadline is January 15th
- Also reminding you to register to the event if you can come, but haven’t done it yet 
Finish test job transition to Ubuntu Xenial 
- Merged at last! 
- A lot of experimental and non votings jobs had to be updated
- Changes to Master no longer run on trusty
- Might have missed things still, so keep a look out
Want to attend the OpenStack Summit Boston but need help with the right words for getting your trip approved? While we won’t write the whole thing for you, here’s a template to get you going. It’s up to you to decide how the Summit will help your team, but with free workshops and trainings, technical sessions, strategy talks and the opportunity to meet thousands of likeminded Stackers, we don’t think you’ll have a hard time finding an answer.
I would like to attend the OpenStack Summit in Boston, May 8-11, 2017. The OpenStack Summit is the largest open source conference in North America, and the only one where I can get free OpenStack training, learn how to contribute code upstream to the project, and meet with other users to learn how they’ve been using OpenStack in production. The Summit is an opportunity for me to bring back knowledge about [Why you want to attend! What are you hoping to learn? What would benefit your team?] and share it with our team, while helping us get to know similar OpenStack-minded teams around the world (think 60+ countries and nearly 1,200 companies represented).
If I register before mid-March, I get early bird pricing–$600 USD for 4 days (plus an optional day of training). Early registration also allows me to RSVP for trainings and workshops as soon as they open (they always sell out!), or sign up to take the Certified OpenStack Administrator exam onsite.
At the OpenStack Summit Austin last year, over 7,800 attendees heard case studies from Superusers like AT&T and China Mobile, learned how teams are using containers and container orchestration like Kubernetes with OpenStack, and gave feedback to Project Teams about user needs for the upcoming software release. You can browse past Summit content at openstack.org/videos to see a sample of the conference talks.
The OpenStack Summit is the opportunity for me to expand my OpenStack knowledge, network and skills. Thanks for considering my request.
- Nova Resource Providers update 
- Nova blueprints update 
- OpenStack-Ansible deploy guide live! 
The Future of OpenStack Needs You 
- Need more mentors to help run Upstream Trainings at the summits
- Interested in doing an abridged version at smaller more local events
- Contact ildikov or diablo_rojo on IRC if interested
New project: Nimble 
- Interesting chat about bare metal management
- The project name is likely to change
Community goals for Pike 
- As Ocata is a short cycle it’s time to think about goals for Pike 
- Or give feedback on what’s already started 
Exposing project team’s metadata in README files (Cont.) 
- Amrith agrees with the value of Flavio’s proposal that a short summary would be good for new contributors
- Will need a small API that will generate the list of badges
- Done- as a part of governance
- Just a graphical representation of what’s in the governance repo
- Do what you want with the badges in README files
- Patches have been pushed to the projects initiating this change
Allowing Teams Based on Vendor-specific Drivers 
Cirros Images to Change Default Password 
- New password: gocubsgo
- Not ‘cubswin:)’ anymore
- Discussion started about adding end-user focused test suits to test OpenStack clusters beyond what’s already available in Tempest 
- Feedback is needed from users and operators on what preferred scenarios they would like to see in the test suite 
- You can read more in the spec for High Availability testing  and the user story describing destructive testing  which are both on review
Events discussion 
- Efforts to remove duplicated functionality from OpenStack in the sense of providing event information to end-users (Zaqar, Aodh)
- It is also pointed out that the information in events can be sensitive which needs to be handled carefully
- Nova placement/resource provider work 
- New release-announce list and other changes to openstack-announce 
- Formal Discussion of Documenting Upgrades
- Stewardship Working Group description/update 
- OpenStack Liberty has reached EOL 
- Switching test jobs from Ubuntu Trusty to Xenial on the gate is happening on December 6th 
A Continuously Changing Environment:
- We have core developers who’ve been around for a long while stepping down and giving the opportunity to the “next generation” to take on the responsibility of leadership
- Thank you for your presence, for teaching and for showing other contributors a good example by embracing open source and OpenStack
- Andrew Laski (Nova): “As I’ve told people many times when they ask me what it’s like to work on an open source project like this: working on proprietary software exposes you to smart people but you’re limited to the small set of people within an organization, working on a project like this exposed me to smart people from many companies and many parts of the world. I have learned a lot working with you all. Thanks.”
- Carl Baldwin (Neutron): “This is a great community and I’ve had a great time participating and learning with you all.”
- Marek Denis (Keystone): “It’s been a great journey, I surely learned a lot and improved both my technical and soft skills.”
- Thank you for all your hard work!
Community goals for Ocata:
- Starting with the Newton, our community commits to release goals in order to provide the minimum level of consistency and user experience and to improve certain areas OpenStack-wide 
- The goal is to remove all remaining incubated Oslo code in Ocata
Unit Test Setup Changes :
- Attempt to remove DB dependency from the unit test jobs
- Special DB jobs still exist to provide workaround where needed along with a script in ‘tools/test-setup.sh’
- Long term goal is for projects to not use the -db jobs anymore, new changes for them should not be accepted.
Project Info in README Files 
- Increase visibility of fundamental project information that is already available on the governance web site 
- Badges are automatically generated as part of the governance CI 
- Every project is strongly recommended to use this new system to provide information about
- The project’s state (in Big Tent or not, etc.)
- Project tags
- Project capabilities
- 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 .
- dulek: Cinder gate is now voting on basic rolling upgrades support. One step closer to get assert:supports-rolling-upgrade tag. 🙂
Thoughts on the TC Election Process
- When deciding to run, candidates write a long thoughtful essay on their reasons for wanting to serve on the TC.
- It is rare for anyone to ask follow-up question, or to challenge the candidates to explain their position more definitively.
- Some people pick by names they are most familiar with and don’t read those candidacy posts.
- It is believed that it’s rare for someone who hasn’t been a PTL of a large project to be elected.
- An example of implicit bias, blind auditions for musical orchestras radically changing the selection results .
- Proposal: have candidates self-nominate, but instead of a long candidacy letter, just state their interests in serving.
- After nominations close, the election officials will assign each candidate with a non-identifying label (e.g. random number).
- Candidates will post their thoughts and positions and respond to questions from people.
- Candidacy essay would be posted in the campaign period, instead of the nomination period. This will exclude biographical information.
- Perhaps candidates can forward their responses to election officials, who will post them for the candidates and identify only by candidate number.
- The voting form will only list the candidates’ numbers.
- Thoughts on the proposal:
- Not allowing people to judge peoples’ 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.
- It can be important to identify candidates. For some people, there’s a difference in what they say, and what they end up doing when left calling the shots.
- Familiarity doesn’t necessarily equal bias. Trust is not bias.
- A good example  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.
- We need several things:
- Allow time between the nomination and the voting. Some candidates don’t announce until the last day or two. This doesn’t allow much time to get to know them.
- How to deal with timezone differences. One candidate may post an answer early and get more reaction.
- Reduce the effect of incumbency.
- 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.
- The job of the TC is:
- Putting the best interests of OpenStack at heart.
- Be effective in working with a diverse set of folks in our community to get things done.
- To find areas of friction and remove them.
- Help set the overall direction for the project that community accepts.
- Writing a good candidacy email isn’t really good representation of those abilities. It’s the measure of writing a good candidacy email, in English.
- Sean Dague hopes that when voters vote in the election that they are taking the reputation of individuals into account.
- Look at the work they did across all of OpenStack.
- How they got consensus on items.
- What efforts they are able to get folks to rally around and move forward.
- When they get stuck and get unstuck.
- When they ask for help and/or admit they’re out of their element.
- How they help new folks.
- How they work with long timers.
- It’s 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.
- Full thread
API Workgroup News
- API usability tests being conducted at the Barcelona summit .
- Two lively discussions :
- Collecting and improving error messages across OpenStack.
- Request semantics with regards to GET and body processing.
- New guidelines:
- Add a warning about JSON expectations .
- Guidelines currently under review:
- Specify time intervals based filtering queries .
- Full thread
Project Teams Gathering from the Ops Perspective
- The first PTG will be held February 20-24 in Atlanta, GA at the downtown Sheraton hotel.
- Tickets are $100.
- Group rate is $185/night.
- Registration will go live in the next couple of weeks.
- Horizontal/cross project teams will meet Monday and Tuesday.
- Vertical projects will meet Wednesday through Friday.
- There’s a lot of great planning happening around the PTG planning, however, it’s going take some time for operators to figure it out.
- Tom Fifield gives some notes for the operators:
- Check out the diagram on the PTG site .
- We’re finally acknowledging a release cycle starts with planning. Now we’ll be finalizing a release, while planning another.
- This puts the summit at the right place to get feedback and decent ideas from users.
- The OpenStack summit is the place the entire community gets together.
- The PTG doesn’t mean the summit becomes a marketing thing. The summit can also include:
- Pre-spec brainstorming
- Feedback with users
- Be involved in strategic direction.
- Don’t expect Ops at the PTG
- The PTG has been designed for space to get stuff done. Unless a user is deep in code, they won’t be there. If you want feedback from users, use the summit.
- 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.
- If you’re going to the summit in Barcelona, Thierry and Erin from the OpenStack Foundation will be hosting informational presentation on the PTG .
- Full thread
Next PTL/TC Elections Timeframes
- At the last TC meeting, TC members discussed future election period, with consideration of the OpenStack Summit and Project Teams Gathering.
- The TC charter which uses “Design Summit” and “Summit” interchangeably is no longer valid and requires change.
- There was a focus on limiting the impact change to avoid the need to modify the Foundation bylaws .
- PTL elections would continue to be organized around development cycle boundaries.
- TC elections would continue to be organized relative to OpenStack Summit dates.
- Full thread
Running Non-Devstack Jobs in Python Projects
- Devstack is the common tool to deploy OpenStack in CI environments.
- However, it doesn’t deploy OpenStack in production versus tools like Kolla, Fuel, TripleO, etc.
- Things might (and did) break when deploying OpenStack outside of Devstack:
- SSL was not tested. Some projects still don’t test with SSL enabled.
- IPv6 is not tested everywhere.
- Production scenarios with HA (HAproxy and/or Pacemaker) are not tested.
- This is not about removing Devstack. The idea is to add more coverage in an interactive way.
- Projects like TripleO and Heat have been added as CI jobs in the experimental pipeline.
- A draft document about increasing coverage in different projects .
- Finding a balance between enough testing and overusing infra resources is tricky.
- Also anything that’s more complicated than unit tests has > 0% chance of failure.
- Another proposal:
- Running periodic testing and moving forward reference hashes everyday if tests pass.
- Allows deployment tools to move forward automatically.
- Quite close to master, but not tightly coupled into every change.
- This is pretty much what the OpenStack-Ansible project does for its “integrated build”.
- Full thread
 – http://lists.openstack.org/pipermail/openstack-dev/2016-October/105299.html
 – http://blog.leafe.com/bias/
 – https://wiki.openstack.org/wiki/UX#Participate_in_a_usability_study_being_conducted_at_the_Barcelona_Summit.21
 – http://eavesdrop.openstack.org/meetings/api_wg/
 – https://review.openstack.org/#/c/364460/
 – https://review.openstack.org/#/c/383862/
 – https://www.openstack.org/ptg
 – https://www.openstack.org/summit/barcelona-2016/summit-schedule/events/17383/project-teams-gathering-101
 – https://review.openstack.org/#/c/385951/
 – https://docs.google.com/spreadsheets/d/1bLg-uEGrQXyRZ-FuR6pf1WT4XN0-6MrlfqEShI7xMxg/edit#gid=0
Candidate Proposals for TC are now open
- Candidate proposals for the Technical committee (6 positions) are open and will remain open until 2016-10-01, 23:45 UTC.
- Candidacies must submit a text file to the openstack/election repository .
- Candidates for the Technical Committee can be any foundation individual member, except the seven TC members who were elected for a one year seat in April .
- The election will be held from October 3rd through to 23:45 October 8th.
- The electorate are foundation individual members that are committers to one of the official programs projects  over the Mitaka-Newton timeframe (September 5, 2015 00:00 UTC to September 4, 2016 23:59 UTC).
- Current accepted candidates 
- Full thread
Release countdown for week R-0, 3-7 October
- Focus: Final release week. Most project teams should be preparing for the summit in Barcelona.
- General notes:
- Release management team will tag the final Newton release on October 6th.
- Project teams don’t have to do anything. The release management team will re-tag the commit used in the most recent release candidate listed in openstack/releases.
- Projects not following the milestone model will not be re-tagged.
- Cycle-trailing projects will be skipped until the trailing deadline.
- Release actions
- Projects not follow the milestone-based release model who want stable/newton branches created should talk to the release team about their needs. Unbranched projects include:
- Important dates:
- Newton final release: October 6th
- Newton cycle-trailing deadline: October 20th
- Ocata Design Summit: October 24-28
- Full thread
Removal of Security and OpenStackSalt Project Teams From the Big Tent (cont.)
- The change to remove Astara from the big tent was approval by the TC .
- The TC has appointed Piet Kruithof as PTL of the UX team .
- Based on the thread discussion  and engagements of the team, the Security project team will be kept as is and Rob Clark continuing as PTL .
- The OpenStackSalt team did not produce any deliverable within the Newton cycle. The removal was approved by the current Salt team PTL and the TC .
- Full thread
 – http://governance.openstack.org/election/#how-to-submit-your-candidacy
 – https://wiki.openstack.org/wiki/TC_Elections_April_2016#Results
 – http://git.openstack.org/cgit/openstack/governance/tree/reference/projects.yaml?id=sept-2016-elections
 – https://review.openstack.org/#/c/376609/
 – http://eavesdrop.openstack.org/meetings/tc/2016/tc.2016-09-27-20.01.html
 – http://lists.openstack.org/pipermail/openstack-dev/2016-September/thread.html#104170
 – http://eavesdrop.openstack.org/meetings/tc/2016/tc.2016-09-27-20.01.html
 – https://review.openstack.org/#/c/377906/
- A MQTT based unified message bus for infra services.
- This allows a single place to go for consuming messages of events from infra services.
- Two interfaces for subscribing to topics:
- MQTT protocol on the default port
- Websockets over port 80
- Launchpad and gerrit events are the only things currently sending message to firehose, but the plan is to expand this.
- An example  of gerritbot on the consuming side, which has support for subscribing to gerrit event stream over MQTT.
- A spec giving details on firehose .
- Docs on firehose .
Release countdown for week R-1, 26-30
- Focus: All teams should be working on release-critical bugs before the final release.
- 29th September is the deadline for the new release candidates or release from intermediary projects.
- Quiet period to follow before the last release candidates on 6th October.
- Release actions:
- Projects not following the milestone-based release model who want a stable/newton branch created should talk to the release team.
- Watch for translation patches and merge them quickly to ensure we have as many user-facing strings translated as possible in the release candidates.
- If your project has already been branched, make sure those patches are applied to the stable branch.
- Liaisons for projects with independent deliverables should import the release history by preparing patches to openstack/release.
- Important Dates:
- Newton last RC, 29 September
- Newton final release, 6 October
- Newton release schedule 
- Full thread
Removal of Security and OpenStackSalt Project Teams From the Big Tent
- The Security and OpenStackSalt projects are without PTLs. Projects leaderless default to the Technical Committee for decision of what to do with the project . Majority of the Technical Committee has agreed to have these projects removed.
- OpenStackSalt is a relatively new addition to the Big Tent, so if they got their act together, they could be reproposed.
- We still need to care about security., and we still need a home for the vulnerability management team (VMT). The suggested way forward is to have the VMT apply to be its own official project team, and have security be a working group.
- The Mitaka PTL for the Security mentions missing the election date, but provides some things the team has been working on:
- Issuing Security Notes for Glance, Nova, Horizon, Bandit, Neutron and Barbican.
- Updating the security guide (the book we wrote on securing OpenStack)
- Hosting a midcycle and inducting new members
- Supporting the VMT with several embargoed and complex vulnerabilities
- Building up a security blog
- Making OpenStack the biggest open source project to ever receive the Core
- Infrastructure Initiative Best Practices Badge
- Working on the OpenStack Security Whitepaper
- Developing CI security tooling such as Bandit
- One of the Technical Committee members privately received information that explains why the security PTL was not on top of things. With ~60 teams around there will always be one of two that miss, but here we’re not sure it passes the bar of “non-alignment with the community” that would make the security team unfit to be an official OpenStack Team.
- Full thread
 – http://git.openstack.org/cgit/openstack-infra/gerritbot/commit/?id=7c6e57983d499b16b3fabb864cf3b
 – http://specs.openstack.org/openstack-infra/infra-specs/specs/firehose.html
 – http://docs.openstack.org/infra/system-config/firehose.html
 – http://releases.openstack.org/newton/schedule.html
 – http://docs.openstack.org/project-team-guide/open-community.html#technical-committee-and-ptl-elections