January 2022 - openstack-discuss - lists.openstack.org

[all][tc] Technical Committee next weekly meeting on Feb 3rd at 1500 UTC
by Ghanshyam Mann 31 Jan '22

31 Jan '22

Hello Everyone, Technical Committee's next weekly meeting is scheduled for Feb 3rd at 1500 UTC. If you would like to add topics for discussion, please add them to the below wiki page by Wednesday, Feb 2nd, at 2100 UTC. https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting -gmann

1 0

[job] What is the best list for posting an OpenStack job opening?
by Chris DiLorenzo 31 Jan '22

31 Jan '22

Hello, My company has an open position for an OpenStack engineer. We haven't gotten a lot of traction or the candidates we do get lack the OpenStack experience we're looking for. Is it appropriate to post here? Thanks Chris

3 2

[watcher][core] Resignation from Watcher core
by info＠dantalion.nl 31 Jan '22

31 Jan '22

Dear all, Unfortunately I have had increasingly little available free time to spent on the Watcher project over the years. Combined with loss of access to a test environment to debug an actual Watcher deployment for which it has become apparent it will not be reinstated. These combined events inhibit me from effectively making and reviewing patches. As of such I feel it is only right to resign as Watcher core reviewer. I will remove my roles from opendev and launchpad where appropriate as well as remove myself as reviewer from any pending patches. Kind regards & stay safe, Corne (Dantali0n)

1 0

[neutron] Bug Deputy Report January 24 - 30
by Nurmatov Mamatisa 31 Jan '22

31 Jan '22

Hi, I was bug deputy last week. Below is the week summary. I would like to highlight critical bug that affects CI and unassigned #1955008 '[functional] Failure of "test_floatingip_mac_bindings"' Also let me ask OVN team to help with triage OVN related bugs (end of list below). Details: Critical --------- - https://bugs.launchpad.net/neutron/+bug/1955008 - [functional] Failure of "test_floatingip_mac_bindings" - Confirmed - Unassigned! Note: Reported in December but was new occurrences - https://bugs.launchpad.net/neutron/+bug/1959196 - New Secure RBAC policies broke devstack-enforce-scope job - Confirmed - Assigned to Slawek Kaplonski High ---- - https://bugs.launchpad.net/neutron/+bug/1959028 - [OVN][Octavia] Fix the functional CI jobs - Fix Released: https://review.opendev.org/c/openstack/ovn-octavia-provider/+/826323 - Assigned to Rodolfo Alonso - https://bugs.launchpad.net/neutron/+bug/1959176 - neutron fullstack/functional jobs TIMED_OUT randomly - Confirmed - Unassigned - https://bugs.launchpad.net/neutron/+bug/1959151 - Don't set HA ports down while L3 agent restart - In progress: https://review.opendev.org/c/openstack/neutron/+/826545 - Assigned to Krzysztof Tomaszewski Medium ------ - https://bugs.launchpad.net/neutron/+bug/1959125 - OVN mech driver failing to check the L2/L3 connectivity - In progress: https://review.opendev.org/c/openstack/neutron/+/826502 - Assigned to Rodolfo Alonso - https://bugs.launchpad.net/neutron/+bug/1959331 - Router's external gateway isn't properly updated when new subnet is added - In progress: https://review.opendev.org/c/openstack/neutron/+/826828 - Assigned to Slawek Kaplonski - https://bugs.launchpad.net/neutron/+bug/1959332 - With new secure RBAC external gateway ports can't be visible in the API - Confirmed - Assigned to Slawek Kaplonski - https://bugs.launchpad.net/neutron/+bug/1959333 - Error 500 after request with Invalid Scope - In progress: https://review.opendev.org/c/openstack/neutron/+/826872 - Assigned to Slawek Kaplonski - https://bugs.launchpad.net/neutron/+bug/1959184 - [tempest] Test "test_list_policy_filter_by_name" failing - Fix released: https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/826827 - Assigned to yatin - https://bugs.launchpad.net/neutron/+bug/1958964 - Fully Populated Load Balancer creation with OVN provider leaves pools as PENDING_CREATE - In progress: https://review.opendev.org/c/openstack/ovn-octavia-provider/+/826257 - Assigned to Fernando Royo Undecided --------- - https://bugs.launchpad.net/neutron/+bug/1959098 - [ovn] metadata route missing on the guest - New - Unassigned - https://bugs.launchpad.net/neutron/+bug/1958961 - [ovn-octavia-provider] lb create failing with with ValueError: invalid literal for int() with base 10: '24 2001:db8::131/64' - In progress: https://review.opendev.org/c/openstack/ovn-octavia-provider/+/826896 - Assigned to Slawek Kaplonski Thanks, Mamatisa --- Advanced Software Technology Lab Huawei, Moscow

