March 2025 - openstack-discuss - lists.openstack.org

about using sriov-agent
by Jiatong Shen 11 Mar '25

11 Mar '25

Hello Experts, I am learning using SR-IOV to enable faster network access. I do not have a smartNIC so I am only talking about regular VF device passthrough. Right now, I configure Nova and use regular device passthrough flavor to create an instance. It works but since the PF device is a trunk network port, I have to configure sub interface manually in the guest. I find that I can only use neutron to configure SR-IOV VF devices (bandwidth, spoofcheck etc.). I am not trying it yet but I would like to ask if I use SR-IOV through neutron, does neutron's sriovagent will configure vlan id automatically such that I do not need to configure it inside the guest? if answer is yes, could you show me the related code? Thank you for your help. -- Best Regards, Jiatong Shen

4 8

[tempest] dynamically defined tests
by jerome.defavereau＠uclouvain.be 11 Mar '25

11 Mar '25

Hi, I'm currently trying to use tempest to run a simple series of tests on each of my hypervisors. I would like to have a separate test for each hypervisor instead of a single test for all. For that I need to dynamically define tests. I wrote a simple plugin to run the tests and then I use "sertattr" in a loop to define one "test_" method per hypervisor. The plugin is listed properly, as well as the tests, but when I run them using a regexp or the full test path I get "The test run didn't actually run any tests". I was able to run them using: "python -m unittest discover -s ./multi_hypervisor_tempest_plugin" but tempest run fails. Would anyone have wisdom to share ? Thanks !

1 0

[tc][all] OpenStack Technical Committee Weekly Summary and Meeting Agenda (2025.1/R-3)
by Goutham Pacha Ravi 11 Mar '25

11 Mar '25

Hello Stackers, We're three weeks away from the coordinated 2025.1 "Epoxy" release [1]. The release will be published on 2025-04-02. This week, we're expecting to publish release candidates for all project deliverables that follow the "cycle-with-rc" release model [2]. In the past week, the OpenStack TC appointed project team leaders for Barbican (Mauricio Harley/mharley), Masakari (Suzhengwei/suzhengwei), and Zaqar (Hao Wang/wanghao) project teams. There's a pending appointment to the OpenStack Charms project [3] that we'll wrap up this week. The Oslo team re-nominated DPL liaisons, and the TC is going through the process of naming its chair and vice-chair for its current term. The community convened alongside Southern California Linux Expo (SCaLE) 2025 for an OpenInfra Days North America event. The event was well attended and featured close to 40 sessions spread across two days. You can watch most of the recorded proceedings as they were streamed live on both days [4][5][6]. We also celebrated OpenStack's 15th birthday with cake! If you missed this one, please check out upcoming birthday celebrations organized by different local user groups around the world [7]. === Weekly Meeting === The OpenStack Technical Committee (TC) held its weekly meeting primarily via video call [8], with action items and minutes documented in IRC [9]. The agenda covered past action items, PTL election results, leaderless projects, and a discussion on the format of TC meetings. A number of new Project Team Leads who will take charge of several OpenStack project teams next week are not core reviewers of the deliverables their teams manage. The general consensus was that a PTL does not have to be a core reviewer, as long as they collaborate effectively with the cores. PTLs should focus on driving consensus rather than making unilateral decisions—whether technical or otherwise. The TC trusts that if no one else nominates or objects, a lone PTL nominee has the support of the team. I personally believe that new and relatively new contributors can bring energy to the PTL role by being inquisitive and enthusiastic. I hope that the core team nurtures these qualities to integrate them into the fold sooner rather than later. The TC discussed why certain project teams that were deemed "leaderless" at the end of this past election consistently require appointments. We're learning from volunteers who have stepped up to lead each of these teams whether they would suggest any changes to the election process. Finally, we spent some time discussing whether the TC's monthly video meetings were useful and what the downsides were. We'll revisit this topic at the upcoming Project Teams Gathering with a wider audience. The next meeting of the OpenStack Technical Committee is today, 2025-03-11. Please find the agenda on the meeting's wiki page [10]. I hope you'll be able to join us. === Governance Proposals === ==== Merged ==== Add suzhengwei as PTL for Masakari | https://review.opendev.org/c/openstack/governance/+/943226 Appoint Hao Wang as PTL for OpenStack Zaqar | https://review.opendev.org/c/openstack/governance/+/943338 Switch back Oslo to DPL model | https://review.opendev.org/c/openstack/governance/+/942793 Appoint Mauricio Harley as PTL for Barbican | https://review.opendev.org/c/openstack/governance/+/942907 Add gouthamr's nomination for 2025.2 TC chair | https://review.opendev.org/c/openstack/governance/+/943204 Add TC chair nomination folder for 2025.2 | https://review.opendev.org/c/openstack/governance/+/943203 ==== Open for Review ==== Appoint Felipe Reyes as PTL for OpenStack Charms | https://review.opendev.org/c/openstack/governance/+/943254 Add Cinder Huawei charm | https://review.opendev.org/c/openstack/governance/+/867588 Resolve to adhere to non-biased language | https://review.opendev.org/c/openstack/governance/+/934907 === Upcoming Events === 2025-03-11: OpenInfra Board Meeting: https://board.openinfra.org/ 2025-04-02: OpenStack 2025.1 ("Epoxy") Release 2025-04-07 - 2025-04-12: OpenInfra PTG Thank you very much for reading! On behalf of the OpenStack TC, Goutham Pacha Ravi (gouthamr) OpenStack TC Chair [1] 2025.1 "Epoxy" Release Schedule: https://releases.openstack.org/epoxy/schedule.html [2] cycle-with-rc release model: https://releases.openstack.org/reference/release_models.html#cycle-with-rc [3] Appoint Felipe Reyes as PTL for OpenStack Charms: https://review.opendev.org/c/openstack/governance/+/943254 [4] OpenInfraDays @ SCaLE 2025, Thursday Stream 1: https://www.youtube.com/watch?v=W9OmGdtJAAE [5] OpenInfraDays @ SCaLE 2025, Thursday Stream 2: https://www.youtube.com/watch?v=prIwZshr55U [6] OpenInfraDays @ SCaLE 2025, Friday: https://www.youtube.com/watch?v=Fv0Bdw6pBlk [7] Celebrating 15 years of OpenStack: https://www.openstack.org/blog/celebrating-15-years-of-openstack/ [8] TC Meeting Video Recording, 2025-03-04: https://youtu.be/NMDrz1N6ogo [9] TC Meeting IRC Log 2025-03-04: https://meetings.opendev.org/meetings/tc/2025/tc.2025-03-04-18.00.log.html [10] TC Meeting Agenda, 2025-03-11: https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting

