September 2020 - openstack-discuss

Re: Re: [openstack-ansible] OpenStack Ansible deployment fails due to lxc containers not having network connection
by Oliver Wenz 22 Sep '20

22 Sep '20

Hi Jonathan, thank you for your reply! I probably should have specified that I already changed some default values in /etc/ansible/roles/lxc_hosts/defaults/main.yml to prevent a conflict with my storage network. Here's the part that I changed: ``` lxc_net_address: 10.255.255.1 lxc_net_netmask: 255.255.255.0 lxc_net_dhcp_range: 10.255.255.2,10.255.255.253 ``` Could there be some other reference to the original default address range which causes the error? I'm also confused about dnsmasq: Running 'apt-get install dnsmasq' I discovered that it wasn't installed on the infra host yet (though installing it also didn't solve the problem). Moreover, I couldn't find dnsmasq in the prerequisites in the OSA deployment guide. Kind regards, Oliver On 03/09/2020 18:38, openstack-discuss-request(a)lists.openstack.org wrote: > Message: 1 > Date: Thu, 3 Sep 2020 16:51:51 +0100 > From: Jonathan Rosser <jonathan.rosser(a)rd.bbc.co.uk> > To: openstack-discuss(a)lists.openstack.org > Subject: Re: [openstack-ansible] OpenStack Ansible deployment fails > due to lxc containers not having network connection > Message-ID: <e6746294-ada6-0f29-cdfb-59538396a0e0(a)rd.bbc.co.uk> > Content-Type: text/plain; charset=utf-8; format=flowed > > Hi Oliver, > > The default route would normally be via eth0 in the container, which I > suspect has some issue. > > This is given an address by dnsmasq/dhcp on the host and attached to > lxcbr0. This is where I would start to look. I am straight seeing that > the default address range used for eth0 is in conflict with your storage > network, so perhaps this is also something to look at. See > https://github.com/openstack/openstack-ansible-lxc_hosts/blob/master/defaul… > <https://github.com/openstack/openstack-ansible-lxc_hosts/blob/master/defaul…> > > You join us on irc at #openstack-ansible for some 'real-time' assistance > if necessary. > > Regards, > Jonathan. > > On 03/09/2020 16:18, Oliver Wenz wrote: >> I'm trying to deploy OpenStack Ansible. When running the first playbook >> ```openstack-ansible setup-hosts.yml```, there are errors for all >> containers during the task ```[openstack_hosts : Remove the blacklisted >> packages]``` (see below) and the playbook fails. >> >> ``` >> fatal: [infra1_repo_container-1f1565cd]: FAILED! => {"changed": false, >> "cmd": "apt-get update", "msg": "E: The repository >> 'http://ubuntu.mirror.lrz.de/ubuntu bionic Release' no longer has a >> Release file. >> E: The repository 'http://ubuntu.mirror.lrz.de/ubuntu bionic-updates >> Release' no longer has a Release file. >> E: The repository 'http://ubuntu.mirror.lrz.de/ubuntu bionic-backports >> Release' no longer has a Release file. >> E: The repository 'http://ubuntu.mirror.lrz.de/ubuntu bionic-security >> Release' no longer has a Release file.", "rc": 100, "stderr": "E: The >> repository 'http://ubuntu.mirror.lrz.de/ubuntu bionic Release' no longer >> has a Release file. >> E: The repository 'http://ubuntu.mirror.lrz.de/ubuntu bionic-updates >> Release' no longer has a Release file. >> E: The repository 'http://ubuntu.mirror.lrz.de/ubuntu bionic-backports >> Release' no longer has a Release file. >> E: The repository 'http://ubuntu.mirror.lrz.de/ubuntu bionic-security >> Release' no longer has a Release file. >> ", "stderr_lines": ["E: The repository >> 'http://ubuntu.mirror.lrz.de/ubuntu bionic Release' no longer has a >> Release file.", "E: The repository 'http://ubuntu.mirror.lrz.de/ubuntu >> bionic-updates Release' no longer has a Release file.", "E: The >> repository 'http://ubuntu.mirror.lrz.de/ubuntu bionic-backports Release' >> no longer has a Release file.", "E: The repository >> 'http://ubuntu.mirror.lrz.de/ubuntu bionic-security Release' no longer >> has a Release file."], "stdout": "Ign:1 >> http://ubuntu.mirror.lrz.de/ubuntu bionic InRelease >> Ign:2 http://ubuntu.mirror.lrz.de/ubuntu bionic-updates InRelease >> Ign:3 http://ubuntu.mirror.lrz.de/ubuntu bionic-backports InRelease >> Ign:4 http://ubuntu.mirror.lrz.de/ubuntu bionic-security InRelease >> Err:5 http://ubuntu.mirror.lrz.de/ubuntu bionic Release >> Cannot initiate the connection to 192.168.100.6:8000 (192.168.100.6). >> - connect (101: Network is unreachable) >> Err:6 http://ubuntu.mirror.lrz.de/ubuntu bionic-updates Release >> Cannot initiate the connection to 192.168.100.6:8000 (192.168.100.6). >> - connect (101: Network is unreachable) >> Err:7 http://ubuntu.mirror.lrz.de/ubuntu bionic-backports Release >> Cannot initiate the connection to 192.168.100.6:8000 (192.168.100.6). >> - connect (101: Network is unreachable) >> Err:8 http://ubuntu.mirror.lrz.de/ubuntu bionic-security Release >> Cannot initiate the connection to 192.168.100.6:8000 (192.168.100.6). >> - connect (101: Network is unreachable) >> Reading package lists... >> ", "stdout_lines": ["Ign:1 http://ubuntu.mirror.lrz.de/ubuntu bionic >> InRelease", "Ign:2 http://ubuntu.mirror.lrz.de/ubuntu bionic-updates >> InRelease", "Ign:3 http://ubuntu.mirror.lrz.de/ubuntu bionic-backports >> InRelease", "Ign:4 http://ubuntu.mirror.lrz.de/ubuntu bionic-security >> InRelease", "Err:5 http://ubuntu.mirror.lrz.de/ubuntu bionic Release", >> " Cannot initiate the connection to 192.168.100.6:8000 (192.168.100.6). >> - connect (101: Network is unreachable)", "Err:6 >> http://ubuntu.mirror.lrz.de/ubuntu bionic-updates Release", " Cannot >> initiate the connection to 192.168.100.6:8000 (192.168.100.6). - connect >> (101: Network is unreachable)", "Err:7 >> http://ubuntu.mirror.lrz.de/ubuntu bionic-backports Release", " Cannot >> initiate the connection to 192.168.100.6:8000 (192.168.100.6). - connect >> (101: Network is unreachable)", "Err:8 >> http://ubuntu.mirror.lrz.de/ubuntu bionic-security Release", " Cannot >> initiate the connection to 192.168.100.6:8000 (192.168.100.6). - connect >> (101: Network is unreachable)", "Reading package lists..."]} >> >> ``` >> >> When I attach to any container and run ```ping 192.168.100.6``` (local >> DNS), I get the same error (```connect: Network is unreachable```). >> However, when I specify an interface by running ```ping -I eth1 >> 192.168.100.6``` there is a successful connection. >> Running ```ip r``` on the infra_cinder container yields: >> ``` >> 10.0.3.0/24 dev eth2 proto kernel scope link src 10.0.3.5 >> 192.168.110.0/24 dev eth1 proto kernel scope link src 192.168.110.232 >> ``` >> so there seems to be no default route which is why the connection fails >> (similar for the other infra containers). Shouldn't OSA automatically >> configure this? I didn't find anything regarding a default route on >> containers in the Docs. >> >> Here's my openstack_user_config.yml: >> >> ``` >> cidr_networks: >> container: 192.168.110.0/24 >> tunnel: 192.168.32.0/24 >> storage: 10.0.3.0/24 >> >> used_ips: >> - "192.168.110.1,192.168.110.2" >> - "192.168.110.111" >> - "192.168.110.115" >> - "192.168.110.117,192.168.110.118" >> - "192.168.110.131,192.168.110.140" >> - "192.168.110.201,192.168.110.207" >> - "192.168.32.1,192.168.32.2" >> - "192.168.32.201,192.168.32.207" >> - "10.0.3.1" >> - "10.0.3.11,10.0.3.14" >> - "10.0.3.21,10.0.3.24" >> - "10.0.3.31,10.0.3.42" >> - "10.0.3.201,10.0.3.207" >> >> global_overrides: >> # The internal and external VIP should be different IPs, however they >> # do not need to be on separate networks. >> external_lb_vip_address: 192.168.100.168 >> internal_lb_vip_address: 192.168.110.201 >> management_bridge: "br-mgmt" >> provider_networks: >> - network: >> container_bridge: "br-mgmt" >> container_type: "veth" >> container_interface: "eth1" >> ip_from_q: "container" >> type: "raw" >> group_binds: >> - all_containers >> - hosts >> is_container_address: true >> - network: >> container_bridge: "br-vxlan" >> container_type: "veth" >> container_interface: "eth10" >> ip_from_q: "tunnel" >> type: "vxlan" >> range: "1:1000" >> net_name: "vxlan" >> group_binds: >> - neutron_linuxbridge_agent >> - network: >> container_bridge: "br-ext1" >> container_type: "veth" >> container_interface: "eth12" >> host_bind_override: "eth12" >> type: "flat" >> net_name: "ext_net" >> group_binds: >> - neutron_linuxbridge_agent >> - network: >> container_bridge: "br-storage" >> container_type: "veth" >> container_interface: "eth2" >> ip_from_q: "storage" >> type: "raw" >> group_binds: >> - glance_api >> - cinder_api >> - cinder_volume >> - nova_compute >> - swift-proxy >> >> ### >> ### Infrastructure >> ### >> >> # galera, memcache, rabbitmq, utility >> shared-infra_hosts: >> infra1: >> ip: 192.168.110.201 >> >> # repository (apt cache, python packages, etc) >> repo-infra_hosts: >> infra1: >> ip: 192.168.110.201 >> >> # load balancer >> haproxy_hosts: >> infra1: >> ip: 192.168.110.201 >> >> ### >> ### OpenStack >> ### >> >> os-infra_hosts: >> infra1: >> ip: 192.168.110.201 >> >> identity_hosts: >> infra1: >> ip: 192.168.110.201 >> >> network_hosts: >> infra1: >> ip: 192.168.110.201 >> >> compute_hosts: >> compute1: >> ip: 192.168.110.204 >> compute2: >> ip: 192.168.110.205 >> compute3: >> ip: 192.168.110.206 >> compute4: >> ip: 192.168.110.207 >> >> storage-infra_hosts: >> infra1: >> ip: 192.168.110.201 >> >> storage_hosts: >> lvm-storage1: >> ip: 192.168.110.202 >> container_vars: >> cinder_backends: >> lvm: >> volume_backend_name: LVM_iSCSI >> volume_driver: cinder.volume.drivers.lvm.LVMVolumeDriver >> volume_group: cinder_volumes >> iscsi_ip_address: "{{ cinder_storage_address }}" >> limit_container_types: cinder_volume >> >> ``` >> >> I also asked this question on the server fault stackexchange: >> https://serverfault.com/questions/1032573/openstack-ansible-deployment-fail… >> >> >> Kind regards, >> Oliver >> >> >> >

