- dims 1: Rally running against Glance (Both Rally and Glance using py3.5).
- AJaegar 2: docs.openstack.org is served from the new Infra file server that is AFS based.
- jd 3: Gnocchi 3.1 will be shipped with an empty /etc and will work without any config file by default.
- cdent 4 : edleafe found narrowed down an important bug in gabbi.
- Tell us yours via OpenStack IRC channels with message “#success <message>”
Return of the Architecture Working Group
- Meeting times Alternate, even weeks Thursday at 20:00UTC, odd weeks Thursday at 01:00UTC
- Currently two proposes:
- “Base Services” proposal 5 recognizes components leveraging features from external services that OpenStack components can assume will be present. Two kinds:
- Local (like a hypervisor on a compute node)
- Global (like a database)
- “Nova Compute API” proposal 6 breaking nova-compute out of Nova itself.
- Full thread
Restarting Service-types-authority / service catalog work
- In anticipation of having a productive time in Atlanta for the PTG, various patches have been refreshed 7.
- Two base IASS services aren’t in the list yet because of issues:
- Neutron / network – discrepancy between common use of “network” and “networking” in the API reference URL. Other services in the list have the service-type and the URL name for the API reference are the same.
- Cinder / volume – Moving forward from using volumev2 and volumev3 in devstack.
- Full thread
Feedback From Driver Maintainers About Future of Driver Projects
- Major observations
- Yes drivers are an important part of OpenStack.
- Discoverability of drivers needs to be fixed immediately.
- It’s important to have visibility in a central place of the status of each driver.
- Both driver developer and a high level person at a company should feel they’re part of something.
- Give drivers access to publish to docs.openstack.org.
- What constitutes a project was never for drivers. Drivers are part part of the project. Driver developers contribute to OpenStack by creating drivers.
- Consensus: it is currently all over the place 8 9 10.
- There should be CI results available.
- Discoverability can be fixed independently of governance changes.
- Driver projects official or not?
- Out-of-tree vendors have a desire to become “official” OpenStack projects.
- Opinion: let driver projects become official without CI requirements.
- Opinion: Do not allow drivers projects to become official, that doesn’t mean they shouldn’t easily be discoverable.
- Opinion: We don’t need to open the flood gates of allowing vendors to be teams in the OpenStack governance to make the vendors developers happy.
- Fact: This implies being placed under the TC oversight. It is a significant move that could have unintended side-effects, it is hard to reverse (kicking out teams we accepted is worse than not including them in the first place), and our community is divided on the way forward. So we need to give that question our full attention and not rush the answer.
- Opinion: Consider driver log 11 an official OpenStack project to be listed under governance with a PTL, weekly meetings, and all that it required to allow the team to be effective in their mission of keeping the marketplace a trustworthy resource for learning about OpenStack driver ecosystem.
- Driver Developers:
- Opinion: A driver developer that ONLY contributes to vendor specific driver code should not have the same influence as other OpenStack developers, voting for PTL, TC, and ATC status.
- Opinion: PTLs should leverage the extra-atcs option in the governance repo.
- In-tree VS out-of-tree
- Cinder has in-tree drivers, but also has out-of-tree drivers when their CI is not maintained or when minimum feature requirements are not met. They are marked as ‘not supported’ and have a single release to get things working before being moved out-of-tree.
- Ironic has a single out-of-tree repo 12 — But also in-tree 13
- Neutron has all drivers out-of-tree, with project names like: ‘networking-cisco’.
- Many opinions on the “stick-based” approach the cinder team took.
- Opinion: The in-tree vs out-of-tree argument is developer focused. Out-of-tree drivers have obvious benefits (develop quickly, maintain their own team, no need for a core to review the patch). But a vendor that is looking to make sure a driver is supported will not be searching git repos (goes back to discoverability).
- Opinion: May be worth handling the projects that keep supported drivers in-tree differently that we handle projects that have everything out-of-tree.
- Full thread
- Guidelines currently under review:
- Add guidelines on usage of state vs. status 14
- Add guidelines for boolean names 15
- Clarify the status values in versions 16
- Define pagination guidelines 17
- Add API capabilities discovery guideline 18
- Add guideline for invalid query parameters 19
- Full thread
New Deadline for PTG Travel Support Program
- Help contributors that are not otherwise funded to join their project team gathering 20
- Originally the application acceptance was set to close January 15, but it’s now extended to the end-of-day Tuesday January 17th.
- Apply now if you need it! 21
- Submissions will be evaluated next week and grantees will be notified by Friday, January 20th.
- Register for the event 22 if you haven’t yet. Prices will increase on January 24 and February 14.
- If you haven’t already booked your hotel yet, do ASAP in the event hotel itself using the PTG room block. This helps us keep costs under control and helps share the most time with the event participants.
- Closes January 27
- Book now 23
- Full thread
Release Countdown For Week R-5
- Feature work and major refactoring be starting to wrap up as we approach the the third milestone.
- Release Tasks:
- stable/ocata branches will be created and configured with a small subset of the core review team. Release liaisons should ensure that these groups exist and the membership is correct.
- General Notes:
- We will start the soft string freeze during R-4 (Jan 23-27) 24
- Subscribe to the release calendar with your favorite calendaring software 25
- Important Dates:
- Final release for non-client libraries: January 19
- Ocata 3 milestone with feature and requirements freeze: January 26
- Ocata release schedule 26
- Full thread
 – http://eavesdrop.openstack.org/irclogs/%23openstack-glance/%23openstack-glance.2017-01-09.log.html
 – http://eavesdrop.openstack.org/irclogs/%23openstack-infra/%23openstack-infra.2017-01-10.log.html
 – http://eavesdrop.openstack.org/irclogs/%23openstack-telemetry/%23openstack-telemetry.2017-01-11.log.html
 – http://eavesdrop.openstack.org/irclogs/%23openstack-nova/%23openstack-nova.2017-01-12.log.html
 – http://git.openstack.org/cgit/openstack/arch-wg/tree/proposals/base-services.rst
 – https://review.openstack.org/#/c/411527/1
 – https://review.openstack.org/#/c/286089/
 – http://docs.openstack.org/developer/cinder/drivers.html
 – http://docs.openstack.org/developer/nova/support-matrix.html
 – http://stackalytics.openstack.org/report/driverlog
 – http://git.openstack.org/cgit/openstack/driverlog
 – https://git.openstack.org/cgit/openstack/ironic-staging-drivers
 – http://git.openstack.org/cgit/openstack/ironic/tree/ironic/drivers
 – https://review.openstack.org/#/c/411528/
 – https://review.openstack.org/#/c/411529/
 – https://review.openstack.org/#/c/411849/
 – https://review.openstack.org/#/c/390973/
 – https://review.openstack.org/#/c/386555/
 – https://review.openstack.org/417441
 – http://www.openstack.org/ptg#tab_travel
 – https://openstackfoundation.formstack.com/forms/travelsupportptg_atlanta
 – https://pikeptg.eventbrite.com/
 – https://www.starwoodmeeting.com/events/start.action?id=1609140999&key=381BF4AA
 – https://releases.openstack.org/ocata/schedule.html#o-soft-sf
 – https://releases.openstack.org/schedule.ics
 – http://releases.openstack.org/ocata/schedule.html
