- openstack-discuss - lists.openstack.org

Help with neutron openstack
by Lohit S 06 May '24

06 May '24

Hi team, I am new to OpenStack. I would like to contribute to the OpenStack Neutron project. However, when I read the OpenStack contribution documentation, I find it difficult to begin. Could anyone please help me get started? I have doubts about how to set up a development environment and if there are any places other than chat available for discussion. Thanks, Lohit S [image: Mailsuite] Sent with Mailsuite · Unsubscribe <https://mailtrack.io/en/privacy/opt-out/unsubscribe/4594fa86f0682220cd357ab…> 05/04/24, 07:00:00 PM

2 2

[kolla][OpenstackAnsible] 2024.1 Caracal cycle-trailing release deadline
by Elõd Illés 06 May '24

06 May '24

Hello teams with trailing projects, The 2024.1 Caracal cycle-trailing release deadline is in 1 month [1], and all projects following the cycle-trailing release model must release their 2024.1 Caracal deliverables by June 6th, 2024. The following trailing projects haven't been released yet for 2024.1 Caracal. OSA team's deliverables: - openstack-ansible-roles - openstack-ansible Kolla team's deliverables: - kayobe - kolla - kolla-ansible - ansible-collection-kolla This is just a friendly reminder to allow you to release these projects in time. Do not hesitate to ping us if you have any questions or concerns. [1] https://releases.openstack.org/dalmatian/schedule.html#d-cycle-trail Thanks, Előd irc: elodilles @ #openstack-release

1 0

[tc][all] OpenStack Technical Committee Weekly Summary and Meeting Agenda
by Goutham Pacha Ravi 06 May '24

06 May '24