2 1

Openstack version 18.04
by ops＠clustspace.com 21 Sep '20

21 Sep '20

Hello, We are decided to change Apache CloudStack to OpenStack. Trying to install, but only Stein....As you can see we have repositories ussuri root@ops:~# apt update Hit:1 http://ubuntu-cloud.archive.canonical.com/ubuntu bionic-updates/ussuri InRelease Hit:2 http://us.archive.ubuntu.com/ubuntu bionic InRelease Hit:3 http://security.ubuntu.com/ubuntu bionic-security InRelease Hit:4 http://us.archive.ubuntu.com/ubuntu bionic-updates InRelease Hit:5 http://us.archive.ubuntu.com/ubuntu bionic-backports InRelease Reading package lists... Done Building dependency tree Reading state information... Done All packages are up to date. root@ops:~# But after installation we got only Stein root@ops:~# openstack --version openstack 5.2.0 Do'es anyone have idea why we can install only Stein?

3 2

[tripleo][ansible-ceph][ussuri]ceph-ansiible fails at chown stack: /tmp/ceph_ansible_tmp on distributed compute HCI node
by Ruslanas Gžibovskis 21 Sep '20

21 Sep '20

Hi all, using tripleo 13.4.0-1.el8 and ceph-ansible 4.0.25-1.el8 on CentOS8 from @centos-openstack-ussuri repo. I get error [1]. When ansi playbook tries to chown to stack user dir: /tmp/ceph_ansible_tmp, but not able to find user stack. As I understand the deployment process, should it have tripleo-admin user? Also executed ansible.sh file with ansible-playbook -vvvv [2] it also has /home/stack/config-download/v3/ceph-ansible/create_ceph_ansible_remote_tmp.log I see in default file, it has the correct things set: owner: "{{ ansible_user | default('tripleo-admin', true) }}" In undercloud.conf I do not have deployment user set, that option is commented out. I have not set any in overcloud config files... [1] http://paste.openstack.org/show/798126/ [2] http://paste.openstack.org/show/798127 -- Ruslanas Gžibovskis +370 6030 7030

