February 2024 - openstack-discuss

[puppet] EOL plan of wallaby, xena and yoga
by Takashi Kajinami 06 Feb '24

06 Feb '24

Hello, I'm sending this as an early announcement of my current plan about these old stable branches in Puppet OpenStack project. Because we've not see any interest to backport changes to these stable branches and we have limited capacity to maintain our project, I'd propose transitioning EOL these old stable branches by the following steps. * stable/yoga is transitioned to unmaintained/yoga but we may not work on maintaining it now (which eventually means it's abandoned right after its transition to unmaintained status). We'll move it to EOL at the next cadence, when zed is transitioned to unmaintained). * wallaby and xena will become immediate candidates for EOL so we'll just move the EOL process forward. If you have any concern, then please let me know. We'll formally work on these processes in the release patches. [1] https://docs.openstack.org/project-team-guide/stable-branches.html#unmainta… -- Takashi Kajinami irc: tkajinam github: https://github.com/kajinamit launchpad: https://launchpad.net/~kajinamit

1 0

[puppet] Retiring puppet-qdr
by Takashi Kajinami 06 Feb '24

06 Feb '24

Hello, Let me restore my old proposal[1] about puppet-qdr. # I lost access to my old emails so I'm starting a new thread. In the previous mail I proposed deprecation instead of retirement, because the module has been used by TripleO. However I noticed that TripleO is now under the process of complete retirement[2]. So, I'd like to revise my proposal, and propose retiring the module completely. Please let me know if you have any concern with this module retired. Unless I hear any objections, I'll start the official retirement process. [1] https://lists.openstack.org/pipermail/openstack-discuss/2023-August/034742.… [2] https://review.opendev.org/c/openstack/governance/+/905145 Thank you, Takashi Kajinami irc: tkajinam

2 2

[neutron] Bugs deputy report January 29th to February 4th
by Miguel Lavalle 05 Feb '24

05 Feb '24

Here's this week's bugs deputy report: Critical ====== https://bugs.launchpad.net/neutron/+bug/2051831 [ovn] neutron-ovn-tempest-slow job fail tests relying on FIP. Assignee ralonsoh. Proposed fix: https://review.opendev.org/c/openstack/neutron/+/907312 High ==== https://bugs.launchpad.net/neutron/+bug/2051729 issue dhcp cleaning stale devices process when enable action. Assignee Sahid Orentino. Proposed fix: https://review.opendev.org/c/openstack/neutron/+/907250 https://bugs.launchpad.net/neutron/+bug/2051928 tests - Python 3.12 - TypeError: Object of type _SentinelObject is not JSON serializable. Needs an owner https://bugs.launchpad.net/neutron/+bug/2051935 [OVN] SNAT only happens for subnets directly connected to a router. Owner haleyb Medium ====== https://bugs.launchpad.net/neutron/+bug/2051510 [OVN] Audit the L2/L3 extensions support. Assignee: https://bugs.launchpad.net/neutron/+bug/2051869 OVS agent DHCP extension fail if not set subnet gateway_ip. Assigned to Liu Yulong https://bugs.launchpad.net/neutron/+bug/2052367 neutron-keepalived-state-change run neutron-rootwrap-daemon anyway regardless of config. Assigned to Liu Yulong. Proposed fix https://review.opendev.org/c/openstack/neutron/+/653378 Need follow up: ============ https://bugs.launchpad.net/neutron/+bug/2051863 Race condition during VM creation - could not open network device tapXXX (No such device). Liu Yulong created an associated LP bug for Nova, but might require a follow from us in the future. Incomplete ========= https://bugs.launchpad.net/neutron/+bug/2052299 neutron-tempest-plugin - HaRoutersTest.test_convert_legacy_router Test "ha" Check Error

1 0

[publiccloud-sig] Reminder - next meeting February 7th - 0800 UTC
by Felix Kronlage-Dammers 05 Feb '24

05 Feb '24

Hi everyone, This Wednesday (February 7th) the next meeting of the public cloud sig is going to happen. Since the majority of participants in the sessions started to like the videocalls, we’ll be doing this as a videocall again. We’ll be meeting at 0800 UTC here: https://conf.scs.koeln:8443/OIF-public-cloud-sig See also here for all other details: https://wiki.openstack.org/wiki/PublicCloudSIG Some of us met at FOSDEM last weekend, so we can share a bit about our discussions and findings there :) See you Wednesday! felix -- Felix Kronlage-Dammers Product Owner IaaS & Operations Sovereign Cloud Stack Sovereign Cloud Stack — standardized, built and operated by many Ein Projekt der Open Source Business Alliance - Bundesverband für digitale Souveränität e.V. Tel.: +49-30-206539-205 | Matrix: @fkronlage:matrix.org | fkr(a)osb-alliance.com

1 0

[storlets] Transition wallaby, xena and yoga to EOL
by Takashi Kajinami 05 Feb '24

05 Feb '24

Hello, As you know, stable/yoga already reached its end of maintenance phase and is now being transitioned to the unmaintained branch. Because we've not seen any attempt to backport changes to it and even older branches, I'd propose retiring yoga and older branches (wallaby and xena) instead of keeping inactive branches. Please let me know if you have any concern. -- Takashi Kajinami irc: tkajinam github: https://github.com/kajinamit launchpad: https://launchpad.net/~kajinamit

1 1

[fwaas][devstack] help configuring dashboard
by garcetto 05 Feb '24

05 Feb '24

good morning, is there some tutorial on how to configure fwaas web dashboard on devstack? thank you.

2 1

[nova] Help with support to SGX
by Winicius Allan 05 Feb '24

05 Feb '24

Hello o/ Anyone already work with Nova to provide VMs with SGX support?

6 7

nova-compute down and no data in log file
by russell.stather＠ignitiongroup.co.za 05 Feb '24

05 Feb '24

nova-compute showing as enabled but down. Log files are not being written to. Service is showing as running. This is a juju installation. Have tried pausing and resuming the nova-compute, and rabbitmq, and nova-cloud-controller.

1 0

[cinder] volume type properties / extra_specs
by Josephine Seifert 05 Feb '24

05 Feb '24

Hi, I was experimenting with the extra_specs of volume types for a project. And while I was able to set and unset properties freely, the volumes created from volume types with random properties could not be created. They always went into Error state. When I removed the properties from the volume type, volumes could be created again. Is it meant to behave like this? So in other words: Are custom properties not allowed for volume types? And if so, why am I allowed to set custom properties? I would expect an Error to happen in the volume type set --property ... process and not when creating a volume. greetings. Josephine (Luzi)

2 2

[oslo] Feature freeze.
by Daniel Bengtsson 04 Feb '24

04 Feb '24

Hi there, Just a friendly reminder that oslo's feature freeze will happen in 2 weeks (R-7 - Feb 12 - Feb 16). To know more about the freeze, we have a policy[1] that discusses it. The main thing is that if you have features you want to get into Oslo libraries this cycle, please make sure they merge by Friday. After that we will need to go through the FFE process and there is no guarantee we can land them. Feel free to ping us on IRC if you need code review. [1] http://specs.openstack.org/openstack/oslo-specs/specs/policy/feature-freeze… -- Daniel Bengtsson Software Engineer

3 2