- openstack-discuss - lists.openstack.org

[all] Failing sqlalchemy-tips jobs should now be passing again
by Stephen Finucane 10 Nov '23

10 Nov '23

Just FYI, for projects that have sqlalchemy-tips jobs that have been failing recently, they should now be passing again. The root cause was neither sqlalchemy nor alembic but rather oslo.utils [1]. It was fixed in oslo.utils 6.3.0 which was released [2] roughly an hour ago. A recheck should be sufficient to clear errors and as these tips jobs only run on master there should be no issues with stable branches. A further point to add: while I appreciate that broken gates are never a good thing, I would be careful making these jobs non-voting. I've already seen a few instances where SQLAlchemy 2.0 support has regressed and I for one have no desire to re-herd cats as we push to get SQLAlchemy uncapped in the coming weeks. If this happens again then we can re-examine things, naturally. Cheers, Stephen [1] https://review.opendev.org/c/openstack/oslo.utils/+/900343 [2] https://review.opendev.org/c/openstack/releases/+/900382

2 2

[kolla-ansible] group_vars question
by Satish Patel 09 Nov '23

09 Nov '23

Folks, I have multiple kinds of nic in cloud and want to configure SRIOV so instead of defining the following variable for each compute node, I would like to create a group and apply config to the groups. Am I right here to define groups like the following or is there a better way to handle this? What is the default path of group_vars and hosts_vars in kolla-ansible? # vi /etc/kolla/group_vars/sriov_eno49.yml neutron_sriov_physnet_mappings: physnet1: eno49 # vi /etc/kolla/group_vars/sriov_eno50.yml neutron_sriov_physnet_mappings: physnet1: eno50 # vi multinode [sriov_eno49] comp1 comp2 comp3 [sriov_eno50] comp4 comp5 comp6

2 2

[Diversity] Diversity and Inclusion WG November Meeting Change and New Time
by Amy Marrich 09 Nov '23

09 Nov '23

Due to travel next week we are bumping the D&I WG meeting to November 21st at our new winter time of 15:00 UTC. As always we welcome members of all the OpenInfra projects to join us to discuss diversity and WG related topics. Amy (spotz)

1 0

[kolla-ansible] Not to install openvswitch on sriov_agent compute nodes
by Satish Patel 09 Nov '23

09 Nov '23

Folks, I have pure sriov compute nodes where I don't want to deploy openvswitch because SRIOV agents do pass through PCI bugs to VM directly. Currently all my SRIOV compute nodes have two agents running. neutron_openvswitch_agent neutron_sriov_agent I don't think "neutron_openvswitch_agent" has any role on sriov compute nodes. If I want to tell kolla-ansible not to deploy neutron_openvswitch_agent on X compute node then how do I tell. Are there any easy ways to turn it off? ~S

1 0

hi
by Tecstim 09 Nov '23

09 Nov '23

1 0

[kolla-ansible] sriov setup
by Satish Patel 09 Nov '23

09 Nov '23

Folks, I am following this guide to deploy sriov compute with kolla-ansible (I am not using kayobe) - https://www.stackhpc.com/sriov-kayobe.html In the above doc last section neutron sriov agent, I am using the same code but those variables are not reflecting. It just prints everything as it is. # cat /etc/kolla/host_vars/os1-bos-sriov-comp-001.yml neutron_sriov_physnet_mappings: physnet1: eno49 # cat /etc/kayobe/kolla/config/neutron/sriov_agent.ini {% raw %} [sriov_nic] physical_device_mappings = {% for dev, physnet in sriov_physnet_mappings.items() %}{{ (loop.index0 > 0)|ternary(',','') }}{{ physnet }}:{{ dev }}{% endfor %} exclude_devices = {% endraw %} After running deploy it just prints the entire file as its in sriov_agent.ini file instead of proper values of variable. Does kolla-ansible support the above code?

2 2

[ptls] [tc] 2023 OpenStack Deployment Data
by Allison Price 09 Nov '23

09 Nov '23

Hi everyone, Apologies for sending this during the PTG as I intended to send this prior, but below is a link to the anonymized data including responses to many project or TC contributed questions. I have removed a significant number of fields to preserve the anonymity of the organizations, but if there is a particular data point that would help your team, please let me know. Cheers, Allison https://docs.google.com/spreadsheets/d/1ehlabuqOnNK4M7xtN1GXvhLoeHn4JBaISih…

2 1

[ironic] Hold approvals for various gate breakages
by Jay Faulkner 08 Nov '23

08 Nov '23