2 3

[tc] weekly meeting time
by Mohammed Naser 21 Sep '20

21 Sep '20

Hi folks: Given that we've landed the change to start having weekly meetings again, it's time to start picking a time: https://doodle.com/poll/xw2wiebm2ayqxvki A few people also mentioned they wouldn't mind taking the current office hours time towards that, I guess we can try and come to an agreement if we want to do that here (or simply by voting that time on the Doodle). Thanks, Mohammed -- Mohammed Naser VEXXHOST, Inc.

2 2

[tc][heat] PTL not available next week
by Rico Lin 20 Sep '20

20 Sep '20

Dear all Due to some personal matters, I'm not available next week 9/21-9/25. for releases, I already propose the patch [1]. And I'm fine with any renew on the patch as long as there's no new feature included (will try to keep update [1] too). [1] https://review.opendev.org/#/c/752809/ -- May The Force of OpenStack Be With You, *Rico Lin*irc: ricolin

1 0

[Neutron] Bug Deputy Report (Sep 14 - Sep 19)
by Hongbin Lu 20 Sep '20

20 Sep '20

Hi all, Below is the bug deputy report: High: * https://bugs.launchpad.net/neutron/+bug/1895671 [OVN] test_add_interface_in_use fail with OVN Midium: * https://bugs.launchpad.net/neutron/+bug/1895933 Admin user can do anything without the control of policy.json * https://bugs.launchpad.net/neutron/+bug/1895950 keepalived can't perform failover if the l3 agent is down * https://bugs.launchpad.net/neutron/+bug/1895972 IPv6 prefix delegation for OVN routers Low: * https://bugs.launchpad.net/neutron/+bug/1896217 [OVS] When "explicitly_egress_direct" is enabled, egress flows are not deleted when the port is removed Undecided: * https://bugs.launchpad.net/neutron/+bug/1895677 [OVS][FW] In some cases, OVS FW tries to set a OF rule when ofport = -1 * https://bugs.launchpad.net/neutron/+bug/1896203 TypeError: Cannot look up record by empty string in check_for_igmp_snoop_support task * https://bugs.launchpad.net/neutron/+bug/1896205 AttributeError: 'NoneType' object has no attribute 'db_find_rows' during neutron-server startup * https://bugs.launchpad.net/neutron/+bug/1896226 The vnics are disappearing in the vm Invalid: * https://bugs.launchpad.net/neutron/+bug/1895636 'NoneType' object has no attribute 'address_scope_id'