2 1

[neutron] CI meeting 1.02.2022 cancelled
by Slawek Kaplonski 31 Jan '22

31 Jan '22

Hi, Due to overlapping internal meetings tomorrow I have to cancel this week Neutron CI meeting. Next week I will be on PTO but meeting (8.02) will be chair by ralonsoh - thx for that. I will be back on the CI meetings in two weeks - 15.02. -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0

Re: Can neutron-fwaas project be revived?
by Heng Zhou (周恒)-浪潮数据 31 Jan '22

31 Jan '22

Hi Lajos， I understand that the process is to retire neutron-fwaas first, and then create a new project in the X namespace. If want to retire the project, do we need to wait until the stable version(Victoria) of the project is no longer maintained(Extended Maintenance estimated 2022-04-27)? 发件人: Lajos Katona [mailto:katonalala@gmail.com] 发送时间: 2022年1月18日 0:15 收件人: Dazhong Qin (秦海中)-云数据中心集团 <qinhaizhong01(a)inspur.com> 抄送: miguel(a)mlavalle.com; openstack-discuss(a)lists.openstack.org; Heng Zhou (周恒)-浪潮数据 <zhouhenglc(a)inspur.com> 主题: Re: Can neutron-fwaas project be revived? Hi, Neutron team discussed this question on the Drivers meeting, see the logs: https://meetings.opendev.org/meetings/neutron_drivers/2022/neutron_drivers.… The agreement is to move neutron-fwaas to x/ namespace, and revive it as x/neutron-fwaas. Best regards Lajos Katona (lajoskatona) Dazhong Qin (秦海中)-云数据中心集团 <qinhaizhong01(a)inspur.com <mailto:qinhaizhong01@inspur.com> > ezt írta (időpont: 2022. jan. 6., Cs, 2:30): Hi，Miguel， Ok，let’s meet at January 14th. Best regards 发件人: Miguel Lavalle [mailto:miguel@mlavalle.com <mailto:miguel@mlavalle.com> ] 发送时间: 2022年1月6日 9:12 收件人: Dazhong Qin (秦海中)-云数据中心集团 <qinhaizhong01(a)inspur.com <mailto:qinhaizhong01@inspur.com> > 抄送: openstack-discuss(a)lists.openstack.org <mailto:openstack-discuss@lists.openstack.org> 主题: Re: Can neutron-fwaas project be revived? Hi Qin, Unfortunately, this coming January 7th several members of the drivers team will be off on holiday. We won't have a quorum to discuss your proposal. I hope that January 14th works for you and your team. Best regards Miguel On Fri, Dec 24, 2021 at 10:18 AM Miguel Lavalle <miguel(a)mlavalle.com <mailto:miguel@mlavalle.com> > wrote: Hi Qin, I have added this topic to the drivers meeting agenda (see on demand agenda close to the bottom): https://wiki.openstack.org/wiki/Meetings/NeutronDrivers Cheers On Thu, Dec 23, 2021 at 7:42 PM Dazhong Qin (秦海中)-云数据中心集团 <qinhaizhong01(a)inspur.com <mailto:qinhaizhong01@inspur.com> > wrote: Hi Miguel, Thank you for your suggestion. My colleague HengZhou will submit relevant documents as soon as possible in accordance with the official neutron rules. Yes，we will attend the neutron drivers meeting on January 7th. Merry Christmas! Best wish for you! 发件人: Miguel Lavalle [mailto:miguel@mlavalle.com <mailto:miguel@mlavalle.com> ] 发送时间: 2021年12月24日 0:43 收件人: Dazhong Qin (秦海中)-云数据中心集团 <qinhaizhong01(a)inspur.com <mailto:qinhaizhong01@inspur.com> > 抄送: openstack-discuss(a)lists.openstack.org <mailto:openstack-discuss@lists.openstack.org> 主题: Re: Can neutron-fwaas project be revived? Hi Qin, In preparation for your meeting with the drivers team, I suggest we follow as a starting point the Neutron Stadium Governance rules and processes as outlined in the official documentation: https://docs.openstack.org/neutron/latest/contributor/stadium/governance.ht…. In the past, we have re-incorporated projects to the Stadium, like for example in the case of neutron-vpnaas. This document in the Neutron specs repo summarizes how we assessed the readiness of vpnaas for the stadium: https://specs.openstack.org/openstack/neutron-specs/specs/stadium/queens/ne… (https://review.opendev.org/c/openstack/neutron-specs/+/506012). I suggest you start a similar document for fwaas in the folder for the current cycle: https://specs.openstack.org/openstack/neutron-specs/specs/yoga/index.html. As soon as you can, please push it to gerrit, so we can start reviewing it. Did I understand correctly that you will attend the drivers meeting on January 7th? Best regards Miguel On Wed, Dec 22, 2021 at 8:09 PM Dazhong Qin (秦海中)-云数据中心集团 <qinhaizhong01(a)inspur.com <mailto:qinhaizhong01@inspur.com> > wrote: Hi Miguel, I am glad to hear this news. How about our discussion on January 7th, this Friday is not convenient, what do I need to prepare before the discussion, do I need to submit rfe or other descriptions? 发件人: Miguel Lavalle [mailto: <mailto:miguel@mlavalle.com> miguel(a)mlavalle.com] 发送时间: 2021年12月23日 0:20 收件人: Dazhong Qin (秦海中)-云数据中心集团 < <mailto:qinhaizhong01@inspur.com> qinhaizhong01(a)inspur.com> 抄送: <mailto:openstack-discuss@lists.openstack.org> openstack-discuss(a)lists.openstack.org 主题: Re: Can neutron-fwaas project be revived? Hi Qin, I think that in principle the community will be delighted if you and your team can reactivate the project and maintain it. Probably the best next step is for you to attend the next Neutron drivers meeting (https://wiki.openstack.org/wiki/Meetings/NeutronDrivers) so we can discuss the specifics of your proposal. This meeting takes place on Fridays at 1400 UTC over IRC in oftc.net <http://oftc.net> , channel #openstack-neutron. Due to the end of year festivities in much of Europe and America, the next meeting will take place until January 7th. Is that a good next step for you? If yes, I'll add this topic to the meeting's agenda. Best regards On Tue, Dec 21, 2021 at 10:29 AM Dazhong Qin (秦海中)-云数据中心集团 <qinhaizhong01(a)inspur.com <mailto:qinhaizhong01@inspur.com> > wrote: Hi： The firewall project is a necessary function when the project is delivered. The lack of firewall function after switching OVN is not acceptable to customers. We intend to maintain this project and develop the fwaas driver based on ovn. Whether the neutron-fwaas project can be reactivate? What should I do ?

