April 2019 - openstack-discuss - lists.openstack.org

[storyboard] sessions at the Summit/Forum + PTG
by Kendall Nelson 24 Apr '19

24 Apr '19

Hello! Interested in StoryBoard? Got questions? Want to join us in the development? Well! We have one Forum session on Monday from 3:50pm to 4:30pm [1]. The focus of the session is to gather pain points people are encountering as we've continued to move forward through our backlog. Please come and share feedback with us! We are also planning on convening in during the PTG in the infra room Thursday morning. We will focus on a complete triage and overhaul and prioritization of all the open stories in Storyboard. If you're interested in helping out, come join us! We will book/update the PTGbot accordingly next week. -Kendall (diablo_rojo) [1] https://www.openstack.org/summit/denver-2019/summit-schedule/events/23658/i…

1 0

[oslo] Project Update Slides
by Ben Nemec 24 Apr '19

24 Apr '19

First draft here: https://docs.google.com/presentation/d/1flIiDiXdE-M4kiL5QkvceqgkqarCm42yc8i… If I missed anything or anything looks wrong let me know ASAP. I'll probably be tweaking them slightly between now and the actual session, but this is pretty much what I plan to present. Thanks. -Ben

1 0

Mentoring at Summit
by Amy Marrich 24 Apr '19

24 Apr '19

For those of you going to summit next week I wanted to point out a few mentoring related sessions. Thanks, Amy (spotz) Sunday: 9:00 - 5:50 OpenStack Upstream Institute sponsored by Lenovo https://www.openstack.org/summit/denver-2019/summit-schedule/events/23607/o… Monday: 12:20-1:40 - Speed Mentoring Lunch sponsored by Intel - RSVP required https://www.openstack.org/summit/denver-2019/summit-schedule/events/23757/r… Tuesday: 4:20 - 5:00 - Welcoming New Contributors State of the Union https://www.openstack.org/summit/denver-2019/summit-schedule/events/23659/w… Wednesday: 10:50-11:30 - Diversity WG BoF - looking for help with the Mentoring Program https://www.openstack.org/summit/denver-2019/summit-schedule/events/23745/d…

1 0

[nova] No meeting the week of the PTG
by Eric Fried 24 Apr '19

24 Apr '19

The Nova meeting that would have been held on 5/2 is canceled due to the PTG. efried .

1 0

[placement][tripleo][kolla] Update on placement extraction from nova
by Matt Riedemann 24 Apr '19

24 Apr '19

I put together an etherpad [1] for a Forum session at the upcoming summit to go over what happened with placement extraction in Stein and the plan for Train. With help I was able to figure out where the extracted placement packages are so it's good to know those exist. Mohammed also gave me the status on OpenStack-Ansible but I'm less clear on TripleO and Kolla. I thought TripleO was supporting fresh installs with extracted placement but gerrit is down and Lee is out today so I'm not sure, and I'm not seeing anything about it in TripleO release notes. I did find that the Kolla release notes say they support extracted placement [2] but I'm not sure to what extent - is it just install from source (pypi?) or also some package support? How about upgrades, i.e. the data migration from placement-in-nova to extracted placement? So if people from the TripleO and Kolla teams can reply here and clarify I can get that back into the etherpad before the Forum session. [1] https://etherpad.openstack.org/p/DEN-update-on-placement-extraction-from-no… [2] https://docs.openstack.org/releasenotes/kolla/stein.html -- Thanks, Matt

4 6

[dev][tc][all] Train Goal Schedule and Update
by Lance Bragstad 24 Apr '19

24 Apr '19

Hi all, Since the community goal selection process has taken a turn, we wanted to send an update regarding the current goals. We originally wanted to have the goals for Train be merged by this point to give project teams ample time to plan for them accordingly in their PTG scheduled. Due to discussions raised in each [0][1], it doesn't sound like either will be making it into Train as a feasible community goal. Fortunately, a couple of last minute goals might be a perfect fit for Train, instead of having a release without any community goals. The first one suggested is to render documentation as PDFs [2]. The second goal, which still needs to be proposed, is for IPv6 support. The advantage is that both of these goals are much smaller in scope, but still useful. We're running up against the clock on getting goals selected for Train, but we still have an opportunity to come to agreement on the new proposals before the PTG. We'd like to ask TC and members of the community to review the proposed goals at their earliest convenience. Additionally, if someone wants help write up the IPv6 support goal [3][4], please reach out gmann and mnaser. Even though we were originally trying to make sure we had firm goals well before the PTG, the reduced scope of the new goals should make them easier to talk about in impromptu sessions or the hallway track. Thanks, JP & Lance [0] https://review.openstack.org/#/c/639376/ [1] https://review.openstack.org/#/c/639010/ [2] https://review.openstack.org/#/c/647712/ [3] http://eavesdrop.openstack.org/irclogs/%23openstack-tc/%23openstack-tc.2019… [4] Note that this goal is for testing IPv6 networking setups in all projects. We already have a tempest full ipv6 job, it would be a matter of making these jobs passing and voting in the future.