1 0

[rpm-packaging][packaging][sigs] Moving to a packaging SIG
by Jean-Philippe Evrard 19 Sep '20

19 Sep '20

Hello folks, It's maybe a little late, as the elections process already have started, but I think it's worth re-opening the conversation about migrating the rpm-packaging project to a SIG. Last time we tried this, we were stopped by bureaucracy and technical details (IIRC?) which shouldn't be there anymore. I don't see a reason why this team couldn't move to a SIG now, which would be a lightweight governance model for you. You would keep your repos, and can still propose releases (if I am not mistaken). Things shouldn't change much. You can decide to change/add chair people when you want, and don't have to sign off a PTL for 6 months at elections, which was the most concerning matter for your projects IIRC (which lead to missed elections deadlines in the past). I hope that this SIG can evolve in the future, to group not only RPM packaging, but also other packaging mechanism that want to follow under that new banner. That's why I proposed the SIG to be named "Packaging" instead. It's up to the community now to gather around the same banner :) So if you're interested with this change, please vote on here: [1] [2]. Regards, Jean-Philippe Evrard (evrardjp) [1]: https://review.opendev.org/752659 [2]: https://review.opendev.org/752661

4 9

[tripleo] patch abandonment, cleaning up gerrit
by Wesley Hayutin 19 Sep '20

