Summaries

• TC Report 39
• Release countdown for week R-21, September 29 – October 6
• Technical committee status update, September 29
• Placement/resource providers update 36
• POST /api-sig/news

Sydney Forum

General Links

• What the heck is the form?
• When: November 6-8, 2017
• Where: OpenStack Summit in Sydney Australia
• Register for The OpenStack Sydney Summit and show up!
• Deadline for topic sessions was September 29th UTC by this submission form.
• All Sydney Forum etherpads

Etherpads (copied from Sydney Forum wiki)

Catch-alls

If you want to post an idea, but aren’t working with a specific team or working group, you can use these:

• Technical Committee Catch-all
• User Committee Catch-all

Etherpads from Teams and Working Groups

• Nova
• Cinder
• Ops Meetups Team
• OpenStack Ansible
• Self-healing SIG
• Neutron Quality-Of-Service Discussion
• QA Team
• Watcher
• SIG K8s
• Kolla

Garbage Patches for Simple Typos Fixes

• There is some agreement that we as a community have to do something beyond mentoring new developers.
  • Others have mentioned that some companies are doing this to game the system in other communities besides OpenStack.
    • Gain: show a high contribution level was “low quality” patches.
  • Some people in the community want to put a stop to this figuratively with a stop sign, otherwise, things will never improve. If we don’t do something now we are hurting everyone, including those developers who could have done more meaningful contributions.
  • Others would like before we go into creating harsh processes, we need to collect the data to show other times to provide guidance I Have not worked.
  • We have a lot of anecdotal information right now that we need to collect and summarize.
  • If the results show that there are clear abuses, rather than misunderstandings, then we can use that data to design effective blocks without hurting other contributors or creating a reputation that our community is not welcoming.
• Some are unclear why there is so much outrage about these patches, to begin with. They are fixing real things.
  • Maybe there is a CI cost, but the faster they are merged the less likely someone is to propose it in the future which keeps the CI cost down.
  • If people are deeply concerned about CI resources, step one is to give us a better accounting into their existing system to see where resources are currently spent.
• Thread

Status of the Stewardship Working Group

• The stewardship working group was created after the first session of leadership training that the Technical Committee, User Committee, Board and other community members were invited to participate in 2016.
• Follow-up on what we learned at ZingTrain and push adoption of the tools we discovered there.
• While we did (and continue)
  • The activity of the workgroup mostly died when we decided to experiment getting rid of weekly meetings for greater inclusion.
  • Lost original leadership.
• The workgroup is dormant until someone steps up and leads it again.
• Join us on IRC Freenode in channel openstack-swg if interested.
• Message

Improving the Process for Release Marketing

• Release marketing is a critical heart for sharing what’s new with each release.
• Let’s work together on reworking how the marketing community and projects work together to make the release communications happen.
• Having multiple, repetitive demands to summarize” top features” during release time can be a pester, and having to recollect the information each time isn’t an effective use of time.
  • Being asked to make a polished, “Press–Friendly” message out of release can feel far outside of the PTL’s Focus areas or skills.
  • Technical content marketers, attempting to find the key features from release notes, mailing lists, specifications, roadmaps, whatever means interesting features are sometimes overlooked.
• To address this gap, the release team and foundation marketing team proposed collecting information as part of the release tagging process.
  • We will collect from deliverable files to provide highlights for the series (about three items).
  • The text will be used to build a landing page on release.openstack.org that shows the”Key features” flagged by PTL’s that the marketing teams should be looking at during release communication times.
    • This page will link to the release notes so marketers can gather additional information.
• Message

Simplification in OpenStack

• Two camps appear: people that want to see OpenStack as a product with a way of doing deployments and the people who want to focus on configuration management tools.
  • One person gives an example of using both Ubuntu MAAS and Puppet. The puppet solution allowed for using existing deployment methodologies unlike the former.
• We should start promoting and using a single solution for the bulk of the community efforts. Right now we do that with Devstack as a reference implementation that nobody should use for anything but dev/test.
  • This sort of idea could make other deployment efforts relevant.
• Kolla came up at the PTG: scenario-based testing and documentation based on different  “constellations” or use cases.
  • Puppet has been doing this and Triple-o has been doing this.
  • If you break down actual use cases, most people want nova (qemu+KVM), neutron (vxlan, potentially VLAN), Cinder (ceph).
    • If we agreed to cover 90% of users, that’ll boil down to 4 to 5 different “constellations.”
  • Someone has been working on a local testing environment, and it boils down to this.
