January 2025 - openstack-discuss - lists.openstack.org

[dev] Invitation to participate in a survey on flaky tests spanning multiple OpenStack projects
by xiao＠ait.kyushu-u.ac.jp 15 Jan '25

15 Jan '25

Hello there, My name is Tao Xiao, Assistant Professor at Kyushu University (Japan), and togather with a team from Canada and China. Our research specifically investigates cross-project flakiness by analyzing information available on the Gerrit Code Review platform. Through our study, we have observed a significant number of flaky tests spanning multiple OpenStack projects and categorized several potential causes behind this phenomenon. Our next step is to validate our empirical findings and gather real developers' perceptions to improve the OpenStack ecosystem through a developer survey. If you have at most 10 minutes, we have designed a simple survey to capture your perceptions. The survey link is here: https://forms.gle/dUMWRL8MNALQE6kG8 This questionnaire is totally anonymized, and the survey was approved by the Kyushu University, Japan ethics board (2024-26). Again, thank you so much for your time, and please feel free to contact us for more information. Tao Xiao on Behalf of Our Team Assistant Professor Faculty of Information Science and Electrical Engineering Kyushu University, Japan xiao(a)ait.kyushu-u.ac.jp <mailto:xiao@ait.kyushu-u.ac.jp> Team Members and their homepages: Tao Xiao – https://tao-xiao.github.io/ Dong Wang – https://dong-w.github.io/ Shane McIntosh – https://shanemcintosh.org/ Hideaki Hata – https://hideakihata.github.io/ Yasutaka Kamei – https://posl.ait.kyushu-u.ac.jp/~kamei/

1 0

[openstack][octavia] How clients can debug their LB
by Nguyễn Hữu Khôi 15 Jan '25

15 Jan '25

Hello. I would like to know how clients can debug their LB such as access log or monitor LB performance? Thank you. Regards Nguyen Huu Khoi

5 7

[ironic] Ironic-Lib being deprecated
by Jay Faulkner 15 Jan '25

15 Jan '25

Hi all, As many of you know, at the recent PTG the Ironic community made a decision to move any functionality out of ironic-lib into ironic / ironic-python-agent. This library has been documented, since it's inception, as for use by Ironic projects only, so there should be little to no impact to deployers other than having one less python package to deploy in their IPA ramdisks and Ironic services. We will keep the repository's stable (and unmaintained) branches open for as long as their Ironic/IPA counterparts are also supported in order to fulfill our support obligation. Remaining patches to complete this deprecation are here: https://review.opendev.org/q/topic:%22ironic-lib-deprecation%22 -- please reach out if there are any questions or concerns. I thought it wise to inform the mailing list of this change. We'll ensure it's highlighted in Ironic cycle highlights for epoxy as well. Thanks, Jay Faulkner

1 0

[release] [upgrades] Seeking OpenStack Upgrade Success Stories
by Allison Price 15 Jan '25

15 Jan '25

Hi everyone, Ahead of the OpenStack 2025.1 ‘Epoxy’ release, the OpenInfra Foundation marketing team wants to work with the OpenStack community to highlight how upgrades have become simplified with the implementation of SLURP. This will include leveraging the governance docs to draft articles around the upstream progress as well as operator success stories for organizations who have upgraded their own deployments or customer deployments to a SLURP release. The goal is to further increase awareness on the improvements made to the upgrade process and reduce common perceptions that OpenStack upgrades remain complex. Here [1] is an etherpad where we are collecting names of volunteers who can either review materials promoting the upstream progress or share operator success stories. If you have any questions, please let me know. [1] https://etherpad.opendev.org/p/OpenStackUpgrades Cheers, Allison Allison Price VP of Marketing & Community p: +1-214-686-6821

1 0

[all] Foundation Individual Director election voting underway
by Jeremy Stanley 15 Jan '25

15 Jan '25

Voting is open now for the 2025 OpenInfra Foundation Individual Director Election. You must have joined the Open Infrastructure Foundation as an Individual Member by Sunday, July 14, 2024 to vote in this election, per the bylaws: https://openinfra.org/legal/bylaws Individual Directors serve as board representatives for the Individual Members who elect them, so are the most effective way we as participants in OpenStack can influence board decisions on the general direction of our supporting foundation. Voting in these elections, once you're eligible to do so, is also necessary in order to maintain your individual membership. To vote, check your email (or your spam folder) for your personal link to vote. It will have been sent to the primary address in your foundation member profile. The subject line is: "OpenInfra Foundation 2025 Individual Director Election" You can review the candidates here: https://openinfra.dev/election/2025-individual-director-election/candidates Voting will close this Friday, January 17th, 2025 at 1900 UTC. Please contact secretary(a)openinfra.dev with any questions you may have about the election. -- Jeremy Stanley