19 Sep '20

Greetings, FYI folks I'm going to tear through our projects today and abandon patches older than 365 days. Please read through our policy [1] if you have any questions or concerns. It will be nice to have a little clean up before the next release and PTL take over :) Thanks [1] https://specs.openstack.org/openstack/tripleo-specs/specs/policy/patch-aban…

1 1

[TC][nova] Failing device detachments on Focal
by Balázs Gibizer 18 Sep '20

18 Sep '20

Hi, I want to raise a potential conflict between the fact that OpenStack Victoria officially supports Ubuntu Focal[3] and a high severity regression in Nova [1] caused by a qemu bug [2] in the qemu version that is shipped with Focal. The Nova team documented[4] it as a limitation without a known workaround in Nova. Also as far as I know Canonical does not support downgrading the qemu version so I don't see a viable workaround on Focal side either. Is the Nova reno[4] enough from the TC perspective to go forward with the switch to Focal and with the Victoria release? cheers, gibi [1] https://bugs.launchpad.net/nova/+bug/1882521 [2] https://bugs.launchpad.net/qemu/+bug/1894804 [3] https://governance.openstack.org/tc/reference/runtimes/victoria.html [4] https://review.opendev.org/#/c/752654

5 6

[manila] Bug squash event coming up next Monday (September 21st)
by Victoria Martínez de la Cruz 18 Sep '20

18 Sep '20

Hi all, After the success of our doc-a-thon last month (details to come soon in the original thread) we decided to repeat the experience, this time, with code bugs. We are organizing a bugs squash next Monday, September 21st, with the main goal of closing several bugs in preparation for the RC (that we are cutting next week). We will gather on our Freenode channel #openstack-manila at 3pm UTC and we will use this Jitsi bridge [0] to go over a curated list (thanks Vida!) of opened bugs we have here [1] *Your* participation is truly valued, being you an already Manila contributor or if you are interested in contributing and you didn't know how, so looking forward to seeing you there :) Cheers, Victoria [0] https://meetpad.opendev.org/ManilaV-ReleaseBugSquashRC [1] http://ethercalc.openstack.org/26utlmzuk6cc

1 0

[all][qa][ci][kuryr] Default swap size of gate VMs is 1 GB now
by Michał Dulko 18 Sep '20

18 Sep '20

Hi, Last Friday Kuryr team noticed elevated rate of failures of the kuryr- kubernetes gate jobs. Later on we've tracked it down to oom-killer slaying our Amphora instances. We couldn't find a reason why that only started to happen on Friday, until now. So commit [1] reduced default swap size to 1 GB. If your jobs need more memory - you can try overwriting that in your job configs like we do in [2]. I'm posting this to save people from a week of debugging as it wasn't a fun activity. ;) Thanks, Michał [1] https://opendev.org/openstack/openstack-zuul-jobs/commit/45f555fdf036de786b… [2] https://review.opendev.org/#/c/752233/4/.zuul.d/base.yaml@35

1 0

[neutron][ovn] Logical flow scaling (flow explosion in lr_in_arp_resolve)
by Krzysztof Klimonda 18 Sep '20

18 Sep '20