• Thread

Summaries

• Technical Committee Status update
• POST /api-sig/news
• Release Countdown

PTG

Survey/polls

• Should we have Upstream Institutes at the PTG? yay or nay

Summaries

• Blazar
• Cross-project
  • Simplification in OpenStack etherpad
  • Skip Level Upgrades & Fast Forward Upgrades and thread
• Charms
• Cinder
  • Team photo
• Cyborg
• Docs and i18n
• Glance
  • Recaps:
    • Wednesday
    • Thursday
• Neutron
  • Videos
  • Team photo
• Nova
  • Recaps:
    • Cells
    • Placement
    • Nova and Neutron
    • Nova and Cinder
    • Everything else
  • Team photo
• Sahara
• Tricircle
• Triple-O
  • Triple-O and Ansible and thread
  • Team photo
• QA

Gerrit Upgrade Update From Infra

• Gerrit emails are slow, because it’s sending one at a time
  • Upstream bug
  • Patch to apply
• Web UI File Editor
  • Behaving oddly. Might be because of API time outs. Gertty is also having reported problems.
• Message

Install Guide VS Tutorial

• Since the doc-migration, people have been having questions regarding the usage of “Install Tutorial” and “Install Guide” in the OpenStack manuals repository and project specific repos.
  • The documentation team agrees this should be consistent.
  • Tutorial’s literal translation is “paper, book, film, or computer program that provide practical information about a specific subject.”
• From PTG discussions, a distinction made was installation provides one of many possible ways to install the components.
• Consistency is more important than bike shedding over the name.
  • Industry wise, what’s the trend?
• Thread

Garbage Patches for simple typo fixes

• Previous thread from 2016 on this
• Various contributors are doing many patches that are typo, style changes.
  • It has been expressed that this can cause CI resource starvation.
• TC created the Top 5 help wanted to help contributors know where the community needs the most identified help.
• This is a social issue, not a technical issue. Arguing about what is useful and what isn’t is probably not worth the effort here.
• Communication and education is probably the best solution here. For repeated offenders, off-list email could be fine to make sure the communication is clear. Communicating this in the new contributor portal and Upstream Institute would be helpful.
• Thread

Successbot Says!

• fungi: Octavia has migrated from Launchpad to StoryBoard [1]
• sc’ : OpenStack is now on the Chef Supermarket! https://supermarket.chef.io/users/openstack [2]

Summaries:

• Notifications Update Week 36 [3]

Updates:

• Summit Free Passes [4]
  • People that have attended the Atlanta PTG or will attend the Denver PTG will receive 100% discount passes for the Sydney Summit
  • They must be used by October 27th
• Early Bird Deadline for Summit Passes is September 8th [5]
  • Expires at 6:59 UTC
  • Discount Saves you 50%
• Libraries Published to pypi with YYY.X.Z versions [6]
  • Moving forward with deleting the libraries from Pypi
  • Removing these libraries:
    • python-congressclient 2015.1.0
    • python-congressclient 2015.1.0rc1
    • python-designateclient 2013.1.a8.g3a2a320
    • networking-hyperv 2015.1.0
  • Still waiting on approval from PTL’s about the others
    • mistral-extra
    • networking-odl
    • murano-dashboard
    • networking-midonet
    • sahara-image-elements
    • freezer-api
    • murano-agent
    • mistral-dashboard
    • Sahara-dashboard
• Unified Limits work stalled [7]
  • Need for new leadership
  • Keystone merged a spec [8]
• Should we continue providing FQDN’s for instance hostnames?[9]
  • Nova network has deprecated the option that the domain in the FQDN is based on
  • Working on getting the domain info from Neutron instead of Nova, but this may not be the right direction
  • Do we want to use a FQDN as the hostnames inside the guest?
    • The Infra servers are built with the FQDN as the instance name itself
• Cinder V1 API Removal[10]
  • Patch here[11]
• Removing Screen from Devstack- RSN
  • It’s been merged
  • A few people are upset that they don’t have screen for debugging anymore
  • Systemd docs are being updated to include pdb path so as to be able to debug in a similar way to how people used screen [12] [13] [14]

PTG Planning

• Video Interviews [15]

[1] http://eavesdrop.openstack.org/irclogs/%23storyboard/%23storyboard.2017-09-06.log.html#t2017-09-06T22:03:06

[2] http://eavesdrop.openstack.org/irclogs/%23openstack-chef/%23openstack-chef.2017-09-08.log.html#t2017-09-08T13:48:14

