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

gitweb link broken after OpenDev migration
by Nadathur, Sundar 25 Apr '19

25 Apr '19

The gitweb link seen in the diffs in review.openstack.org is broken - it still points to git.openstack.org in all the diffs I looked at, and that returns a 404. E.g. https://drive.google.com/file/d/1XVEyLnDOeJ0UUY16EfmDmV8029Ktp6HS/view?usp=… Regards, Sundar

3 4

[cyborg] [ironic] [ptg] Cyborg-Ironic cross-project etherpad available
by Nadathur, Sundar 25 Apr '19

25 Apr '19

Please see https://etherpad.openstack.org/p/ptg-train-xproj-ironic-cyborg . It has been linked to: https://etherpad.openstack.org/p/DEN-train-ironic-brainstorming Line 162 https://etherpad.openstack.org/p/DEN-train-ironic-ptg Line 198 https://etherpad.openstack.org/p/cyborg-ptg-train Line 20 https://wiki.openstack.org/wiki/PTG/Train/Etherpads Regards, Sundar

1 0

[all][qa][ptg][forum] QA PTG Schedule and Related Forum Sessions
by Ghanshyam Mann 24 Apr '19

24 Apr '19

Hello Everyone, I have prepared the QA schedule for Denver Open Infrastructure Summit and PTG. We will be meeting for two days in PTG which is divided into two parts 1. topic discussions for one and half days 2. Code Sprint & Open Discussion. * PTG: QA 2nd May- 3rd May 2019: Room 105 PTG Scheduled is flexible and we can adjust it based on request. QA Stein PTG Schedule - https://ethercalc.openstack.org/Train-PTG-QA-Schedule Details of each session can be found in this etherpad - https://etherpad.openstack.org/p/qa-train-ptg * Summit: QA Forum sessions: Along with project updates & onboarding sessions, QA team will host QA feedback sessions . 1. OpenStack QA - Project Update: Tuesday, April 30, 2:35pm-2:55pm [1] 2. OpenStack QA - Project Onboarding : Wednesday, May 1, 9:00am-9:40am [2] 3. Users / Operators adoption of QA tools / plugins : Wednesday, May 1, 10:50am-11:30am [3] [1] https://www.openstack.org/summit/denver-2019/summit-schedule/events/23703/o… [2] https://www.openstack.org/summit/denver-2019/summit-schedule/events/23728/o… [3] https://www.openstack.org/summit/denver-2019/summit-schedule/events/23660/u… -gmann

1 0

[all][qa][forum] Etherpad for Users / Operators adoption of QA tools / plugins sessions
by Ghanshyam Mann 24 Apr '19

24 Apr '19

Hello Everyone, I've created the etherpad for the QA feedback sessions[1] which is scheduled on Wednesday, May 1, 10:50am-11:30am. I have added a few basic feedback questions there and If you have any additional items to add or modify, please feel free to do that. In case, you are not able to attend this session, you can still write your feedback with your irc/name contact. Etherpad: https://etherpad.openstack.org/p/Den-forum-qa-ops-user-feedback [1] https://www.openstack.org/summit/denver-2019/summit-schedule/events/23660/u… -gmann

1 0

[self-healing][PTG][Forum] Self-healing SIG sessions at Denver Forum and PTG
by Adam Spiers 24 Apr '19

24 Apr '19

Hi there, This is a last call for topics for discussion at either of the two self-healing SIG sessions scheduled next week in Denver. Everyone is warmly invited to add topics they are interested in to the etherpad: https://etherpad.openstack.org/p/DEN-self-healing-SIG As always, we are particularly interested to hear feedback from operators: - Are you already implementing any self-healing functionality in your OpenStack clouds? - If so, how are you doing it, and what's working and not working? - What self-healing functionality would you like to see which is currently missing? The Birds of a Feather session on Wednesday May 1, 9:50am-10:30am is the best time to provide that feedback: https://www.openstack.org/summit/denver-2019/summit-schedule/events/23743/s… However we also have a PTG session the whole afternoon of Thursday May 2nd: https://www.openstack.org/ptg#tab_schedule and while it will certainly cover developer-oriented topics, operator feedback is very welcome there too. Looking forward to seeing you all! Regards, Adam and Eric

1 0

