March 2024 - openstack-discuss - lists.openstack.org

[tacker] FFE request for tacker-horizon's patch and obsoleting Legacy API patch
by Ayumu Ueha (Fujitsu) 07 Mar '24

07 Mar '24

Hi tacker team, As we talked about in today's regular IRC, I would like to request FFE in the 2024.1 Caracal cycle for the following patch: 908983: Support NFV Orchestration API v2.0 | https://review.opendev.org/c/openstack/tacker-horizon/+/908983 910104: Obsolete Legacy APIs excluding VIM feature | https://review.opendev.org/c/openstack/tacker/+/910104 Reasons: [Support NFV Orchestration API v2.0] The tacker-horizon patch provides GUI of NFV Orchestration API V2.0 operations that are very useful to users and developers. This is a major feature addition to tacker-horizon which has not been maintained for a long time, but change is green and now usable. [Obsolete Legacy APIs excluding VIM feature] I could not check Zuul CI pass due to some gate issue that occurred before the Feature freeze and my work was stopped to resolve the issue. The removal of the Legacy API has been declared since the 2023.1 Antelope release, so I would like to merge it if possible in this 2024.1 Caracal cycle. Regards, Ayumu

2 1

[tacker] FFE request for RBAC change for project personas
by Ghanshyam Mann 07 Mar '24

07 Mar '24

Hi Team, I would like to request the Feature freeze exception for the Tacker RBAC work for project personas. - https://review.opendev.org/q/topic:%22bp/implement-project-personas%22+stat… Reason: All the changes are green, including the testing framework/tests for existing RBAC. Finishing the RBAC works for project personas in this cycle will help enable the new defaults and remove the old ones in coming cycles. We are already behind the schedule for RBAC community-wide goal -gmann

2 1

[kolla][cinder][nfs] NFS backend error for volumes
by Satish Patel 07 Mar '24

07 Mar '24

Folks, I am configuring NFS for the cinder backend but somehow it doesn't go well. I am running kolla-ansible with the 2023.1 release. cinder.conf [DEFAULT] enabled_backends = volumes-ssd,volumes-nfs [volumes-nfs] volume_driver = cinder.volume.drivers.nfs.NfsDriver volume_backend_name = volumes-nfs nfs_shares_config = /etc/cinder/nfs_shares nfs_snapshot_support = True nas_secure_file_permissions = False nas_secure_file_operations = False Inside the cinder_volume docker container I can see it mounts NFS automatically and directory permissions is also cinder:cinder also I am able to write on NFS share also so it's not a permission issue also. $ docker exec -it cinder_volume mount | grep nfs 192.168.18.245:/volume1/NFS on /var/lib/cinder/mnt/1ec32c051aa5520a1ff679ce879da332 type nfs (rw,relatime,vers=3,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.18.245,mountvers=3,mountport=892,mountproto=udp,local_lock=none,addr=192.168.18.245) But service is still showing down. | cinder-volume | os-ctrl2@volumes-nfs | nova | enabled | down | 2024-02-28T04:13:11.000000 | In logs I am seeing these 3 lines but then no activity in logs even after restarting the container so that is very strange. 2024-02-28 04:13:12.995 153 ERROR os_brick.remotefs.remotefs [None req-6bcb8eab-6aa6-4c36-9a7a-ed673c39dcbc - - - - - -] Failed to mount 192.168.18.245:/volume1/NFS, reason: mount.nfs: Protocol not supported : oslo_concurrency.processutils.ProcessExecutionError: Unexpected error while running command. 2024-02-28 04:13:13.501 153 WARNING cinder.volume.drivers.nfs [None req-6bcb8eab-6aa6-4c36-9a7a-ed673c39dcbc - - - - - -] The NAS file permissions mode will be 666 (allowing other/world read & write access). This is considered an insecure NAS environment. Please see https://docs.openstack.org/cinder/latest/admin/blockstorage-nfs-backend.html for information on a secure NFS configuration. 2024-02-28 04:13:13.501 153 WARNING cinder.volume.drivers.nfs [None req-6bcb8eab-6aa6-4c36-9a7a-ed673c39dcbc - - - - - -] The NAS file operations will be run as root: allowing root level access at the storage backend. This is considered an insecure NAS environment. Please see https://docs.openstack.org/cinder/latest/admin/blockstorage-nfs-backend.html for information on a secure NAS configuration. Has anyone configured NFS and noticed any behavior?

3 12

[all][elections][tc] TC Election Voting Kickoff
by Tony Breeds 07 Mar '24

07 Mar '24