[3] http://lists.openstack.org/pipermail/openstack-dev/2017-September/121769.html

[4] http://lists.openstack.org/pipermail/openstack-dev/2017-September/121843.html #Free

[5] http://lists.openstack.org/pipermail/openstack-dev/2017-September/121847.html

[6] http://lists.openstack.org/pipermail/openstack-dev/2017-September/121705.html #YYYY

[7] http://lists.openstack.org/pipermail/openstack-dev/2017-September/121944.html

[8] https://specs.openstack.org/openstack/keystone-specs/specs/keystone/ongoing/unified-limits.html

[9] http://lists.openstack.org/pipermail/openstack-dev/2017-September/121762.html

[10] http://lists.openstack.org/pipermail/openstack-dev/2017-September/121956.html

[11] https://review.openstack.org/#/c/499342/

[12] https://review.openstack.org/#/c/501834/

[13] https://pypi.python.org/pypi/remote-pdb

[14] https://review.openstack.org/#/c/501870/

[15] http://lists.openstack.org/pipermail/openstack-dev/2017-September/121901.html

Succesbot Says!

• ttx: Pike is released! [21]
• ttx: Release automation made Pike release process the smoothest ever [22]

PTG Planning

• Monasca (virtual)[1]
• Vitrage(virtual)[2]
• General Info & Price Hike[3]
  • Price Goes up to $150 USD
  • Happy Hour from 5-6pm on Tuesday
  • Event Feedback during Lunch on Thursday
• Queens Goal Tempest Plugin Split [4]
• Denver City Guide [5]
  • Please add to and peruse
• ETSI NFV workshop[6][7]

Summaries

• TC Update [8]
• Placement/Resource Providers Update 34 [9]

Updates

• Pike is official! [10]
• Outreachy Call for Mentors and Sponsors! [11]
  • More info here[12]
  • Next round runs December 5th to March 5th
• Libraries published to pypi with YYYY.X.Z versions[13]
  • During Kilo when the neutron vendor decomposition happened, the release version was set to 2015.1.0 for basically all of the networking projects
  • Main issue is that networking-hyperv == 2015.1.0 is currently on Pypi and whenever someone upgrades through pip, it ‘upgrades’ to 2015.1.0 because its considered the latest version
  • Should that version be unpublished?
  • Three options[14]
    • Unpublish- simplest, but goes against policy of pypi never unpublishing
      • +1 from tonyb, made a rough list of others to unpublish that need to be confirmed with PTL’s before passing to infra to unpublish[15]
    • Rename- a bunch of work for downstreams, but cleaner than unpublishing
    • Reversion- Start new versions at 3000 or something, but very hacky and ugly
  • dhellman, ttx, and fungi think that deleting it from pypi is the simplest route though not the typically recommended way of handling things
• Removing Screen from devstack-RSN[16]
  • Work to make devstack only have a single execution mode- same between automated QA & local- is almost done!
  • Want to merge before PTG
  • Test your devstack plugins against this patch before it gets merged
  • Patch [17]
• Release Countdown for week R+1 and R+2[18]
  • Still have release trailing deliverables to take care of
  • Need to post their Pike final release before the cycle-trailing release deadline (September 14th)
  • Join #openstack-release if you have questions
  • ttx passes RelMgmgt mantle to smcginnis

Pike Retrospectives

• Nova [19]
• QA [20]

[1] https://etherpad.openstack.org/p/monasca_queens_midcycle

[2] https://etherpad.openstack.org/p/vitrage-ptg-queens

[3] http://lists.openstack.org/pipermail/openstack-dev/2017-August/121637.html

[4] http://lists.openstack.org/pipermail/openstack-dev/2017-September/121715.html

[5] https://wiki.openstack.org/wiki/PTG/Queens/CityGuide

[6] http://lists.openstack.org/pipermail/openstack-dev/2017-August/121494.html

[7] https://etherpad.openstack.org/p/etsi-nfv-openstack-gathering-denver

[8] http://lists.openstack.org/pipermail/openstack-dev/2017-September/121711.html

[9] http://lists.openstack.org/pipermail/openstack-dev/2017-September/121734.html

[10]  http://lists.openstack.org/pipermail/openstack-dev/2017-August/121647.html

[11] http://lists.openstack.org/pipermail/openstack-dev/2017-August/121656.html

[12] https://wiki.openstack.org/wiki/Outreachy/Mentors