Hi, We're running some tests of ussuri deployment with ovn ML2 driver and seeing some worrying numbers of logical flows generated for our test deployment. As a test, we create 400 routes, 400 private networks and connect each network to its own routers. We also connect each router to an external network. After doing that a dump of logical flows shows almost 800k logical flows, most of them in lr_in_arp_resolve table: --8<--8<--8<-- # cat lflows.txt |grep -v Datapath |cut -d'(' -f 2 | cut -d ')' -f1 |sort | uniq -c |sort -n | tail -10 3264 lr_in_learn_neighbor 3386 ls_out_port_sec_l2 4112 lr_in_admission 4202 ls_in_port_sec_l2 4898 lr_in_lookup_neighbor 4900 lr_in_ip_routing 9144 ls_in_l2_lkup 9160 ls_in_arp_rsp 22136 lr_in_ip_input 671656 lr_in_arp_resolve # --8<--8<--8<-- ovn: 20.06.2 + patch for SNAT IP ARP reply issue openvswitch: 2.13.0 neutron: 16.1.0 I've seen some discussion about similar issue at OVS mailing lists: https://www.mail-archive.com/ovs-discuss@openvswitch.org/msg07014.html - is this relevant to neutron, and not just kubernetes? -- Krzysztof Klimonda kklimonda(a)syntaxhighlighted.com

3 5

[tripleo][ci] collectd-mysql
by Wesley Hayutin 18 Sep '20

18 Sep '20

Greetings, More fun as usual. Error: Problem: cannot install the best candidate for the job - nothing provides libmysqlclient.so.21()(64bit) needed by collectd-mysql-5.11.0-2.el8.x86_64 - nothing provides libmysqlclient.so.21(libmysqlclient_21.0)(64bit) needed by collectd-mysql-5.11.0-2.el8.x86_64 (try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages) https://bugs.launchpad.net/tripleo/+bug/1896178 https://review.rdoproject.org/r/#/c/29472/ 0/

2 1

[release] Release countdown for week R-3 Sept 21 - 25
by Sean McGinnis 18 Sep '20

18 Sep '20

Development Focus ----------------- The Release Candidate (RC) deadline is next Thursday, September 24. Work should be focused on fixing any release-critical bugs. General Information ------------------- All deliverables released under a cycle-with-rc model should have a first release candidate by the end of the week, from which a stable/victoria branch will be cut. This branch will track the victoria release. Once stable/victoria has been created, master will be ready to switch to wallaby development. While master will no longer be feature-frozen, please prioritize any work necessary for completing victoria plans. Release-critical bugfixes will need to be merged in the master branch first, then backported to the stable/victoria branch before a new release candidate can be proposed. Actions ------- Early in the week, the release team will be proposing RC1 patches for all cycle-with-rc projects, using the latest commit from master. If your team is ready to go for cutting RC1, please let us know by leaving a +1 on these patches. If there are still a few more patches needed before RC1, you can -1 the patch and update it later in the week with the new commit hash you would like to use. Remember, stable/victoria branches will be created with this, so you will want to make sure you have what you need included to avoid needing to backport changes from master (which will technically then be wallaby) to this stable branch for any additional RCs before the final release. The release team will also be proposing releases for any deliverable following a cycle-with-intermediary model that has not produced any victoria release so far. Finally, if you haven't submitted any yet, now is a good time to finalize release highlights. Release highlights help shape the messaging around the release and make sure that your work is properly represented. Upcoming Deadlines & Dates -------------------------- RC1 deadline: September 24 (R-3) Final Victoria release: October 14 Open Infra Summit: October 19-23 Wallaby PTG: October 26-30

1 0

[all][goals] Switch legacy Zuul jobs to native - update #4
by Luigi Toscano 18 Sep '20

18 Sep '20