4 5

Re: [Release-job-failures] release-post job for openstack/releases failed
by Thierry Carrez 24 Apr '19

24 Apr '19

zuul(a)openstack.org wrote: > Build failed. > > - tag-releases http://logs.openstack.org/76/762e357c0d821c35b0373ac344d697807be031bf/relea… : FAILURE in 3m 35s > - publish-tox-docs-static publish-tox-docs-static : SKIPPED Error during release-post job processing https://opendev.org/openstack/releases/commit/22a2d440f0abddff4ba8d9e3cb8a1… The tags went through, but the Launchpad comment-adding script failed with: python3 -u /home/zuul/scripts/release-tools/launchpad_add_comment.py '--subject=Fix included in openstack/panko 3.1.1' '--content=This issue was fixed in the openstack/panko 3.1.1 release.' 1710812 Connecting to Launchpad at 'production' using credentials in '/home/zuul/.launchpadlib/creds'... Adding comment to #1710812... ERROR during save ! (HTTP Error 401: Unauthorized Response headers: --- content-length: 60 content-type: text/plain date: Wed, 24 Apr 2019 05:17:10 GMT server: zope.server.http (HTTP) status: 401 x-lazr-oopsid: OOPS-f5382a2ee4e917c314954fb63ea98c61 x-powered-by: Zope (www.zope.org) Python (www.python.org) --- Response body: --- b'Unknown consumer (System-wide: Ubuntu (review.opendev.org))' --- ) We might have to reestablish credentials for that to work again... Impact: Bugs were not commented on (job failed), and the release website was not refreshed (job skipped). -- Thierry Carrez (ttx)

3 4

[keystone] Team dinner in Denver
by Colleen Murphy 24 Apr '19

24 Apr '19

Berlin feels like it was ages ago, so let's organize a team dinner in Denver. Poll here: https://framadate.org/BHNNU9S3f9N3lasH If you have strong feelings or even mild inclinations about where to go, please comment on the poll or in the brainstorming etherpad[1] because otherwise I am pretty much just going to throw a dart. Colleen [1] https://etherpad.openstack.org/p/DEN-keystone-forum-sessions

5 5

[openstack-helm] Office hours - 20:00-21:00UTC Wednesdays in #openstack-helm
by Pete Birley 24 Apr '19

24 Apr '19

------------------------------ Hey! Thanks to all those who could attend the meeting we held on the 9th of April; at this meeting we decided that we would resume holding office hours weekly in IRC until the end of this development cycle at least. These will be in our standard channel #openstack-helm, from 20:00-21:00UTC on Wednesdays. During this time we will ensure that there is representation from the core reviewers, and try to help with general support: from onboarding, and deployment issues, to more interactive disucssion regarding specs and testing - please drop in and ask us anything! :) The meeting agenda for this is here: * https://etherpad.openstack.org/p/openstack-helm-meeting-2019-04-09 With minutes logged here: * http://eavesdrop.openstack.org/meetings/openstack_helm/2019/openstack_helm.… The next OpenStack-Helm meeting will be held on the 16th April, at 3pm UTC in #openstack-meeting-4 in freenode IRC, with the following agenda: https://etherpad.openstack.org/p/openstack-helm-meeting-2019-04-16 Cheers Pete

2 1

[placement][ptg] Containers/dockerfiles
by Chris Dent 24 Apr '19

24 Apr '19

>From etherpad [1]: * Some talk in the past of moving https://github.com/cdent/placedock into placement but not sure * Another option is [to] trigger container build with each merge I wrote this one, so I guess I should expand on it a bit. Basically, placedock is a Dockerfile for placement that strives to be small but configurable. The same repo also contains instructions (and YAML) for using the container in kubernetes, and provides a helm chart that uses the generated image. Each of those three things is done in a way where many of the choices are made for you in favor of being light and simple. In things like Kolla, openstack-helm, and other containerizing setups some of those choices are left as options, making the build and run infrastructure more complex. The result with placedock is a tiny service that scales horizontally really well. In the past there's been talk of including some of that stuff in the placement repo itself as a sort of "hey look, here's one way to do it". If we did that, which stuff? Another suggestion has been to use a web-hook or similar from zuul to trigger an image build (either at docker hub or some other registry) post-merge. Or we can let things go as they are (I manually build new images every now and again, which triggers automatic placecat [2] testing). The reason this comes back up is because I'm somewhat concerned that the "seriously, this is really simple" aspect of Placement gets lost and there's probably plenty of useful info in this kind of stuff. If we make it owned by more than just me, that might help spread the learning. Thoughts?k [1] https://etherpad.openstack.org/p/placement-ptg-train [2] https://github.com/cdent/placecat -- Chris Dent ٩◔̯◔۶ https://anticdent.org/ freenode: cdent tw: @anticdent

6 7