Hello Stackers, Next week marks Milestone-1 of the 2024.2 (Dalmatian) release cycle [1]. So as we march on, there have been a number of governance changes that I'd like to brief you about: - The Freezer team now opted to have a distributed project leadership - Thank you for stepping up, noonedeadpunk and khyr0n! - The TC appointed a PTL for the Skyline project - Thank you for stepping up, wu_wenxiang! - The TC has decided that projects can be identified as inactive at any point during a release cycle. When this happens, we would prevent releases for the cycle from such projects. - The "openstack-helm" team has spun up a new repository: "openstack/openstack-helm-plugin," and the "openstack-ansible" team has introduced "openstack/ansible-role-frrouting." === Weekly Meeting === Last week's TC meeting was held on IRC on April 30th, 2024. The meeting was logged to eavesdrop [2]. For the past few release cycles, the OpenStack Technical Committee has been hosting a video meeting call as the first weekly meeting in each month. Last week, we discussed the platform we have been using for these video meetings. Some members expressed concerns about the recording capabilities of Jitsi/Meetpad [3] versus Zoom, while others were open to trying MeetPad again. Ultimately, it was agreed to stick with Zoom for the next meeting. When we host these meetings, we do have a simultaneous IRC conversation - i.e., every discussion is reflected on IRC for those who cannot or do not want to participate in the video meeting. We also upload the recording of the video meeting to the OpenStack TC's YouTube channel [4] for the sake of transparency and for posterity. I'm interested to know what the community thinks about this activity in the TC. Any feedback is most welcome! The discussion then moved to the TC Activities Tracker [5], where gate stability and Python 3.12 compatibility were among the topics discussed. Concerns were raised about the lack of volunteers to make DevStack run on Ubuntu 24.04, and it was noted that some projects still have issues with Python 3.12 compatibility [6]. Project teams must prioritize addressing Python 3.12 compatibility issues before the "E" (2025.1) release cycle - the sooner, the better. If you'd like to contribute your time and effort to testing DevStack with Ubuntu 24.04, please let us know, either here or on OFTC's #openstack-qa channel. This issue was also discussed at the Infra meeting [7]. During the open discussion, the topic of cleanup in global-requirements.txt was raised, particularly regarding the removal of old constraints (excludes) [8] causing issues in some projects. Patches were pushed to address these issues [8]. However, there were concerns that we were losing documentation of known bad versions of these requirements. The effort to fix this up quickly snowballed, and the requirements cleanup has now been reverted [9]. Project teams are encouraged to actively vet their requirements files and raise the minimum versions periodically. Tomorrow's meeting is our monthly Video+IRC meeting, and the call details and agenda are at [10]. We look forward to seeing you there. You're welcome to add new agenda items to weekly meetings. === Goal Proposals === I'd like to request a community review of the following OpenStack community goals and updates: - Migrate eventlet usages to asyncio (https://review.opendev.org/c/openstack/governance/+/902585) - Add timeline to remove enforce_scope in RBAC goal (https://review.opendev.org/c/openstack/governance/+/915179) === Governance Proposals === Merged: Transition Freezer project to DPL | https://review.opendev.org/c/openstack/governance/+/914911 Add frrouting route under OpenStack-Ansible governance | https://review.opendev.org/c/openstack/governance/+/910019 Appoint Wenxiang Wu as PTL of Skyline | https://review.opendev.org/c/openstack/governance/+/915108 Add openstack-helm-plugin git repository | https://review.opendev.org/c/openstack/governance/+/916009 Clarify the timeline for project to move to Inactive state | https://review.opendev.org/c/openstack/governance/+/908880 Move distributed-project-leadership model into doc | https://review.opendev.org/c/openstack/governance/+/916822 Abandoned: Add the Woodpecker charm to OpenStack charms | https://review.opendev.org/c/openstack/governance/+/869752 (Reason: stale) Add Cinder Huawei charm | https://review.opendev.org/c/openstack/governance/+/867588 (Reason: stale) Move docs tools into TC governance | https://review.opendev.org/c/openstack/governance/+/914950 (Reason: disagreement) Appoint Jens Harbott as Skyline PTL | https://review.opendev.org/c/openstack/governance/+/914248 (Reason: withdrawal) The following governance proposals are actively being discussed, so please share your view! - Add option to move leaderless project to Inactive status | https://review.opendev.org/c/openstack/governance/+/914726 - Add DPL model & liaison reset policy | https://review.opendev.org/c/openstack/governance/+/916833 - Update to include docs and miscellaneous repos for AC status | https://review.opendev.org/c/openstack/governance/+/915021 - Move openstack/kuryr and openstack/kuryr-libnetwork to Zun | https://review.opendev.org/c/openstack/governance/+/917517 - 2023 User Survey TC Question Analysis | https://review.opendev.org/c/openstack/governance/+/900516 The following governance proposals need attention: - Appoint Felipe Reyes as OpenStack Charms PTL | https://review.opendev.org/c/openstack/governance/+/914254 (Needs attention from the author) [1] https://releases.openstack.org/dalmatian/schedule.html [2] https://meetings.opendev.org/meetings/tc/2024/tc.2024-04-30-18.00.log.html [3] https://meetpad.opendev.org [4] https://www.youtube.com/@openstack-tc [5] https://etherpad.opendev.org/p/tc-2024.2-tracker [6] https://zuul.openstack.org/builds?job_name=openstack-tox-py312&skip=0 [7] https://meetings.opendev.org/meetings/infra/2024/infra.2024-04-30-19.00.log… [8] https://review.opendev.org/c/openstack/requirements/+/916006 [9] https://review.opendev.org/c/openstack/requirements/+/917869 [10] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting

1 0

CAD applications on OpenStack
by Arne Wiebalck 05 May '24

05 May '24

Dear all, We're looking into integrating the use case of CAD applications, such as CATIA V5/6 or CATIA 3DEXPERIENCE, into our OpenStack deployment, with the goals of increased resource sharing and to reduce the park of individual workstations we have for this at the moment. If anyone has experience running such applications on top of OpenStack (on individual VMs with GPU access, on bare metal servers with concurrent sessions, maybe even containerised ...) and would like to share what they have done, it'd be great if you got in touch with me. Thanks! Arne -- Arne Wiebalck CERN IT

1 0

[magnum-cluster-api] CREATE_IN_PROGRESS never ending
by pahrialtkj＠gmail.com 04 May '24

04 May '24