Hi, another round of updates. The list of the remaining legacy jobs is shortening but the Victoria branching will happen next week, so we need to speed up a bit. Status ====== As usual, the etherpad [3] lists the full status and the links to the patches. Here is a more detailed report for each remaining project. cinder ------ The only legacy job left is a bit unusual, but there is a WIP review now. It needs some more work to fix the reporting. designate --------- The patch for only legacy job has been approved, but there is an unrelated issue which requires input from the designate team. heat ------ Only one legacy job left, the heat cores are aware of it. infra ----- Only one devstack-gate job in the os-loganalyze repository, which should be probably retired. There are 2 other legacy jobs, but not devstack-gate, so less urgent. ironic ------ The port of the remaining legacy job is going to be merged soon (even though it's failing, but the legacy job is failing as well). manila ------ There is only one legacy-base job (not devstack-gate), so less urgent, but there is a patch for it. monasca ------- The monasca-transform contains a devstack-gate legacy job, but the repository is almost retired. There are 3 legacy (non devstack-gate) jobs in other repositories. murano ------ There are two legacy jobs left (murano-apps-refstackclient-unittest and murano-dashboard-sanity-check) which require some input from the team. neutron ------- Only two legacy grenade jobs are left and they are being worked on. nova ---- The work is ongoing on the remaining legacy jobs (a new job which will replace a legacy one, and a grenade job)). zaqar ----- Mostly done, it only requires a python-zaqarclient backport to be merged in Victoria. References ========== [1] the goal: https://governance.openstack.org/tc/goals/selected/victoria/native-zuulv3-j… [2] the up-to-date Zuul v3 porting guide: https://docs.openstack.org/project-team-guide/zuulv3.html [3] the etherpad which tracks the current status: https://etherpad.opendev.org/p/goal-victoria-native-zuulv3-migration [4] the previous reports: http://lists.openstack.org/pipermail/openstack-discuss/2020-July/016058.html http://lists.openstack.org/pipermail/openstack-discuss/2020-August/016561.h… http://lists.openstack.org/pipermail/openstack-discuss/2020-August/016892.h… Ciao -- Luigi

1 0

[policy] Wallaby PTG planning
by Ghanshyam Mann 18 Sep '20

18 Sep '20

Hello Everyone, We have booked 2 hrs slot for the policy popup team in the Wallaby vPTG. Time is Monday 23.00-00 UTC and Tuesday 00.-01:00 UTC Tuesday in Havana room (Both are continuous slots). I have created the etherpad to collect the discussion point. Please add the topic you would like to discuss - https://etherpad.opendev.org/p/policy-popup-wallaby-ptg We request more and more projects to participate in this and discuss the various queries or plan to switch to the new policy. -gmann & raildo

1 0

[neutron] Drivers meeting cancelled
by Slawek Kaplonski 18 Sep '20

18 Sep '20

Hi, I know that it's been already a while since we had our last drivers meeting but recently we don't have any new RFEs to discuss and because of that lets cancel it this week too. If You have any ideas or topics which You would like to discuss on the drivers meeting, please add it to the "On Demand" section at [1]. [1] https://wiki.openstack.org/wiki/Meetings/NeutronDrivers -- Slawek Kaplonski Senior software engineer Red Hat

1 0

[TC] vPTG Details
by Kendall Nelson 18 Sep '20

18 Sep '20

Hello! As you might or might not have seen, I signed up the TC for two chunks of time (based on poll results). The times are: - 15-17 UTC Tuesday October 27th (2 hours; Grizzly Room) - 13-17 UTC Friday October 30 (4 hours; Grizzly Room Hope to see you all there! Also, please add your discussion topics to our brainstorming etherpad[1]! -Kendall Nelson (diablo_rojo) [1] https://etherpad.opendev.org/p/tc-wallaby-ptg

1 0

[Diversity] Diversity & Inclusion WG Meeting 9/21 - Removing Divisive Language
by Amy Marrich 18 Sep '20

18 Sep '20

The Diversity and Inclusion WG will be holding a meeting to continue drafting the OSF's stance on the removal of Divisive Language within the OSF projects. The WG invites members of all OSF projects to participate in this effort and to join us at our next meeting Monday, September 21, at 17:00 UTC which will be held at https://meetpad.opendev.org/osf-diversity-and-inclusion. <https://meetpad.opendev.org/osf-diversity-and-inclusion> Drafts for the stance can be found at https://etherpad.opendev.org/p/divisivelanguage If you have any questions please let me and the team know here, on #openstack-diversity on IRC, or you can email me directly. Thanks, Amy Marrich (spotz)

1 0

[release][heat][karbor][patrole][requirements][swift][tempest][vitrage] Cycle With Intermediary Unreleased Deliverables
by Kendall Nelson 18 Sep '20

18 Sep '20

Hello! Quick reminder that we'll need a release very soon for a number of deliverables following a cycle-with-intermediary release model but which have not done *any* release yet in the Victoria cycle: heat-agents karbor-dashboard karbor patrole requirements swift tempest vitrage-dashboard vitrage Those should be released ASAP, and in all cases before $rc1-deadline, so that we have a release to include in the final $series release. - Kendall Nelson (diablo_rojo)

2 1

[baremetal-sig][ironic] Future work and regular meetings
by Arne Wiebalck 17 Sep '20

17 Sep '20

Dear all, With the release of the bare metal white paper [0] the bare metal SIG has completed its first target and is now ready to tackle new challenges. A number of potential topics the SIG could work on were raised during the recent opendev events. The suggestions are summarised on the bare metal etherpad [1]. To select and organise the future work, we feel that it may be better to start with regular meetings, though: the current idea is once a month, for one hour, on zoom. Based on the experience with the ad-hoc meetings we had so far I have set up a doodle to pick the exact slot: https://doodle.com/poll/3hpypw73455t2g24 If interested, please respond by the end of this week. Equally, if you have additional suggestions for the next focus of the SIG, do not hesitate to add them to [1]. Thanks! Arne [0] https://www.openstack.org/use-cases/bare-metal/how-ironic-delivers-abstract… [1] https://etherpad.opendev.org/p/bare-metal-sig

1 1

[Neutron][FFE] request for QoS policy update for bound ports feature
by Lajos Katona 17 Sep '20

17 Sep '20

Hi, I would like to ask for FFE for the RFE "allow replacing the QoS policy of bound port", [1]. This feature adds the extra step to port update operation to change the allocation in Placement to the min_kbps values of the new QoS policy, if the port has a QoS policy with minimum_bandwidth rule and is bound and used by a server. In neutron there's one open patch: https://review.opendev.org/747774 There's an open bug report for the neutron-lib side: https://bugs.launchpad.net/neutron/+bug/1894825 (placement story: https://storyboard.openstack.org/#!/story/2008111 ) and a fix for that: https://review.opendev.org/750349 [1] https://bugs.launchpad.net/neutron/+bug/1882804 Thanks and Regards, Lajos Katona (lajoskatona)

4 8

[Neutron][python-openstackclient][openstacksdk][FFE] Add source_ip_prefix and destination_ip_prefix to metering label rules
by Rafael Weingärtner 17 Sep '20

17 Sep '20

Hello guys, I would like to ask for FFE for the RFE "Add source_ip_prefix and destination_ip_prefix to metering label rules", [1]. This feature adds source and destination filtering options to Neutron metering label rules. Most of the patches (PRs) relating to this feature have already been reviewed, and are ready to be merged [2]. Moreover, the feature has already been partially merged into Neutron and Neutron-lib. Therefore, it might be interesting to finish the merging process and get the feature into Victoria. [1] https://bugs.launchpad.net/neutron/+bug/1889431 [2] https://review.opendev.org/#/q/topic:bug/1889431+(status:open+OR+status:mer… Thanks and Regards, -- Rafael Weingärtner

2 1

[tripleo] stepping down as PTL
by Wesley Hayutin 17 Sep '20

17 Sep '20

Greetings, Thank you for the opportunity to be the TripleO PTL. This has been a great learning opportunity to work with a pure upstream community, other projects and the OpenStack leadership. Thank you to the TripleO team for your help and dedication in adding features, fixing bugs, and responding to whatever has come our way upstream. Lastly.. Thank you to Alex and Emilien for all the assistance throughout!! Managing the work required here with Covid-19, home schooling is a little much for me at this time, I would like to encourage others to volunteer for the opportunity in Wallaby. 0/

4 3

[qa] Wallaby PTG planning
by Masayuki Igawa 17 Sep '20

17 Sep '20

Hi, We need to start thinking about the next cycle already. As you probably know, next virtual PTG will be held in October 26-30[0]. I prepared an etherpad[1] to discuss and track our topics. So, please add your name if you are going to attend the PTG session. And also, please add your proposals of the topics which you want to discuss during the PTG. I also made a doodle[2] with possible time slots. Please put your best days and hours so that we can try to schedule and book our sessions in the time slots. [0] https://www.openstack.org/ptg/ [1] https://etherpad.opendev.org/p/qa-wallaby-ptg [2] https://doodle.com/poll/qqd7ayz3i4ubnsbb Best Regards, -- Masayuki Igawa Key fingerprint = C27C 2F00 3A2A 999A 903A 753D 290F 53ED C899 BF89

3 5