May 2024 - 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 03 May '24

03 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 03 May '24

03 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 02 May '24

02 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