[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

[octavia] Octavia 4.x for Rocky?
by Volodymyr Litovka 24 Apr '19

24 Apr '19

Dear colleagues, whether Octavia 4.x can be used with Rocky? Whether it makes sense (I mean, whether Octavia's new features are tied to Stein's features)? Thank you. -- Volodymyr Litovka "Vision without Execution is Hallucination." -- Thomas Edison

2 1

[ptg] ptgbot HOWTO
by Thierry Carrez 24 Apr '19

24 Apr '19

Hi everyone, In a few days, some contributor teams will meet in Denver for the 5th Project Teams Gathering. The event is organized around separate 'tracks' (generally tied to a specific team/group). Topics of discussion are loosely scheduled in those tracks, based on the needs of the attendance. This allows to maximize attendee productivity, but the downside is that it can make the event a bit confusing to navigate. To mitigate that issue, we are using an IRC bot to expose what's happening currently at the event at the following page: http://ptg.openstack.org/ptg.html It is therefore useful to have a volunteer in each room who makes use of the PTG bot to communicate what's happening. This is done by joining the #openstack-ptg IRC channel on Freenode and voicing commands to the bot. Usage of the bot is of course optional, but in past editions it was really useful to help attendees successfully navigate this dynamic event. How to keep attendees informed of what's being discussed in your room --------------------------------------------------------------------- To indicate what's currently being discussed, you will use the track name hashtag (found in the "Scheduled tracks" section on the above page), with the 'now' command: #TRACK now <what's currently being discussed> Example: #swift now brainstorming improvements to the ring You can also mention other track names to make sure to get people attention when the topic is transverse: #ops-meetup now discussing #cinder pain points There can only be one 'now' entry for a given track at a time. To indicate what will be discussed next, you can enter one or more 'next' commands: #TRACK next <what will be discussed and when> Example: #api-sig next at 2pm we'll be discussing pagination woes Note that in order to keep content current, entering a new 'now' command for a track will automatically erase any 'next' entry for that track. Finally, if you want to clear all 'now' and 'next' entries for your track, you can issue the 'clean' command: #TRACK clean Example: #ironic clean How to book reservable rooms ---------------------------- Like at every PTG, in Denver we will have additional reservable space for extra un-scheduled discussions. Two of those rooms (Ballroom 4 and Room 112) are equipped with a projector, so if your discussion would benefit from projection, you can also book time there. Finally, some of the smaller teams do not have any pre-scheduled space, and will solely be relying on this feature to book the time that makes the most sense for them. Those teams are the OpenStack release management team (#release-management) and requirements team (#requirements), the Extended Maintenance SIG (#extended-maint-sig), the Security SIG (#security-sig), the Bare Metal SIG (#baremetal-sig) and the Interoperability working group (#interop-wg). The PTG bot page shows which track is allocated to which room, as well as available reservable space, with a slot code (room name - time slot) that you can use to issue a 'book' command to the PTG bot: #TRACK book <slot code> Example: #release-management book Room 112-ThuA1 Any track can book additional space and time using this system. All slots are 1h45-long. If your topic of discussion does not fall into an existing track, it is easy to add a track on the fly. Just ask PTG bot admins (ttx, diablo_rojo...) on the channel to create a track for you (which they can do by getting op rights and issuing a ~add <TRACK> command). For more information on the bot commands, please see: https://opendev.org/openstack/ptgbot/src/branch/master/README.rst Let me know if you have any additional questions. -- Thierry Carrez (ttx)

1 0

[scientific-sig] No IRC meeting today
by Stig Telfer 24 Apr '19

24 Apr '19

Hi All - Apologies, no Scientific SIG meeting today. We have plenty going on besides in preparation for Denver next week, and I hope to see you there. Cheers, Stig

1 0

[kolla] Instance unable to contact outside network
by vladimir franciz blando 24 Apr '19

24 Apr '19

Hi All, Deploying an OpenStack Rocky (1 controller+ceph, 1 compute+ceph) environment on Packet.net using kolla-ansible 7.1.0. Everything works except Instance connectivity going out. controller1 network http://paste.openstack.org/show/749565/ compute1 network http://paste.openstack.org/show/749566/ openvswitch show http://paste.openstack.org/show/749567/ 1. Instance to Instance PING via it's private IP = success 2. Instance to Instance PING via floating IP = success 3. Instance to gateway ping = success 4. Instance to outside world (ex. 8.8.8.8 or google.com) = failed 5. PINGing the instance from the controller node using the floating IP = failed Here is my global.yml file http://paste.openstack.org/show/lpAGgrEm8rNe43WeB8Uo/ Here is my multinode file http://paste.openstack.org/show/DL7l1WG2xotH5KziwuyL/ Here is my init-runounce file http://paste.openstack.org/show/749568/ - Vlad ᐧ

2 1

[Kolla-Ansible] Support for LXC
by Amit Kumar 24 Apr '19

24 Apr '19

Hello All, We have deployed OpenStack multinode using Kolla-Ansible. We are able to create VMs, Docker Containers (using Zun). However, we also want to launch LXCs, but we couldn't find any such option in globals.yaml to enable this support. Is there any plan to provide it out-of-box? If anybody has enabled LXC using Kolla-Ansible by themselves, then also please let us know. Thanks. Regards, Amit

2 1

[neutron] CI meeting next week
by Slawek Kaplonski 24 Apr '19

24 Apr '19

Hi, As most of us will be on summit next week, CI meeting from 30.04 is cancelled. We will have next meeting on 7.05. See You in Denver next week :) -- Slawek Kaplonski Senior software engineer Red Hat