1 0

[kolla] [wallaby] [openvswitch]
by Albert Braden 15 Jan '25

15 Jan '25

One of our busiest clusters was rebuilt on Wallaby a few months ago (kolla-ansible) and deletions are taking a long time for VMs on some hypervisors. When I look at the ovs-vswitchd.log on the slow hypervisors I see lots of errors that apparently refer to a missing VM interface: 2024-12-27T19:06:10.482Z|01793|bridge|WARN|could not open network device qvo0430a2f7-cd (No such device) For most network devices I see "added" and "deleted" lines in the log. This one has an "added" line but no "deleted". I tried restarting the neutron_openvswitch_agent and openvswitch_vswitchd containers but that didn't make a difference. How can I get OVS to stop choking on this missing interface?

2 17

[ironic][networking] Baremetal Networking Working Group resuming 2/15
by Julia Kreger 15 Jan '25

15 Jan '25

Greetings everyone, Now that we are in the new year and a number of ironic contributors are back from PTO, we're going to resume the networking meetings. One aspect which we discussed in December was to focus the discussion. To that end, after some follow-up discussion, we're going to try and focus the meeting a bit more using the agenda. We have an agenda posted to the etherpad[0], along with a meeting link. If you have additional topics, please feel free to add to that agenda, but also be mindful between the use cases of standalone usage and openstack integrated usage and explicitly call out the use case. As a reminder, the meeting will be at 1500 UTC. Meeting link in the etherpad! Thanks! -Julia [0]: https://etherpad.opendev.org/p/ironic-networking

1 0

[publiccloud-sig] Reminder: first meeting of the new year - January 15th at 0800 UTC
by Felix Kronlage-Dammers 14 Jan '25

14 Jan '25

Hi everyone, This upcoming Wednesday (January 15th) the next meeting of the publiccloud-sig is going to happen. We’ll be meeting at 0800 UTC here: https://meetpad.opendev.org/publiccloud-sig See also here for all other details: https://wiki.openstack.org/wiki/PublicCloudSIG felix -- Felix Kronlage-Dammers Tel.: +49-30-206539-205 | Matrix: @fkronlage:matrix.org | fkr(a)osb-alliance.com

1 0

[all][tc] Election dates for the 2025.2 cycle
by Sławek Kapłoński 14 Jan '25

14 Jan '25

Hi, To align with the proposal from Goutham [1] we have updated election calendar for the upcoming elections [2] to make voting period slightly longer thus nomination will also start earlier. Please be aware of it. New calendar looks like: Release is at: 2025-04-02 Latest possible completion is at: 2025-03-19 Moving back to Wednesday: 2025-03-19 PTL Election from 2025-02-26T23:45 to 2025-03-19T23:45 TC Election from 2025-02-26T23:45 to 2025-03-19T23:45 TC Campaigning from 2025-02-19T23:45 to 2025-02-26T23:45 PTL Nominations from 2025-02-05T23:45 to 2025-02-19T23:45 TC Nominations from 2025-02-05T23:45 to 2025-02-19T23:45 Set email_deadline to 2025-02-19T00:00 Setting TC timeframe end to email_deadline Begining of 2024.2 Cycle @ 2024-03-15 00:00:00+00:00 End of 2025.1 cycle @ 2025-02-19 00:00:00+00:00 Election timeframe: 341 days, 0:00:00s --- [1] https://review.opendev.org/c/openstack/governance/+/937741 [2] https://review.opendev.org/c/openstack/election/+/938782/ -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0

Dalmatian Devstack: Empty Port Binding section in Horizon
by berndbausch＠gmail.com 14 Jan '25

14 Jan '25

Is there a known bug, either in Devstack or Horizon, that prevents Neutron port binding details from being displayed? My googling did not find anything. As admin, I open a port's details, and in the Binding section at the end of the page, all I get is a bold text "VNIC Type". The CLI command "openstack port show" does provide the details. Also on a Xena Devstack, Horizon displays them[1]. Horizon's setup.py seems to be identical on both releases, as far as Neutron configuration is concerned. Thanks for any input. Bernd. [1] The Binding details I expect: Binding VNIC Type Normal Host xena-202 Profile None VIF Type ovs VIF Details connectivity l2 port_filter True ovs_hybrid_plug False datapath_type system bridge_name br-int

2 1