1 0

openstack ansible lxc containers
by engineer2024 10 Mar '25

10 Mar '25

Using the lxc-container-create playbook, how to. create a container with a specific name and specific release ? openstack-ansible lxc-containers-create.yml -e "container_name=testing" -e "lxc_container_distribution=ubuntu" -e "lxc_container_release=jammy" --limit 'test' is throwing an error. it is trying to attach to the 'testing' container when it does not exist in the first place. I want the playbook to create one with that name ? So, what's the workaround ? --- module_stderr": "lxc-attach: testing: attach.c: get_attach_context: 405 Connection refused - Failed to get init pid\nlxc-attach: testing: attach.c: lxc_attach: 1469 Connection refused - Failed to get attach context\n", "module_stdout": "", "msg": "MODULE FAILURE\nSee stdout/stderr for the exact error", ----

2 1

[telemetry] Nominate Juan Larriba to Telemetry core
by Takashi Kajinami 10 Mar '25

10 Mar '25

Hi, As some of you may know, current telemetry core team is quite small due to some cores shifting their focus recently. (As far as I see Matthius and I are the cores around the community recently). On the other hand we have seen revived interest in adding new features to telemetry services. To make sure these effort may receive appropriate feedback, I'd like to nominate Juan as a new Telemetry project core. He has been contributing the project for some time, and I've recently seen his consistent presence to review patches. In addition he volunteered to be a Telemetry PTL for the next cycle with his continued interest to keep the project active. If I don't hear any objections for one week, I'll add Juan to the group. Also, I'd like to take this chance to mention that we are really happy to see anyone who is interested in helping the project and appreciate any help to review proposed changes or maintain the project (so that we can invite them to the core group as well). Thank you, Takashi Kajinami -- Takashi Kajinami irc: tkajinam github: https://github.com/kajinamit launchpad: https://launchpad.net/~kajinamit

2 4

[neutron] bug deputy report for 2025w10
by Bence Romsics 10 Mar '25

10 Mar '25