[13] http://lists.openstack.org/pipermail/openstack-dev/2017-August/121598.html

[14] http://lists.openstack.org/pipermail/openstack-dev/2017-August/121602.html

[15] http://lists.openstack.org/pipermail/openstack-dev/2017-August/121623.html

[16] http://lists.openstack.org/pipermail/openstack-dev/2017-August/121681.html

[17] https://review.openstack.org/#/c/499186/

[18] http://lists.openstack.org/pipermail/openstack-dev/2017-September/121706.html

[19] https://etherpad.openstack.org/p/nova-pike-retrospective

[20] https://etherpad.openstack.org/p/qa-pike-retrospective

[21] http://eavesdrop.openstack.org/irclogs/%23openstack-dev/%23openstack-dev.2017-08-30.log.html#t2017-08-30T16:07:24

[22] http://eavesdrop.openstack.org/irclogs/%23openstack-dev/%23openstack-dev.2017-08-30.log.html#t2017-08-30T16:08:07

SuccessBot Says

• rosmaita: Glance is merging like crazy today! welcome back jokke_ , and thanks flaper87, mfedosin , abhishekk, and smcginnis [1]
• coolsvap: devs, the community support for pycharm subscription has been extended by one year! Enjoy [2]
• Rosmaita:  Glance Pike RC-2 is now available! [3]

PTG Planning

• Skip Level Upgrades[12]
• Cyborg [13]
• Keystone has things they want to share with the Baremetal/VM SIG [14]
• CI Squad week 34 [24]

Summaries

• TC Report 34[4]
• api-sig/news [5]
• TC Update- Aug 25th [15]
• placement/resource providers update 33 [16]

Updates

• Magnum is back to weekly meetings starting 8/22 every Tuesday at 16:00 UTC
• Updating the Docs Mission Statement  [17]
  • Thierry proposed [18]:
    • The docs team provides guidance, assistance, tooling, and style guides
      enabling OpenStack project teams to produce consistent, accurate, and
      high-quality documentation.
  • Shifting opinions towards starting from scratch- looking at what the docs team actually does/makes before crafting words around it [19]
  • Discussion will likely continue at the PTG
• Microversion Parse Growth [20]
  • cdent has a patch that has started cleaning up and shifting miroversion related functions out of the placement serves and into a microversion-parse library [21]
  • Still more work to be done- decorators that handle multiple callables of the same name based on microversion, utility method to raise a status code response based microversion match, etc
  • cdent would like opinions on how to proceed
• Custom Resource Classes, Bare Metal Scheduling and You [22]
  • If you run a 3rd party CI– this is important
  • In Pike, Nova provides a new way of scheduling baremetal based on custom resource classes
  • The old way is now deprecated but will be UNAVAILABLE in Queens
  • All operators running ironic will have to set the resource class field before upgrading to Pike and change flavors before upgrading to Queens
  • The ironic virt driver in Nova is going to be automatically migrating the embedded flavor within existing instances in Pike [23]
  • A periodic task in the nova-compute service
    will automatically create any custom resource class from an ironic node
    in the Placement service if it does not already exist
• Install Guide Testing [25]
  • Docs team needs volunteers to test and verify the installation instructions [26]
  • If you find things that need work, add them here [27]
  • Teams in particular that should take note:
    • Cinder
    • Keystone
    • Horizon
    • Neutron
    • Nova
    • Glance
• Reducing Code Complexity as a to-5 goal [6]
  • Different than former approaches- cdent proposes prioritization of a few simple rules of thumb
    • Extracing methods
    • Keeping methods short
    • Avoiding side effects
    • Keeping modules short
  • Cdent proposed a patch [7]
  • Current Top 5 list [8]
• CleanUp Oslo Deprecated Stuff [9]
  • There are a lot of things that need to be cleaned up in Queens that have been deprecated in Oslo[10]
  • If you have questions- go to the oslo helproom at the PTG
  • Common gerrit topic will be ‘oslo-debt-cleanup’ to help track reviews around this technical debt