Hi all, I created a k8s cluster using magnum-cluster-api in openstack bobcat , I used kind for the capi (kind on top of lxc), magnum has been successfully installed along with the cluster-api, but when I create a k8s cluster it is always in the CREATE_IN_PROGRESS status and never completes, if you look at the loadbalancer and the master/worker server has been successfully provisioned, if in the show cluster it looks: status_reason | CAPI Cluster status: Provisioned: Cluster kube-r6jnx is Provisioned. CAPI OpenstackCluster status reason: And when I check the capi-system capi-controller-manager, it always say : http: TLS handshake error from 10.244.0.1:9005: EOF full log https://sprunge.us/DgnUOE Regards, Pahrial

2 6

[magnum-cluster-api] Is it support octavia loadbalancer with ovn driver ?
by pahrialtkj＠gmail.com 04 May '24

04 May '24

Does magnum-cluster-api support with octavia loadbalancer by using ovn driver ?, previously I used amphora driver

4 5

Current Issues on Neutrons
by Cakra Wirabuana 03 May '24

03 May '24

Hi everyone, I am a master's student in computer science at a university in Indonesia. I am interested in writing a thesis related to OpenStack-Neutron because my background is in the networking field. However, I am still having trouble deciding on the right topic other than security. Can I get information here about what's hot on the Neutron network? Maybe for example in terms of measurements (delay, packet drop, jitter), etc. Thank you, Cakra Wirabuana

3 2

[ironic] [docs] Looking for input on how you use Ironic
by Jay Faulkner 03 May '24

03 May '24

Hey all, Ironic is undergoing a project to evaluate our docs with the idea of improving them as a whole. Dave Welsch is a technical writer who is helping us with this effort. We are sending this email out looking for Ironic operators or deployers who are interested in having a short conversation with Dave (and myself, potentially) about how they use Ironic to help us focus our documentation on common use cases. Something that'd be especially valuable is a conversation with anyone who is new to the community (in any capacity) as to their experience with Ironic's documentation. If you're interested in having a one of those conversations, please reach out to me off-list and I'm happy to coordinate. If you have any general input for Ironic docs, feel free to respond directly on this thread. Thanks, Jay Faulkner

1 0

Magnum error after Antelope upgrade
by Michel Jouvin 03 May '24

03 May '24