The poll for the TC Election is now open and will remain open until Mar 20, 2024 23:45 UTC. We are selecting 5 TC members, please rank all candidates in your order of preference. You are eligible to vote if you are a Foundation individual member[1] that also has committed to one of the official project teams' deliverable repositories[2] over the Mar 03, 2023 00:00 UTC - Feb 28, 2024 00:00 UTC timeframe (2023.2 to 2024.1) or if you are one of the extra-acs.[3] If you are eligible to vote in an election, you should find your email with a link to the Condorcet Internet Voting Service (CIVS) page to cast your vote in the inbox of your Gerrit preferred email[4]. What to do if you don't see the email and have a commit in at least one of the official deliverables[2]: * due to a new CIVS policy, to get the email from poll supervisors, you must opt in to email communication opt in with your Gerrit email address at: https://civs1.civs.us/cgi-bin/opt_in.pl * eligible voters who opt in to email communication late can see a pending poll invitation and vote until Mar 20, 2024 23:45 UTC. * check the trash or spam folder of your Gerrit Preferred Email address[4], in case it went into trash or spam * wait a bit and check again, in case your email server is a bit slow * find the sha of at least one commit from an official deliverable repo[2] and email the election officials[1]. If we can confirm that you are entitled to vote, we will add you to the voters list and you will be emailed a ballot. Our democratic process is important to the health of OpenStack, please exercise your right to vote. Candidate statements/platforms can be found linked to Candidate names[6]. Happy voting! Thank you, [1] https://www.openstack.org/community/members/ [2] https://opendev.org/openstack/governance/src/tag/0.16.0/reference/projects.… [3] Look for the extra-acs element in [2] [4] Sign into review.openstack.org: Go to Settings > Contact Information. Look at the email listed as your preferred email. That is where the ballot has been sent. [5] https://governance.openstack.org/election/#election-officials [6] https://governance.openstack.org/election/#tc-candidates Yours Tony.

1 0

Devstack
by BEDDA Fadhel 07 Mar '24

07 Mar '24

Good morning, as part of a test lab, I installed DevStack on Ubuntu. and I want to start linux and windows instances. I created the images and instances. but none that starts. on the console I have: boot from disk and nothing happens Thank you for your help

2 1

[cinder] Feature Freeze Exception Request
by Zong, Yian 06 Mar '24

06 Mar '24

Dear All, I'm requesting a feature freeze exception for Caracal-3 milestone regarding https://review.opendev.org/c/openstack/cinder/+/899795. This change adds cinder active-active support for Dell PowerFlex driver and allows users to configure PowerFlex backends in cinder clustered environment. It's also a customer ask. Please let me know if you have any concern on this FFE. Thank you! BR, Yian Internal Use - Confidential

2 1

[neutron][FFE] OVN routers HA extension support
by Rodolfo Alonso Hernandez 06 Mar '24

06 Mar '24

Hello all: Along with the already implemented and merged feature "Multiple backend support for L3 routers in ML2/OVN" [1], it was needed to implement the HA extension support for the ML2/OVN routers. This is also a long standing technical debt in the L3 side of the ML2/OVN mech driver. The non-OVN routers have a HA flag to define the high availability support; the OVN routers, that are HA by default, do not expose nor accept this API flag. The following patch [2] implements this API extension for the ML2/OVN routers. This patch adds the needed extension to the mechanism driver and adds the "ha" flag to the router resource. Because right now OVN routers are only HA, creating or setting an OVN router to "no-ha" will fail (raising the corresponding exception). This is tested in the patch. The proposal of this FFE was discussed in the Neutron team meeting yesterday [3]. Regards. [1]https://review.opendev.org/q/topic:%22router-flavor-ovn%22 [2]https://review.opendev.org/c/openstack/neutron/+/910889 [3] https://meetings.opendev.org/meetings/networking/2024/networking.2024-03-05…

2 1

[ops][largescale-sig] Looking for large deployments to showcase
by Thierry Carrez 06 Mar '24

06 Mar '24

Hi everyone, You may be familiar with the Large Scale SIG's "Ops Deep Dive" series on OpenInfra Live[1], where our recurring hosts (Arnaud Morin, Mohammed Naser, Felix Hüttner and Belmiro Moreira) discuss with operator guests the details of their large scale OpenStack deployment or a given operational topic. [1] https://openinfra.dev/live/#all-episodes This is a reminder that for this season we want to open things up: if YOU run a large scale deployment that you would like to discuss with our hosts, or if YOU have an idea of an operational challenge that you would like to discuss with your peers (and you have secured their interest in joining), please submit your idea to https://ideas.openinfra.live and we'll consider it during our next Large Scale SIG meeting ! Hoping to see you next on the Ops Deep Dive ! -- Thierry Carrez (ttx)

1 0

Openstack ansible
by Gk Gk 06 Mar '24

06 Mar '24

Hi, When I checked all the host variables for repo containers, I see two entries for 'haproxy_ssl' as shown below: -- "haproxy_port": 8181, "haproxy_service_enabled": true, "haproxy_service_name": "repo_all", "haproxy_ssl": false }, "haproxy_ssl": true, "haproxy_ssl_all_vips": false, "haproxy_ssl_bind_options": "no-tlsv11 no-tlsv10 no-sslv3", "haproxy_stats_bind_address": "0.0.0.0", -- So, does the haproxy frontend for repo service use ssl or not ? Why there are two entries here for the repo containers ?

1 0

[keystone] weekly meeting canceled for 06-March-2024
by Dave Wilde 06 Mar '24

06 Mar '24

Hello, Apologies for the late notice but I need to cancel the weekly meeting today due to a conflict in my schedule. Please reach out to me on list or on IRC if you need anything. Thanks! /Dave

1 0