Hi Neutron Team! Last week we had the following new bug reports: Gate failures: * https://bugs.launchpad.net/neutron/+bug/2100776 test_securitygroup(ovs-openflow) fullstack test random failure with Time out exception unassigned * https://bugs.launchpad.net/neutron/+bug/2101165 Random failure in test_established_tcp_session_after_re_attachinging_sg unassigned * https://bugs.launchpad.net/neutron/+bug/2101166 Random failure in dvr ovs grenade jobs to ping vm post upgrade unassigned * https://bugs.launchpad.net/neutron/+bug/2100806 Intermittent test_batch_notifier failure fix proposed: https://review.opendev.org/c/openstack/neutron/+/943212 High: * https://bugs.launchpad.net/neutron/+bug/2101150 User who is not owner of the SG can create/delete rules in the shared SG assigned to Slawek * https://bugs.launchpad.net/neutron/+bug/2101063 [OVN] min-bw QoS policy cannot be defined alone, exception raised fix proposed: https://review.opendev.org/c/openstack/neutron/+/943664 Medium: * https://bugs.launchpad.net/neutron/+bug/2101140 [OVN] Make LSP up/down events processing resilient to IDL disconnections fix proposed: https://review.opendev.org/c/openstack/neutron/+/943404 * https://bugs.launchpad.net/neutron/+bug/2101162 [OVN] Use HA_Chassis_Group for tunnelled gateway network LRPs WIP fix: https://review.opendev.org/c/openstack/neutron/+/938134 * https://bugs.launchpad.net/neutron/+bug/2100938 Assign HA_Chassis_Group to all LRPs for tunnelled gateway assigned to Rodolfo Eventlet removal: * https://bugs.launchpad.net/neutron/+bug/2101076 [eventlet-removal] Remove the usage of eventlet in the MacVTap agent unassigned RFEs: * https://bugs.launchpad.net/neutron/+bug/2100770 [RFE] Make alembic_migration scripts in neutron idempotent * https://bugs.launchpad.net/neutron/+bug/2073254 nova-compute optional wait for vif-plugged in ovn usecase Further triage needed: * https://bugs.launchpad.net/neutron/+bug/2101077 neutron-bgp-agent dies with debug log + json Info requested from reporter on reproduction method * https://bugs.launchpad.net/neutron/+bug/2100752 Severe Packet Loss During Live Migration Due to Premature Route Advertisement in Neutron BGP Dynamic Routing Edit Lajos promised to triage this Cheers, Bence

1 0

using compute_monitors option for nova
by Jiatong Shen 08 Mar '25

08 Mar '25

Hello Experts, I hope this email finds you well. I am researching the "compute_monitors" option for nova and would like to find out what it can do. By some googling I find that by enabling this option, the compute_nodes table will store extra metrics and reflect the vcpu usage on the compute node. My question is is it possible to also save memory usage? Besides, is this option still supported in the long term? Thank you very much for the help. -- Best Regards, Jiatong Shen https://docs.openstack.org/ocata/config-reference/compute/config-options.ht…

2 2

[dev][ptl][release] Cycle highlights reminder (2025.1/Epoxy)
by Jeremy Stanley 07 Mar '25

07 Mar '25

Just a reminder in case anyone missed it: we've officially reached the deadline for merging 2025.1/Epoxy release highlights, but if anyone has something they want to mention then now is the time to write, push and approve it! The OpenInfra marketing machine is getting ready to digest what they find at https://releases.openstack.org/epoxy/highlights.html and put together a press release and package for news outlets. They're interested in whatever you're excited to include, but especially anything related to AI, digital sovereignty, security, or VMware feature parity. Please get your remaining highlights in ASAP!!! -- Jeremy Stanley

1 0

[horizon] Propose Jan Jašek to Horizon core
by Tatiana Ovchinnikova 07 Mar '25

07 Mar '25

Hello team, As it was discussed at our weekly meeting, I would like to add Jan Jašek to the OpenStack Horizon core team. Jan has been contributing to the Horizon project since 2022, and his impact is tremendous. His improvement and maintenance of Horizon test jobs made them significantly more stable, and Jan's reviews are always fast and valuable. Thank you Jan! Regards, Tatiana

1 0

[release] Release countdown for week R-3
by Thierry Carrez 07 Mar '25

07 Mar '25

Development Focus ----------------- The Release Candidate (RC) deadline is next Friday, March 14th, 2025. 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/2025.1 branch will be cut. This branch will track the 2025.1 Epoxy release. Once stable/2025.1 has been created, the master branch will be ready to switch to 2025.2 Flamingo development. While the master branch will no longer be feature-frozen, please prioritize any work necessary for completing 2025.1 Epoxy plans. Release-critical bugfixes will need to be merged in the master branch first, then backported to the stable/2025.1 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 the master branch. 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/2025.1 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 the master branch (which will technically then be Flamingo development) 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 2025.1 Epoxy release so far. Finally, 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: March 14th, 2025 (R-3 week) Final RC deadline: March 28th, 2025 (R-1 week) Final 2025.1 Epoxy release: April 2nd, 2025 Project Teams Gathering (virtual): April 7th-11th, 2025 -- Thierry Carrez (ttx)

1 0