5 9

[all][tc] What's happening in Technical Committee: summary 28th Jan, 21: Reading: 5 min
by Ghanshyam Mann 29 Jan '22

29 Jan '22

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * We had this week meeting yesterday. Most of the meeting discussions are summarized below (Completed or in-progress activities section). Meeting full logs are available @https://meetings.opendev.org/meetings/tc/2022/tc.2022-01-27-15.00.log.html * Next week's meeting is on 3rd Feb Thursday 15:00 UTC, feel free add the topic on the agenda[1] by 2nd Feb. 2. What we completed this week: ========================= * "FIPS compatibility and compliance" community-wide goal proposal is merged[2] * Renamed Skyline repo to openstack/ namespace[3] 3. Activities In progress: ================== TC Tracker for Yoga cycle ------------------------------ * This etherpad includes the Yoga cycle targets/working items for TC[4]. 2 out of 9 items are completed. Open Reviews ----------------- * 3 open reviews for ongoing activities[5]. Renaming all `master` branches on all repos to `main` --------------------------------------------------------------- lourot brought this topic and we discussed if we want to do that. Key point here is how much effort it will take to do for all the existing repo in term of make it working in CI/integration testing tooling/other scripts or not. And we should do it for new repo only. All these are unknown as of now. As first step, lourot will try the project-config importing of dummy project with 'main' branch from GitHub. Based on that, we will discuss it further. Z release cycle name ------------------------- Name nomination is closed, election for proposed names are in-progress. Follow the ML thread for updates[6]. Z release cycle Technical Election --------------------------------------- Election schedule is under review [7], please review and add your feedback. Remove the tags framework --------------------------------- yoctozepto has proposed the WIP patch to remove the tag framework, feel free to review and provide early feedback[8]. OpenStack Pain points discussion ---------------------------------------- No updates in this week. Stay tuned on the ML thread[9] and Rico will inform you about the next meeting details. TC position on release cadence ------------------------------------- Dan started the skip level upgrade in grenade and made its working for stable/wallaby to master[10]. TC is planning to meet and discuss the release cadence on 3rd Feb 16 UTC. Fixing Zuul config error ---------------------------- Requesting projects with zuul config error to look into those and fix them which should not take much time[11]. Project updates ------------------- * Retire js-openstack-lib (waiting on Adjutant to have new PTL/maintainer) [12] 4. How to contact the TC: ==================== If you would like to discuss or give feedback to TC, you can reach out to us in multiple ways: 1. Email: you can send the email with tag [tc] on openstack-discuss ML[13]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15 UTC [14] 3. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. [1] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting [2] https://governance.openstack.org/tc/goals/proposed/fips.html [3] https://review.opendev.org/c/openstack/governance/+/826243 [4] https://etherpad.opendev.org/p/tc-yoga-tracker [5] https://review.opendev.org/q/projects:openstack/governance+status:open [6] http://lists.openstack.org/pipermail/openstack-discuss/2022-January/026810.… [7] https://review.opendev.org/c/openstack/election/+/825017 [8] https://review.opendev.org/c/openstack/governance/+/822900 [9] http://lists.openstack.org/pipermail/openstack-discuss/2021-December/026245… [10] https://review.opendev.org/c/openstack/grenade/+/826101 [11] https://etherpad.opendev.org/p/zuul-config-error-openstack [12] https://review.opendev.org/c/openstack/governance/+/798540 [13] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [14] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0

