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

[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