Hey Ironicers, We have a couple of gate unhappinesses: - bifrost gate is busted until this lands: https://review.opendev.org/c/openstack/bifrost/+/900487 - Ironic gate is busted until the new oslo.utils is released and added to requirements (we vote on a sqlalchemy 2x job) -- https://review.opendev.org/c/openstack/releases/+/900382 appears to be the next change in that chain. Just ensuring folks know what's going on! Please avoid approving changes to these repos until the issues are resolved. Thanks, Jay Faulkner Ironic PTL

1 0

[ironic] 2024.1 vPTG Notes & Work Items
by Jay Faulkner 08 Nov '23

08 Nov '23

Hi all, In typical Ironic tradition, we've documented the outcome of the PTG in a spec: https://specs.openstack.org/openstack/ironic-specs/priorities/2024-1-workit… -- please review it for information on work we plan on at least trying to start this cycle :). For full notes, please see the etherpad: https://etherpad.opendev.org/p/ironic-ptg-october-2023. Thanks, Jay Faulkner Ironic PTL

1 0

[FOSDEM] Call for participation: Virtualization and Cloud infrastructure Room at FOSDEM 2024
by Piotr Kliczewski 08 Nov '23

08 Nov '23

We are excited to announce that the call for proposals is now open for the Virtualization and Cloud infrastructure devroom at the upcoming FOSDEM 2024, to be hosted on February 3rd 2024. This devroom is a collaborative effort, and is organized by dedicated folks from projects such as OpenStack, Xen Project, KubeVirt, QEMU, KVM, and Foreman. We would like to invite all those who are involved in these fields to submit your proposals by December 8th, 2023. About the Devroom The Virtualization & IaaS devroom will feature session topics such as open source hypervisors or virtual machine managers such as Xen Project, KVM, bhyve and VirtualBox as well as Infrastructure-as-a-Service projects such as KubeVirt, Apache CloudStack, OpenStack, QEMU and OpenNebula. This devroom will host presentations that focus on topics of shared interest, such as KVM; libvirt; shared storage; virtualized networking; cloud security; clustering and high availability; interfacing with multiple hypervisors; hyperconverged deployments; and scaling across hundreds or thousands of servers. Presentations in this devroom will be aimed at developers working on these platforms who are looking to collaborate and improve shared infrastructure or solve common problems. We seek topics that encourage dialog between projects and continued work post-FOSDEM. Important Dates Submission deadline: 8th December 2023 Acceptance notifications: 10th December 2023 Final schedule announcement: 15th December 2023 Devroom: 3rd February 2024 Submit Your Proposal All submissions must be made via the Pretalx event planning site[1]. It is a new submission system so you will need to create an account. If you submitted proposals for FOSDEM in previous years, you won’t be able to use your existing account. During submission please make sure to select Virtualization and Cloud infrastructure from the Track list. Please fill out all the required fields, and provide a meaningful abstract and description of your proposed session. Submission Guidelines We expect more proposals than we can possibly accept, so it is vitally important that you submit your proposal on or before the deadline. Late submissions are unlikely to be considered. All presentation slots are 30 minutes, with 20 minutes planned for presentations, and 10 minutes for Q&A. All presentations will be recorded and made available under Creative Commons licenses. In the Submission notes field, please indicate that you agree that your presentation will be licensed under the CC-By-SA-4.0 or CC-By-4.0 license and that you agree to have your presentation recorded. For example: "If my presentation is accepted for FOSDEM, I hereby agree to license all recordings, slides, and other associated materials under the Creative Commons Attribution Share-Alike 4.0 International License. Sincerely, <NAME>." In the Submission notes field, please also confirm that if your talk is accepted, you will be able to attend FOSDEM and deliver your presentation. We will not consider proposals from prospective speakers who are unsure whether they will be able to secure funds for travel and lodging to attend FOSDEM. (Sadly, we are not able to offer travel funding for prospective speakers.) Code of Conduct Following the release of the updated code of conduct for FOSDEM, we'd like to remind all speakers and attendees that all of the presentations and discussions in our devroom are held under the guidelines set in the CoC and we expect attendees, speakers, and volunteers to follow the CoC at all times. If you submit a proposal and it is accepted, you will be required to confirm that you accept the FOSDEM CoC. If you have any questions about the CoC or wish to have one of the devroom organizers review your presentation slides or any other content for CoC compliance, please email us and we will do our best to assist you. Questions? If you have any questions about this devroom, please send your questions to our devroom mailing list. You can also subscribe to the list to receive updates about important dates, session announcements, and to connect with other attendees. See you all at FOSDEM! [1] <https://penta.fosdem.org/submission/FOSDEM17> https://pretalx.fosdem.org/fosdem-2024/cfp [2] virtualization-devroom-manager at fosdem.org

1 0