Secure Boot VM issues (libvirt / SMM) | Secure boot requires SMM feature enabled
by Imran Hussain 28 Jan '22

28 Jan '22

Hi, Deployed Wallaby on Ubuntu 20.04 nodes. Having issues with libvirt XML being incorrect, I need the smm bit (<smm state='on'/>) and it isn't being added to the XML. Anyone seen this before? Or any ideas? More info below... Error message: : libvirt.libvirtError: unsupported configuration: Secure boot requires SMM feature enabled Versions: libvirt version: 6.0.0, package: 0ubuntu8.15 QEMU emulator version 4.2.1 (Debian 1:4.2-3ubuntu6.18) Nova 23.1.1 (deployed via kolla, so kolla/ubuntu-source-nova-compute:wallaby is the image) ovmf 0~20191122.bd85bf54-2ubuntu3.3 Context: https://specs.openstack.org/openstack/nova-specs/specs/wallaby/implemented/… Image metadata: hw_firmware_type: uefi hw_machine_type: q35 os_secure_boot: required os_hidden: false hw_disk_bus: scsi hw_qemu_guest_agent: yes hw_scsi_model: virtio-scsi hw_video_model: virtio os_require_quiesce: yes os_secure_boot: required os_hidden: false XML snippets taken from nova-compute.log: <sysinfo type="smbios"> <system> <entry name="manufacturer">OpenStack Foundation</entry> <entry name="product">OpenStack Nova</entry> <entry name="version">23.1.1</entry> <entry name="serial">2798e3fe-ffae-4c26-955b-ef150b849561</entry> <entry name="uuid">2798e3fe-ffae-4c26-955b-ef150b849561</entry> <entry name="family">Virtual Machine</entry> </system> </sysinfo> <os> <type machine="q35">hvm</type> <loader type="pflash" readonly="yes" secure="yes">/usr/share/OVMF/OVMF_CODE.ms.fd</loader> <nvram template="/usr/share/OVMF/OVMF_VARS.ms.fd"/> <boot dev="cdrom"/> <smbios mode="sysinfo"/> </os> <features> <acpi/> <apic/> </features> Other info: # cat /usr/share/qemu/firmware/40-edk2-x86_64-secure-enrolled.json { "description": "UEFI firmware for x86_64, with Secure Boot and SMM, SB enabled, MS certs enrolled", "interface-types": [ "uefi" ], "mapping": { "device": "flash", "executable": { "filename": "/usr/share/OVMF/OVMF_CODE.ms.fd", "format": "raw" }, "nvram-template": { "filename": "/usr/share/OVMF/OVMF_VARS.ms.fd", "format": "raw" } }, "targets": [ { "architecture": "x86_64", "machines": [ "pc-q35-*" ] } ], "features": [ "acpi-s3", "amd-sev", "enrolled-keys", "requires-smm", "secure-boot", "verbose-dynamic" ], "tags": [ ] }