- AJaeger: We’ve now got the first Deployment guide published for Newton, see http://docs.openstack.org/project-deploy-guide/newton/ . Congrats to OpenStack Ansible team!
- clarkb: OpenStack CI has moved off of Ubuntu Trusty and onto Ubuntu Xenial for testing Newton and master.
- ihrachys: first oslo.privsep patch landed in Neutron.
- dulek: Cinder now supports ZeroMQ messaging!
Release Countdown for Week R-8, 26-30 December
- Feature work and major refactoring should be well under way as we pass the second milestone.
- Deadline for non-client library releases is R-5 (19 Jan).
- Feature freeze exceptions are not granted for libraries.
- General Notes:
- Project teams should identify contributors that have a significant impact this cycle who not otherwise qualify for ATC status.
- Those names should be added to the governance repository for consideration as ATC.
- The list needs to be approved by the TC by 20 January to qualify for contributor discounts codes for the event.
- Submit these by 5 January
- Important Dates:
- Extra ATCs deadline: 5 January
- Final release of non-client libraries: 19 January
- Ocata 3 Milestone, with Feature and Requirements freezes: 26 January
- Ocata release schedule 
- Full thread
- There is movement to still move to Storyboard as our task tracker.
- To spread awareness, some blog posts have been made about it, and it’s capabilities:
- General over and decision to move from Launchpad .
- Next post will focus on compare and contrast of Launchpad and Storyboard.
- If you want to hear about something in particular in the blog posts, let the team know on #storyboard IRC channel on Freenode.
- Attend their weekly meeting .
- Try out Storyboard in the sandbox .
- Storyboard documentation 
- Full thread
 – http://releases.openstack.org/ocata/schedule.html
 – https://storyboard-blog.sotk.co.uk/why-storyboard-for-openstack.html
 – https://wiki.openstack.org/wiki/StoryBoard
 – https://storyboard-dev.openstack.org/
 – http://docs.openstack.org/infra/storyboard/
- 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