Hi, In a cloud where all services have been upgraded from Yoga to Antelope, I tried to upgrade Magnum but after the (successful) upgrade, Magnum reports "keystone client errors" when trying to retrieve the status of existing clusters or to create new ones (deletion of existing ones seem to work). The typical error is: ---- 2024-04-29 11:57:39.733 72464 WARNING magnum.service.periodic [-] Skip pulling data from cluster 2e8d6ee8-01cb-42d4-9b6d-0cf242cd4afa due to error: unexpected keystone clie nt error occurred: Forbidden (HTTP 403): magnum.common.exception.AuthorizationFailure: unexpected keystone client error occurred: Forbidden (HTTP 403) 2024-04-29 11:57:39.733 72464 ERROR magnum.service.periodic Traceback (most recent call last): 2024-04-29 11:57:39.733 72464 ERROR magnum.service.periodic File "/usr/lib/python3.9/site-packages/magnum/common/exception.py", line 57, in wrapped 2024-04-29 11:57:39.733 72464 ERROR magnum.service.periodic return func(*args, **kw) 2024-04-29 11:57:39.733 72464 ERROR magnum.service.periodic File "/usr/lib/python3.9/site-packages/magnum/common/clients.py", line 166, in barbican 2024-04-29 11:57:39.733 72464 ERROR magnum.service.periodic self._barbican = barbicanclient.Client(session=session, 2024-04-29 11:57:39.733 72464 ERROR magnum.service.periodic File "/usr/lib/python3.9/site-packages/barbicanclient/client.py", line 186, in Client 2024-04-29 11:57:39.733 72464 ERROR magnum.service.periodic return client_class(session=session, *args, **kwargs) 2024-04-29 11:57:39.733 72464 ERROR magnum.service.periodic File "/usr/lib/python3.9/site-packages/barbicanclient/v1/client.py", line 47, in __init__ 2024-04-29 11:57:39.733 72464 ERROR magnum.service.periodic normalized_microversion = self._get_max_supported_version( 2024-04-29 11:57:39.733 72464 ERROR magnum.service.periodic File "/usr/lib/python3.9/site-packages/barbicanclient/v1/client.py", line 88, in _get_max_supported_version 2024-04-29 11:57:39.733 72464 ERROR magnum.service.periodic min_ver, max_ver = self._get_min_max_server_supported_microversion( 2024-04-29 11:57:39.733 72464 ERROR magnum.service.periodic File "/usr/lib/python3.9/site-packages/barbicanclient/v1/client.py", line 119, in _get_min_max_server_supporte d_microversion 2024-04-29 11:57:39.733 72464 ERROR magnum.service.periodic return self._get_min_max_version(session, endpoint, '1.1') 2024-04-29 11:57:39.733 72464 ERROR magnum.service.periodic File "/usr/lib/python3.9/site-packages/barbicanclient/v1/client.py", line 125, in _get_min_max_version 2024-04-29 11:57:39.733 72464 ERROR magnum.service.periodic resp = discover.get_version_data( 2024-04-29 11:57:39.733 72464 ERROR magnum.service.periodic File "/usr/lib/python3.9/site-packages/keystoneauth1/discover.py", line 107, in get_version_data 2024-04-29 11:57:39.733 72464 ERROR magnum.service.periodic resp = session.get(url, headers=headers, authenticated=authenticated) 2024-04-29 11:57:39.733 72464 ERROR magnum.service.periodic File "/usr/lib/python3.9/site-packages/keystoneauth1/session.py", line 1141, in get 2024-04-29 11:57:39.733 72464 ERROR magnum.service.periodic return self.request(url, 'GET', **kwargs) 2024-04-29 11:57:39.733 72464 ERROR magnum.service.periodic File "/usr/lib/python3.9/site-packages/keystoneauth1/session.py", line 986, in request 2024-04-29 11:57:39.733 72464 ERROR magnum.service.periodic raise exceptions.from_response(resp, method, url) 2024-04-29 11:57:39.733 72464 ERROR magnum.service.periodic keystoneauth1.exceptions.http.Forbidden: Forbidden (HTTP 403) 2024-04-29 11:57:39.733 72464 ERROR magnum.service.periodic --- Did I miss something in the upgrade procedure? Thanks in advance for any help. Best regards, Michel

4 9

[Barbican] Query on "barbican-manage hsm" command
by rajiv mucheli 02 May '24

02 May '24

Hi, Currently, my setup involves utilizing OpenStack Barbican on the Bobcat release, with the Thales HSM A790 serving as the PKCS11 backend for multi-tenancy purposes. In this configuration, each project has the flexibility to select its preferred backend, allowing for a mix of PKCS11 and simpler cryptographic methods across projects. I'm particularly interested in exploring the possibility of dedicating an HMAC/MKEK key specifically for a project, utilizing the PKCS11 backend. This approach would involve assigning a unique key pair to each project, thereby enabling the creation of a segregated partition within the HSM for enhanced security and management. By establishing dedicated keys per project, I aim to optimize security measures and streamline the management of cryptographic resources within the environment. Your insights on the feasibility and implications of this approach would be greatly appreciated. Looking forward to your response. Regards, Rajiv

1 0

Upgrade Bobcat/Caracal and python3-futurist
by Francesco Di Nucci 02 May '24

02 May '24

Hi all, I'm upgrading from Bobcat to Caracal using RDO repositories. I noticed that the package python3-futurist.noarch was present in centos-openstack-bobcat repo, but it is not in openstack-caracal. So it is not possible to update/reinstall/etc. it as it is "orphaned" once the bobcat repository is disabled. Should it be removed? Is it still a dependency? Best regards Francesco Di Nucci

4 6

[Glance] Cancelling Today's Weekly Meeting
by Pranali Deore 02 May '24

02 May '24

Hello, Cancelling today's weekly meeting since most of the team members are not around. See you next week! Thanks, Pranali D.

1 0

overload factor tunning
by pikajorge＠gmail.com 02 May '24

02 May '24

Greetings Folks! My name is Jorge! and currently I'm tunning a policy, in the past due to a lack of hardware the overload factor was set to 320.00% (3.200000) since we are in the process of reducing the number of the replicas (currently 3.56) to three and also When running: swift-ring-builder object-90210.builder dispersion Dispersion is 0.000000, Balance is 234.102882, Overload is 320.00% Required overload is 233.738772% It's suggesting us to decrease the overload factor, nonetheless if a rebalance is run, this value is once again calculated, and it has suggested 1000%, kindly I'd like for your assistance to help me understand first, how can I estimate the overload factor, and also considering the number of desired replicas and our capacity, how can I set the overload factor to be optimum? or is this a value that will need to be modified everytime? . Thanks in advance for all your help! Warmest regards Jorge!

1 0

[barbican][requirements] Request to Include Barbican Installation Guide in OpenStack-Helm Documentation
by Renu Rani 01 May '24

01 May '24

Hi dear colleagues, We are presently in the process of enhancing the official OpenStack-Helm documentation by including a procedural guide for deploying Tacker using helmchart. Through discussions with members of the openstack-helm community, it has been emphasized that Barbican is an indispensable component for Tacker. Hence, it would be highly beneficial for users to have comprehensive instructions for installing Barbican with helmchart included in the official OpenStack-Helm documentation [1]. Consequently, we suggest that the Barbican community integrate the installation guide for the Barbican component into the official OpenStack-Helm documentation. This addition is poised to significantly enhance the clarity and accessibility of deployment procedures for users. We eagerly welcome your opinions and feedback on this proposal, as we aim to ensure that the documentation for openstack deployment with helmchart meets the needs of our community. [1] Deploy OpenStack - openstack-helm 0.1.1.dev4172 documentation<https://docs.openstack.org/openstack-helm/latest/install/deploy_openstack.h…> Best Regards, Renu Rani The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any liability on the originator or NEC Corporation India Private Limited or its affiliates. Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of NEC Corporation India Private Limited or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately.

2 1

[dev][requirements] Potentially ceasing development of Paste
by Jeremy Stanley 01 May '24

01 May '24

Just a heads up that Chris is raising concerns about continued maintenance of the Paste library, which more than a few of our projects rely on: https://github.com/cdent/paste/discussions/91 It's worth considering whether we would offer to adopt/fork it or if there are straightforward migration paths to actively maintained alternatives. -- Jeremy Stanley

3 3

[cinder] this week's meeting canceled
by Jon Bernard 01 May '24

01 May '24

Hello all, we will cancel tomorrow's regularly scheduled meeting in honor of International Workers' Day. See you all next week. -- Jon

1 0

Upgrade Bobcat/Caracal and python3-futurist
by Francesco Di Nucci 30 Apr '24

30 Apr '24

Hi all, I'm upgrading from Bobcat to Caracal using RDO repositories. I noticed that the package python3-futurist.noarch was present in centos-openstack-bobcat repo, but it is not in openstack-caracal. So it is not possible to update/reinstall/etc. it as it is "orphaned" once the bobcat repository is disabled. Should it be removed? Is it still a dependency? Best regards Francesco Di Nucci

1 0

[Octavia] next weekly meetings cancelled
by Gregory Thiemonge 30 Apr '24

30 Apr '24

Hi Folks, I'll be on Holiday for the 2 next weekly meetings (May 1st and 8th), so I'm cancelling them. The next meeting will be May 15th. For any topics (requesting reviews, questions, etc..) we're still reachable on IRC. Thanks Greg

1 0

Nova Antelope / RHEL9 : failure to lauch VM because video model virtio is not supported
by Michel Jouvin 30 Apr '24

30 Apr '24

Hi, After upgrading a compute server from Yoga/EL8 to Antelope/EL9, I cannot start VM on it. nova-compute log says: ---- Failed to build and run instance: libvirt.libvirtError: unsupported configuration: domain configuration does not support video model 'virtio' ---- According to https://bugs.launchpad.net/nova/+bug/2018172, it seems the problem also existed when trying to deploy nova-compute Yoga/Zed on EL9 but what fixed the problem is not clear in the issue... Any idea about what could cause this problem and how to fix it? Best regards, Michel

2 2

[Horizon][Skyline][API] Recommendation for a Web Application Firewall in front of Services
by Kaster, Jörn 30 Apr '24

30 Apr '24

Hello together, are there any recommendations or best practices how to expose the openstack API and/or WebUI's over a WAF (web application firewall) to the internet? We think we would use VMware NSX ALB [1] for this, but with the current broadcom trouble in the VMware sphere, we are uncertain for the future with this product. Are there any alternative software tools to reach the waf functionality to secure the api and http path's to openstack? regards Jörn [1]https://docs.vmware.com/en/VMware-NSX-Advanced-Load-Balancer/index.html [https://docs-prod.vmware.com/en/VMware-NSX-Advanced-Load-Balancer/images/GU…]<https://docs.vmware.com/en/VMware-NSX-Advanced-Load-Balancer/index.html> VMware NSX Advanced Load Balancer Documentation<https://docs.vmware.com/en/VMware-NSX-Advanced-Load-Balancer/index.html> Welcome to the VMware NSX Advanced Load Balancer (formerly known as Avi Networks). The NSX Advanced Load Balancer makes it easy to apply load balancing, web application firewall, and container ingress to any application in any datacenter and cloud. docs.vmware.com

1 0

[neutron] neutron-dynamic-routing advertising IPv4 AND IPv6 routes for true MP-BGP OR running multiple BGP speakers per agent (host)?
by Christian Rohmann 30 Apr '24

30 Apr '24

Hello OpenStack-Discuss, when setting up Neutron Dynamic Routing [1] to advertise IPV4 floating IPs and also IPv6 tenant networks I ran into some questions / issues. I was just about to ask about them here on the ML, when I found the older thread [2] discussing the advertising of IPv6 routes (e.g. from tenant networks). There Sean mentioned [4] that even with MP-BGP support [3] it's required to have two BGP speakers. While [3] means IPv4 or IPv6 can be used to establish the BGP session itself to then advertise routes for either address family, it's not possible to advertise IPv4 AND IPv6 routes via the same session. To cut to the chase of this threat .... It's not uncommon to simply use individual (non Multi-Protocol) BGP sessions to exchange routes for IPv4 and IPv6 individually and to me this poses no issue to me. The problem with Neutron is though, that the os_ken dragent driver only supports one BGP speaker [5] per agent. This leads to only one of the BGP speakers (IPv4 or IPv6) running per individual (control plane, networking) host. Or am I not seeing something or am misreading the capabilities of the components involved? If not, I see two options for improvement here: 1) Enabling a BGP speaker to have more than one address family (dragent driver already has MP-BGP support via [3]), so the query fetching the routes [6] simply returns them both. 2) Somehow get more than one BGP speaker per dragent working by ... a) ... extending the driver to host more than one BGP speaker b) ... extending dragent to have more than one driver instance Would love to hear how others have set up their dynamic routing and what your ideas are! Regards Christian [1] https://github.com/openstack/neutron-dynamic-routing [2] https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… [3] https://review.opendev.org/c/openstack/neutron-dynamic-routing/+/608302 [4] https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… [5] https://github.com/openstack/neutron-dynamic-routing/blob/ffaaf5a25d846fead… [6] https://github.com/openstack/neutron-dynamic-routing/blob/ffaaf5a25d846fead…

3 4

[tc][all] OpenStack Technical Committee weekly summary and meeting agenda
by Goutham Pacha Ravi 30 Apr '24

30 Apr '24

Hello Stackers, We're slowly approaching Milestone-1 of the 2024.2 (Dalmatian) release cycle [1]. As you observe, there is a buzz of activity across all OpenStack repositories as we've just gotten out of our design and planning event. I hope you've been enjoying the PTG summaries that have been posted thus far; I would especially recommend reading through the summary JayF put up for the Technical Committee meetings [2]. Allow me to take you through the latest news from the Technical Committee: === Weekly Meeting === Last week's TC meeting was held on IRC on Apr 23rd, 2024. The meeting was logged to eavesdrop [3]. Our main topic of discussion was about the fate of unmaintained branches, and the discussion was timely given that Elod Iles from the OpenStack Release Management SIG brought a discussion to this list about transitioning the "stable/zed" branch of all release-cycle deliverables to "unmaintained/zed" [5]. This process is underway [6]. Concerns were expressed that the unmaintained process may be easy for teams to opt in, and the burden on the "unmaintained-core" team is growing with each branch. Project Teams are expected to actively assist in transitioning branches to end-of-life. Since this isn't happening, and since the TC has noted that a number of projects have CI (Zuul) configuration errors on these "unmaintained" branches, it was proposed that we be aggressive about proposing end-of-life for unmaintained branches. It was also argued that our release model is going too fast for real-world deployments to catch up, and transitioning a lot of branches simultaneously to EOL may impact many consumers. In the interest of time during the meeting, we decided not to interfere with the transition of stable/zed to "unmaintained/zed". We encourage project leaders to: - Get their CI configuration in order for any unmaintained branches - If there is no interest/time to maintain any unmaintained branch, please actively pursue the branch's EOL process [7] In the rest of the meeting, we went through open governance proposals. We have been distracted by the PTG and Action Items across OpenStack, so some of these proposals are lacking review attention. We'll be focusing on getting these adequate review attention in the coming week/s. The next TC meeting is today, Apr 30th, 2024, at 1800 UTC on OFTC's #openstack-tc channel [4]. The agenda feels light, but we'll try to address a number of TC trackers at this meeting. This meeting is enhanced by the community's participation. We'd especially invite project leaders (PTLs, DPLs, Core maintainers) to participate and propose topics. === Goal Proposals === I'd like to request a community review of the following OpenStack community goals and updates: - Migrate eventlet usages to asyncio (https://review.opendev.org/c/openstack/governance/+/902585) - Goal: Remove eventlet requirements from shared libraries (https://review.opendev.org/c/openstack/governance/+/916546) - Add timeline to remove enforce_scope in RBAC goal (https://review.opendev.org/c/openstack/governance/+/915179) === Governance Proposals === The following governance proposals are close to being merged: - Add option to move leaderless project to Inactive status (https://review.opendev.org/c/openstack/governance/+/914726) - Appoint Wenxiang Wu as PTL of Skyline | (https://review.opendev.org/c/openstack/governance/+/915108) - Transition Freezer project to DPL | (https://review.opendev.org/c/openstack/governance/+/914911) The following governance proposals are actively being discussed: - Add DPL model & liaison reset policy (https://review.opendev.org/c/openstack/governance/+/916833) - Update to include docs and miscellaneous repos for AC status (https://review.opendev.org/c/openstack/governance/+/915021) - Clarify the timeline for a project to move to Inactive state (https://review.opendev.org/c/openstack/governance/+/908880) The following governance proposals need some review attention: - Move openstack/kuryr and openstack/kuryr-libnetwork to Zun (https://review.opendev.org/c/openstack/governance/+/917517) - 2023 User Survey TC Question Analysis (https://review.opendev.org/c/openstack/governance/+/900516) And finally, please consider volunteering as an Election official for the next OpenStack elections! [8] Thank you very much for reading! On behalf of the OpenStack TC, Goutham Pacha Ravi (gouthamr) OpenStack TC Chair [1] https://releases.openstack.org/dalmatian/schedule.html [2] https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… [3] https://meetings.opendev.org/meetings/tc/2024/tc.2024-04-23-18.00.log.html [4] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting [5] https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… [6] https://review.opendev.org/q/topic:zed-unmaintained [7] https://governance.openstack.org/tc/resolutions/20230724-unmaintained-branc… [8] https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack…

1 0

[all][oslo] Removing Python 3.8 support
by Takashi Kajinami 30 Apr '24

30 Apr '24

Hello, I'm sending this to remind you of the fact that Python 3.8 support will no longer be part of the tested python versions for 2024.2 . Based on the plan, I'll drop Python 3.8 support from all oslo libraries and update the minimum python version from 3.8 to 3.9, in the final release of oslo deliverables. Please make sure that none of the master jobs are dependent on Python 3.8 . We faced some problems when we first attempted to remove python 3.8 support early and the removal was eventually reverted because of remaining usage of Focal and remaining lifecycle of Python 3.8. However now Python 3.8 is actually reaching its EOL, we may no longer attempt the same revert. https://governance.openstack.org/tc/reference/runtimes/2024.2.html Thank you, Takashi Kajinami -- Takashi Kajinami irc: tkajinam github: https://github.com/kajinamit launchpad: https://launchpad.net/~kajinamit

1 0

[tc][election] A call for election officials for 2024.2
by Goutham Pacha Ravi 30 Apr '24

30 Apr '24

Hello Stackers, I'd like to express my gratitude to Ian Y Choi and Tony Breeds for their service as OpenStack's election officials for the 2024.1 term. A hallmark of our community has been its leadership and the guiding principles [1] we use when defining them. In Aug-Sep 2024, we're going to be electing the next set of OpenStack Project Team Leads as well as 4 members of the OpenStack Technical Committee. We've run a combined election for PTLs and TC seats in the past few years. We envision doing the same for this upcoming election. Most of the election process is automated, and election officials help execute and oversee this process [2]. If you're interested in being an election official, please reach out to me. If you've previously served as an election official, please do not hesitate to reach out. If we have enough volunteers, you may do us a great favor by mentoring those doing this for the first time. Thank you, Goutham Pacha Ravi (gouthamr) OpenStack TC Chair [1] https://governance.openstack.org/tc/reference/principles.html [2] https://governance.openstack.org/election/process.html

1 0

Re: [magnum][magnum-capi][cinder] Override csi plugin to override availability zone for cinder
by Satish Patel 30 Apr '24

30 Apr '24

Thanks for the quick response. I would like to have this in the MCAPI driver so we have more control on variables by labels. Because each deployment is different. I have created issue here: https://github.com/vexxhost/magnum-cluster-api/issues/366 On Mon, Apr 29, 2024 at 5:26 PM Mohammed Naser <mnaser(a)vexxhost.com> wrote: > Hi Satish, > > > Replies inline, as I’m trying to “decompose” this. 😊 > > > > *From: *Satish Patel <satish.txt(a)gmail.com> > *Date: *Monday, April 29, 2024 at 5:13 PM > *To: *OpenStack Discuss <openstack-discuss(a)lists.openstack.org> > *Subject: *[magnum][magnum-capi][cinder] Override csi plugin to override > availability zone for cinder > > Folks, > > > > I have deployed a magnum with magnum-capi driver. Now trying to work with > a cinder for PV stuff and found some strange issue related to the > Availability Zone. > > > > My k8s cluster running in AZ: foo > > My Ceph/Cinder running in AZ: nova (default) > > > > I have created k8s cluster using magnum-capi selecting AZ: foo but when I > am trying to create/attach PV then getting an error saying invalid AZ. Ofc > because its in different AZ so I have add following snippet in Storage > class to override AZ of CSI > > > > allowedTopologies: - matchLabelExpressions: - key: > topology.cinder.csi.openstack.org/zone values: - nova > > > > So in this case, you do allow cross az attach inside OpenStack in order to > allow this, is this correct? Since the AZ of your storage != the AZ of > your compute nodes. > > > > PV creation completed successfully after applying the above change. Now > when I try to deploy ngnix and pass that PV then again I get a volume > affinity issue because worker nodes and volume are in different AZ. > > > > I did the following to change CSI plugin az to nova for worker node to > make it fix. > > > > kubectl label nodes kube-acrsf-default-worker-rxmg6-t7wzd > topology.cinder.csi.openstack.org/zone=nova --overwrite > > > > What is the proper workaround here for the above scenario and what would > be the proper way to fix it? > > > > In this case, what you’re doing is telling the node that it is running in > the `nova` AZ (which it is not!) > > > > Does magnum have Cinder CSI AZ label to override availability zone in > magnum template? > > > > > https://github.com/kubernetes/cloud-provider-openstack/blob/master/docs/cin… > > > > I believe in this case, you’ll need to set the ignore-volume-az if I > understand correctly, it seems Magnum does not have a default label for > this. If you want to file an issue to the CAPI driver we can add an option > to enable this and make it ignore it. >

1 0