2 3

[release] Release countdown for week R-8, Jan 31 - Feb 04
by Előd Illés 28 Jan '22

28 Jan '22

General Information ------------------- The following cycle-with-intermediary deliverables have not done any intermediary release yet during this cycle. The cycle-with-rc release model is more suited for deliverables that plan to be released only once per cycle. As a result, we have proposed[1] to change the release model for the following deliverables: ovn-octavia-provider ironic-prometheus-exporter ironic-python-agent-builder ironic-ui networking-baremetal networking-generic-switch patrole swift [1] https://review.opendev.org/q/topic:not-yet-released-yoga PTLs and release liaisons for each of those deliverables can either +1 the release model change, or propose an intermediary release for that deliverable. In absence of answer by the end of R-8week we'll consider that the switch to cycle-with-rc is preferable. We also published a proposed release schedule for the upcoming Zcycle. Please check out the separate thread: http://lists.openstack.org/pipermail/openstack-discuss/2022-January/026696.… Upcoming Deadlines & Dates -------------------------- Non-client library freeze: February 17th, 2022(R-6 week) Client library freeze: February 24th, 2022(R-5 week) Yoga-3 milestone: February 24th, 2022(R-5 week) Yoga final release: March 30th, 2022 Next PTG: April 4 - 8, 2022 (virtual) Előd Illés irc: elodilles

1 0

[sdk][devstack] openstacksdk-functional-devstack job failing on stable branches
by Brian Rosmaita 28 Jan '22

28 Jan '22

openstacksdk-functional-devstack began failing in the stable branches (xena through ussuri) shortly after 2022-01-24 11:53:49 with the error openstack.exceptions.ResourceNotFound: ResourceNotFound: 404: Client Error for url: https://{ip_address}:9696/v2.0/qos/policies/69e472c0-37d2-46e0-9b9e-727c962c5511/minimum_packet_rate_rules, The resource could not be found. for these four tests: openstack.tests.functional.network.v2.test_qos_minimum_packet_rate_rule.TestQoSMinimumPacketRateRule.test_find openstack.tests.functional.network.v2.test_qos_minimum_packet_rate_rule.TestQoSMinimumPacketRateRule.test_get openstack.tests.functional.network.v2.test_qos_minimum_packet_rate_rule.TestQoSMinimumPacketRateRule.test_list openstack.tests.functional.network.v2.test_qos_minimum_packet_rate_rule.TestQoSMinimumPacketRateRule.test_update job build history: https://zuul.opendev.org/t/openstack/builds?job_name=openstacksdk-functiona… It's passing in master and stable/{train,stein,rocky}. Anyone know what's up?

6 6