• Marking <= mitaka EOL[11]
  • There are a number of old stable/* branches that need to be cleaned up
  • If you are involved in the following projects, please speak up!
    • QA
    • Group-based-policy
    • Zaqar
    • Packaging-deb
    • Fuel
    • networking-*
  • Removal is set to happen at the PTG

[1] http://eavesdrop.openstack.org/irclogs/%23openstack-glance/%23openstack-glance.2017-08-21.log.html#t2017-08-21T13:53:36

[2] http://eavesdrop.openstack.org/irclogs/%23openstack-dev/%23openstack-dev.2017-08-22.log.html#t2017-08-22T10:14:47

[3] http://eavesdrop.openstack.org/irclogs/%23openstack-glance/%23openstack-glance.2017-08-24.log.html#t2017-08-24T13:53:16

[4] http://lists.openstack.org/pipermail/openstack-dev/2017-August/121383.html

[5] http://lists.openstack.org/pipermail/openstack-dev/2017-August/121462.html

[6] http://lists.openstack.org/pipermail/openstack-dev/2017-August/121445.html

[7] https://review.openstack.org/#/c/496404/

[8] https://governance.openstack.org/tc/reference/top-5-help-wanted.html

[9] http://lists.openstack.org/pipermail/openstack-dev/2017-August/121345.html

[10] https://etherpad.openstack.org/p/oslo-queens-tasks

[11] http://lists.openstack.org/pipermail/openstack-dev/2017-August/121432.html

[12] https://etherpad.openstack.org/p/queens-PTG-skip-level-upgrades

[13] https://etherpad.openstack.org/p/cyborg-queens-ptg

[14] http://lists.openstack.org/pipermail/openstack-dev/2017-August/121468.html

[15] http://lists.openstack.org/pipermail/openstack-dev/2017-August/121484.html

[16] http://lists.openstack.org/pipermail/openstack-dev/2017-August/121490.html

[17] http://lists.openstack.org/pipermail/openstack-dev/2017-August/120744.html

[18] http://lists.openstack.org/pipermail/openstack-dev/2017-August/120796.html

[19] http://lists.openstack.org/pipermail/openstack-dev/2017-August/121361.html

[20] http://lists.openstack.org/pipermail/openstack-dev/2017-August/121384.html

[21] https://review.openstack.org/#/c/496212

[22] http://lists.openstack.org/pipermail/openstack-dev/2017-August/121380.html

[23] http://lists.openstack.org/pipermail/openstack-dev/2017-August/121385.html

[24] http://lists.openstack.org/pipermail/openstack-dev/2017-August/121502.html

[25] http://lists.openstack.org/pipermail/openstack-dev/2017-August/121482.html

[26]  https://docs.openstack.org/install-guide/

[27] https://wiki.openstack.org/wiki/Documentation/PikeDocTesting

Summaries

• Nova placement/resource providers update 30 1
• TC Report 30 2
• POST /api-wg/news 3
• Release countdown for week R-4, July 28 – Aug 4 4
• Technical Committee Status update, July 28 5

Project Team Gathering Planning

• Nova 6
• Keystone 7
• Sahara 8
• Cinder 9
• Oslo 10
• Neutron 11
• Documentation 12

Oslo DB Network Database Base namespace throughout OpenStack Projects

• Mike Bayer has been working with Octave Oregon on adding the network database storage engine for mysql to oslo.db module so other projects can take advantage of it. Mike Bayer notes:
  • The code review 13
  • Support in Nova 14
  • Support in Neutron 15
• New data types that map to types from the NDB namespace.
  • oslo_db.sqlalchemy.types.SmallString
  • oslo_db.sqlalchemy.types.String
• Full thread: 16

1. http://lists.openstack.org/pipermail/openstack-dev/2017-July/120290.html
2. http://lists.openstack.org/pipermail/openstack-dev/2017-July/120112.html
3. http://lists.openstack.org/pipermail/openstack-dev/2017-July/120245.html
4. http://lists.openstack.org/pipermail/openstack-dev/2017-July/120304.html
5. http://lists.openstack.org/pipermail/openstack-dev/2017-July/120280.html
6. http://lists.openstack.org/pipermail/openstack-dev/2017-July/120020.html
7. http://lists.openstack.org/pipermail/openstack-dev/2017-July/119299.html
8. http://lists.openstack.org/pipermail/openstack-dev/2017-July/119352.html
9. http://lists.openstack.org/pipermail/openstack-dev/2017-July/119358.html
10. http://lists.openstack.org/pipermail/openstack-dev/2017-July/119462.html
11. http://lists.openstack.org/pipermail/openstack-dev/2017-July/120270.html
12. http://lists.openstack.org/pipermail/openstack-dev/2017-July/119990.html
13. https://review.openstack.org/#/c/427970/
14. https://review.openstack.org/#/c/446643
15. https://review.openstack.org/#/c/446136/
16. http://lists.openstack.org/pipermail/openstack-dev/2017-July/thread.html#120037