1 0

[tripleo][openstack-ansible] collaboration on os_tempest role update XX - Apr 24, 2019
by Chandan kumar 24 Apr '19

24 Apr '19

Hello, Here is the 20th update (Apr 17 to Apr 23, 2019) on collaboration on os_tempest[1] role between TripleO and OpenStack-Ansible projects. Highlights of the week: * os_tempest got support of novajoin tempest plugin. * During stein branching on OSA side, we found that tempest_git_repo is not defined thanks to Jesse Pretorius (odyssey4me) and mnaser for fixing it. Things got merged: os_tempest: * Enable support for novajoin tempest plugin - https://review.openstack.org/652986 * Only add tempest/tempestconf git constraints *_git_repo is defined - https://review.opendev.org/653690 Things in Progress: os_tempest: * Make smoke tests as a default whitelist tests - https://review.openstack.org/652060 * Update openstack.org -> opendev.org - https://review.opendev.org/654942 tripleo: * Enable os_tempest in baremetal-full-overcloud-validate playbook - https://review.openstack.org/652983 * Run novajoin tempest tests in all TLS job using os_tempest - https://review.openstack.org/639324 * Add documentation for consuming os_tempest role - https://review.opendev.org/#/c/654406/ What is coming? On TripleO side, we will be working on porting all upstream standalone tripleo jobs to os_tempest. We will be continue working on current os_tempest patches. Here is the 19th update [2]. Have queries, Feel free to ping us on #tripleo or #openstack-ansible channel. Links: [1.] http://git.openstack.org/cgit/openstack/openstack-ansible-os_tempest [2.] http://lists.openstack.org/pipermail/openstack-discuss/2019-April/005256.ht… Thanks, Chandan Kumar

1 0

[tricircle] Bi-weekly meeting brief note (2019-04-24)
by zhangchi＠szzt.com.cn 24 Apr '19

24 Apr '19

Hi, All, Here is today bi-weekly meeting brief note. We’ve previously decided to move back the Tricircle bi-weekly meeting back to community IRC channel, and this week some of tricircle team members facing trouble of registering IRC account so that we have to use wechat group for this week meeting again. Startling from next week, we will move back the meeting to IRC, when all team members having their IRC accounts ready. Below is a brief note of what we discussed today, 1. [tricircle] This bug is now being tracked: Tricircle some unit tests can not pass since neutron Stein introduced network_segment_ranges https://bugs.launchpad.net/neutron/+bug/1821567. PR has been submitted. 2. [tricircle] tricircle unit tests development is in progress, targeting to have 80% user case coverage. 3. [tricircle] Integrate Tricircle to work with zuul v3 (this is under planning) 4. [tricircle] Deploy containers in tricircle environment (discussion started and currently team is working on writing spec) 5. [tricircle] Finish the PR "ipv6_address_mode" not found in unit test (planning) 6. [tricircle] meeting will move back to IRC (openStack-meeting channel) every two weeks starting from next Wednesday (2019-05-08) UTC 1:00 7. [tricircle] Haoyang shared 9th Open Source Hackathon summary held in Shenzhen last week to catch up latest OpenStack activity in China.

1 0

[Forum][Ops] Ops War Stories Lightning Talk session
by Shintaro Mizuno 24 Apr '19

24 Apr '19

Hi There is a Forum session for the operators [1] at the Denver Summit, which I want to shed some light on before the Summit. This session is a Lightning Talk session for the operators to share their war stories and architectures. It will be a short 5 min slot and slides are not required (you can have them if you want). If you have stories to share, please put your name and a title of your talk to the etherpad below. [1] https://etherpad.openstack.org/p/DEN-ops-war-stories-LT Hope to see you in Denver! Best regards, Shintaro -- Shintaro MIZUNO NTT Software Innovation Center TEL: 0422-59-4977 E-mail: mizuno.shintaro(a)lab.ntt.co.jp (Expires on 2019.6） New E-mail：shintaro.mizuno.gt(a)hco.ntt.co.jp

1 1

[tricircle] Today's Topics (2019-04-24)
by zhangchi＠szzt.com.cn 24 Apr '19

24 Apr '19

Today's topic is: 1. [tricircle] The bug is now being tracking: Tricircle some unit tests can not pass since neutron Stein introduced network_segment_ranges https://bugs.launchpad.net/neutron/+bug/1821567 pr have been submitted 2. [tricircle] tricircle unitests is being added aims at Use case coverage over 80% (in progress) 3. [tricircle] Make Tricircle work with zuul v3 (planned) 4. [tricircle] deploying containers in tricircle environments (started and writing sepc) 5. [tricircle] finish the pr "ipv6_address_mode" not found in unit test (planning) 6. [tricircle] meeting will move back to IRC (openStack-meeting channel) every two weeks since next Wednesday (2019-05-08) UTC 1:00 7. [tricircle] learning the 9th Open Source Cloud Hackathon

1 0