- openstack-discuss - lists.openstack.org

[cinder][glance][nova][telemetry][monasca][oslo][vmware] Can we deprecate(and remove) VMWare support ?
by Takashi Kajinami 07 Mar '24

07 Mar '24

Hi all, As you might know, some of the OpenStack projects currently support usage of VMWare component. However recently the VMware virt driver in nova was marked experimental in 2023.2 release [1] and it has been discussed that the driver will be removed in 2023.2 release[2], after deprecation is backported to 2023.1. (Please someone from nova team correct me if I'm wrong) So my current question is; Does it make sense to deprecate all of the features to support VMWare component ? My understanding is that these features were added to be used along with VMWare virt driver in nova, but once the virt driver is removed this use case is voided. I'll list up the features within the discussion scope below. nova: VMWare virt driver (this is already experimental by [1]) cinder: VMware Storage Driver (vmdk) glance: VMWare Datastore (I proposed deprecating this in [3][4]) ceilometer: VMWare virt driver (this was deprecated by [5]) os-brick: VmdkConnector monasca-agent: vcenter collector (*1) oslo.vmware: the whole project NOTE: These features are found based on dependency on oslo.vmware but there can be a few not listed here. Outside of OpenStack's governance, there are two projects dependent on oslo.vmware, networking-vsphere and vmware-nsx but both of these look inactive. Because of SLURP, we have to complete deprecation during in 2024.1 release so that we can drop the feature right after 2024.1. If we fail then we have to maintain these features until 2025.1 (the features already deprecated can be removed earlier, though). So I'd like to get feedback and decision before deadline for 2024.1 Thank you, Takashi (*1) Monasca is now inactive so I doubt anyone would work on this topic before it is retired. [1] https://review.opendev.org/c/openstack/nova/+/863911 [2] https://review.opendev.org/c/openstack/nova/+/897017 [3] https://review.opendev.org/c/openstack/glance_store/+/893696 [4] https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… [5] https://review.opendev.org/c/openstack/ceilometer/+/894540

6 21

[oslo][requirements] RFE for new tooz release
by Takashi Kajinami 07 Mar '24

07 Mar '24

Hello, We have identified a regression[1] in tooz 6.0.0, which is the latest version in 2024.1 u-c. I have identified its cause and prepared the bug fix[2] and the follow up change to fix CI coverage[3]. I'll create 6.0.1 release once both of these two land. I'm sending this email to get early approval to bump tooz version in caracal requirements. The bug is at least known to be blocking kolla, but would affect any deployment which is using redis sentinel as tooz backend. Thank you, Takashi [1] https://bugs.launchpad.net/python-tooz/+bug/2056429 [2] https://review.opendev.org/c/openstack/tooz/+/911648 [3] https://review.opendev.org/c/openstack/tooz/+/911682 [4] https://review.opendev.org/c/openstack/releases/+/911711 -- Takashi Kajinami irc: tkajinam github: https://github.com/kajinamit launchpad: https://launchpad.net/~kajinamit

1 0

RE: openstack-discuss Digest, Vol 65, Issue 27
by Asma Naz Shariq 06 Mar '24

06 Mar '24

Hello team, I am intending to deploy Openstack AIO (zed) release, directly at ubuntu 20.04 BareMetal server. The issue I am facing as below: RUNNING HANDLER [MariaDB : Wait for MariaDB service port liveness] Failed - Retrying : [Localhost]: Wait for MariaDB service port liveness ( 10 retries left) Fatal: [localhost]: FAILED! => {"attempts": 10, "changed": false, "elapsed": 60, "msg": "Timeout when waiting for search string MariaDB in ip address:3306"} I need assistance to resolve this issue, -----Original Message----- From: openstack-discuss-request(a)lists.openstack.org <openstack-discuss-request(a)lists.openstack.org> Sent: Thursday, March 7, 2024 5:12 AM To: openstack-discuss(a)lists.openstack.org Subject: openstack-discuss Digest, Vol 65, Issue 27 Send openstack-discuss mailing list submissions to openstack-discuss(a)lists.openstack.org To subscribe or unsubscribe via email, send a message with subject or body 'help' to openstack-discuss-request(a)lists.openstack.org You can reach the person managing the list at openstack-discuss-owner(a)lists.openstack.org When replying, please edit your Subject line so it is more specific than "Re: Contents of openstack-discuss digest..." Today's Topics: 1. [ansible][aio][glance] Cannot create image, TypeError: Response is undefined (Tang Chai Keong) 2. Devstack (BEDDA Fadhel) 3. Re: [kolla-ansible][2023.2] Manila cephFS NFS ganesha need some clarifications (Goutham Pacha Ravi) 4. Re: Devstack (Alvaro Soto) ---------------------------------------------------------------------- Message: 1 Date: Thu, 7 Mar 2024 06:40:20 +0800 From: Tang Chai Keong <tchaikeong(a)gmail.com> Subject: [ansible][aio][glance] Cannot create image, TypeError: Response is undefined To: openstack-discuss(a)lists.openstack.org Message-ID: <CADnLa1bZ7AAy+FsxggR3up+3XhooNCuJZteTzj3vijXnL_sG9w(a)mail.gmail.com> Content-Type: text/plain; charset="UTF-8" I deployed openstack-ansible AIO and is trying to create a new image but is encountering "TypeError: Response is undefined" and "Error: Unable to create the image". The image creation task is just stuck in the "queued" mode forever after that. I also do not see any of the service logs in the lxc containers under /var/logs/ folder. Appreciate any advice on how I can troubleshoot this. Thank you. Regards, Ben ------------------------------ Message: 2 Date: Wed, 6 Mar 2024 23:48:35 +0100 From: BEDDA Fadhel <fadhel.bedda(a)gmail.com> Subject: Devstack To: openstack-discuss(a)lists.openstack.org Message-ID: <CAE1GhS7rhRi_qZt_vvwViSaHXoFUzkse5V+=hof+NcR7s-cnYg(a)mail.gmail.com> Content-Type: multipart/alternative; boundary="000000000000e690e2061305c23f" 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

1 0

Openstack installation on Virtual Machines: External network issue
by KK CHN 06 Mar '24

06 Mar '24

Hi OpenStackers, I am just beginning with openstack. I am trying kolla-ansible all-in-on installation on a Virtual Machine(on an Ubuntu 22.04 VM hosted by ESXi Server). Deployment success, able to create VMs and networks. Base VM Ubuntu-22.04 ( kolla-ansible all-in-one installation) Network details. [image: image.png] From the base VM, I am able to ping tenant VMs through network namespace from base VM . But from a tenant VM, I can't ping to 10.176.17.61( the base VM address) [image: image.png] I am unable to ping to my base VM IP from my tenant VM, whether my deployment is wrong ? How to check? also how to test internet connectivity from Tenant VM ( all VMs are default cirros VMs). [image: image.png] *Note: Why ovs-vsctl not found on base VM ? Do I need to explicitly install, apt get install openvswitch-switch ?* Kolla-ansible won't install it by default?? (kolla_ansible_venv3) ubuntu@ubuntu-VM:~$ ovs-vsctl show Command 'ovs-vsctl' not found, but can be installed with: sudo apt install openvswitch-switch (kolla_ansible_venv3) ubuntu@ubuntu-VM:~$ If any more details are required other than the following, I can provide. # Include files from /etc/network/interfaces.d: source /etc/network/interfaces.d/* auto lo iface lo inet loopback auto ens224 iface ens224 inet static address 10.220.0.51 netmask 255.255.255.0 gateway 10.220.0.1 dns-nameserver 0.0.0.0 auto ens160 iface ens160 inet static address 10.176.17.61 netmask 255.255.254.0 gateway 10.176.16.1 dns-nameserver 10.176.0.11 auto ens192 iface ens192 inet manual up ip link set dev ens192 up down ip link set dev ens192 down globals.yml (kolla_ansible_venv3) ubuntu@ubuntu-VM:~$ grep ^[^#] /etc/kolla/globals.yml --- workaround_ansible_issue_8743: yes config_strategy: "COPY_ALWAYS" kolla_base_distro: "ubuntu" openstack_release: "2023.1" kolla_internal_vip_address: "10.220.0.24" kolla_external_vip_address: "{{ kolla_internal_vip_address }}" kolla_container_engine: docker network_interface: "ens224" neutron_external_interface: "ens192" neutron_plugin_agent: "openvswitch" nova_compute_virt_type: "qemu" (kolla_ansible_venv3) ubuntu@ubuntu-VM:~$ BUT why brctl shows nothing enabled state as "no" (kolla_ansible_venv3) ubuntu@ubuntu-VM:~$ brctl show bridge name bridge id STP enabled interfaces qbr1f4a7fde-87 8000.525b9c0d0f71 no qvb1f4a7fde-87 tap1f4a7fde-87 qbr6800c928-bb 8000.82aaa756a3cc no qvb6800c928-bb tap6800c928-bb qbr83937c49-06 8000.16da67140926 no qvb83937c49-06 tap83937c49-06 qbr9304eb11-59 8000.fa7e2e6ca3e3 no qvb9304eb11-59 tap9304eb11-59 (kolla_ansible_venv3) ubuntu@ubuntu-VM:~$ +--------------------------------------+-----------------------------------------------+ (kolla_ansible_venv3) ubuntu@ubuntu-VM:~$ nova list nova CLI is deprecated and will be a removed in a future release +--------------------------------------+--------------+--------+------------+-------------+--------------------+ | ID | Name | Status | Task State | Power State | Networks | +--------------------------------------+--------------+--------+------------+-------------+--------------------+ | d402d554-a56e-4cc6-af06-694ea913c939 | greenboxes-1 | ACTIVE | - | Running | GREEN=10.10.10.177 | | a69e4c16-e02f-4b5c-b6b1-e929ec309495 | greenboxes-2 | ACTIVE | - | Running | GREEN=10.10.10.6 | | 6b4d4b5d-2cc6-463d-89d9-5180f16ec3e3 | redboxes-1 | ACTIVE | - | Running | RED=20.20.20.104 | | a29576e8-46ca-4311-93ad-f2ca540a9880 | redboxes-2 | ACTIVE | - | Running | RED=20.20.20.121 | +--------------------------------------+--------------+--------+------------+-------------+--------------------+ (kolla_ansible_venv3) ubuntu@ubuntu-VM:~$ neutron port-list -c id -c fixed_ips neutron CLI is deprecated and will be removed in the Z cycle. Use openstack CLI instead. +--------------------------------------+------------------------------------------------------ (kolla_ansible_venv3) ubuntu@ubuntu-VM:~$ neutron port-list -c id -c fixed_ips neutron CLI is deprecated and will be removed in the Z cycle. Use openstack CLI instead. +--------------------------------------+-------------------------------------------------------------------------------------+ | id | fixed_ips | +--------------------------------------+-------------------------------------------------------------------------------------+ | 02344545-8003-4f0c-bc58-b0812d400939 | {"subnet_id": "754de697-6cdb-4277-9d87-0b3fbabb9744", "ip_address": "20.20.20.2"} | | 1f4a7fde-87dc-4547-9ea2-cd0084cd68ff | {"subnet_id": "754de697-6cdb-4277-9d87-0b3fbabb9744", "ip_address": "20.20.20.104"} | | 6800c928-bbac-4c9f-9db0-5d6126a4f46f | {"subnet_id": "b3f4fb8c-a926-4fc0-a9b5-28d7c2ac649b", "ip_address": "10.10.10.177"} | | 83937c49-06a0-4fc6-b34c-76a627989fb2 | {"subnet_id": "b3f4fb8c-a926-4fc0-a9b5-28d7c2ac649b", "ip_address": "10.10.10.6"} | | 9304eb11-5970-4197-b589-2c04a158fad9 | {"subnet_id": "754de697-6cdb-4277-9d87-0b3fbabb9744", "ip_address": "20.20.20.121"} | | 9fcaebab-36a7-401e-97dc-06755b20e817 | {"subnet_id": "b3f4fb8c-a926-4fc0-a9b5-28d7c2ac649b", "ip_address": "10.10.10.2"} | +--------------------------------------+------------------------------------------------------------------------------- (kolla_ansible_venv3) ubuntu@ubuntu-VM:~$ openstack network list +--------------------------------------+-------+--------------------------------------+ | ID | Name | Subnets | +--------------------------------------+-------+--------------------------------------+ | 20374e5f-6639-4e90-8241-2c3ddec72684 | RED | 754de697-6cdb-4277-9d87-0b3fbabb9744 | | 35fe9fe1-05d1-42ea-a3cb-e8f7588ca571 | EXT1 | c35e54e2-4ff5-4775-ab4e-21b24074745b | | 515ec17a-16fa-4be2-ae5f-afc4af388c3d | GREEN | b3f4fb8c-a926-4fc0-a9b5-28d7c2ac649b | +--------------------------------------+-------+--------------------------------------+ (kolla_ansible_venv3) ubuntu@ubuntu-VM:~$ Thank you, Krish

1 0

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

06 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 06 Mar '24

06 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 06 Mar '24

06 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 06 Mar '24

06 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 06 Mar '24

06 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

Barbican/Heat Xena: strange error with barbican-manage (and heat-manage)
by Michel Jouvin 06 Mar '24

06 Mar '24

Hi, I'm trying to update our Wallaby cloud to Xena. Doing this for Barbican and Heat, I have a problem when trying to upgrade the database. Here is the log for Barbican: ---------- [root@os-77023 ~]# barbican-manage db upgrade head [root@os-77023 ~]# barbican-manage db current ERROR: 'int' object is not iterable [root@os-77023 ~]# barbican-manage db upgrade ERROR: 'int' object is not iterable ---------- I can find a similar error in log files of Heat services, for example in heat-engine.log: --------- 2024-03-05 12:16:27.978 1638283 INFO heat.engine.worker [-] Starting engine_worker (1.4) in engine 686dc841-d595-49cd-bf5e-04a4de876dc1. 2024-03-05 12:16:28.109 1638283 ERROR oslo_service.service [req-b991252a-f4c1-4955-a2ed-b20db59a161c - - - - -] Error starting thread.: TypeError: 'int' object is not iterable --------- My DB connection information, working well with Wallaby, is: ---------- sql_connection=mysql+pymysql://barbican:very_secret_pwd@os-sql-admin.lal.in2p3.fr/barbican ---------- I cannot find any other useful information. Anything trivial I missed? Thanks in advance for any help. Best regards, Michel

1 2

[Watcher] How use Watcher to scheduler Openstack resource without cpu_usage
by Nguyễn Hữu Khôi 06 Mar '24

06 Mar '24

Hello guys. I want to use watcher to scheduler openstack resources but some openstack versions are missing cpu_usage metric. How do we use Watcher without it? Thank you. Nguyen Huu Khoi

3 5

[largescale-sig] Next meeting: March 6, 9utc
by Thierry Carrez 06 Mar '24

06 Mar '24

Hi everyone, The Large Scale SIG will be meeting this Wednesday in #openstack-operators on OFTC IRC, at 9UTC, our EU+APAC time. You can doublecheck how that UTC time translates locally at: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20240306T09 Feel free to add topics to the agenda: https://etherpad.opendev.org/p/large-scale-sig-meeting Regards, -- Thierry Carrez

1 1

[tc] [ptg] Tentative schedule
by Jay Faulkner 05 Mar '24

05 Mar '24

I've posted a tentative schedule for the TC vPTG here: https://etherpad.opendev.org/p/apr2024-ptg-os-tc and booked the appropriate times in the PTGBot. I need people to take the following actions: - Existing TC members please review the times for accuracy and confirm their ability to attend. - TC candidates, please review the times for major conflicts and inform me if any of the selected times are hardships. We will finalize the times once the new TC is seated, but I wanted to ensure we had something scheduled. Also, please take time to indicate topics for the TC session here: https://etherpad.opendev.org/p/apr2024-ptg-os-tc. Thanks, Jay Faulkner OpenStack TC Chair

1 0

[tc][murano] Removing Murano from 2024.1 release
by Jay Faulkner 05 Mar '24

05 Mar '24

Hi all, After discussion in the TC meeting today about lots of gathered evidence that Murano is inactive and plagued by serious bugs, I have proposed a resolution to remove Murano from the release. This is roughly equivalent to marking it inactive; however we can only use inactive status to remove things from the release before milestone-2. At this point, the TC is too late discovering the bad state of Murano to use inactivity to prevent its release. Therefore, I have proposed a special-case resolution[0] reflecting general consensus in the TC meeting that Murano should not be released. I wanted to inform the community of this resolution, and advise anyone who may be considering deployment of Murano to be aware of its current inactive state. Additionally, if you believe our evaluation of the situation is wrong, feel free to let your voice be heard in Gerrit. Thanks, Jay Faulkner OpenStack TC Chair 0: https://review.opendev.org/c/openstack/governance/+/910434

1 1

[magnum][stein][kolla-ansible] Cluster creation timeout
by İzzettin Erdem 05 Mar '24

05 Mar '24

Hi everyone, I am currently working on Magnum installed on kolla-ansible stein version. I followed the docs and created clusters using Fedora-Atomic-27-20180419.0.x86_64.qcow2 image according to docs. Now, magnum is creating necessary resources, VMs etc but after some time it is getting timeout at kube_minions&kube_cluster_deploy steps and there are not any information logs about it. I've tried to use different images but I could not succeed. Can you help me, please? Thanks a lot, İzzettin.

3 6

[diskimage-builder] bootable ISO image for baremetal
by Ettore Simone 05 Mar '24

05 Mar '24

Hi! I know it is not one of the most wonderful options for DIB, but in some circumstances I used ISO image in a USB stick for some old and unmaintained hardware. I used to fix by hand every time the "iso" element to complete the task, due to an old reference to a deprecated variable (DIB_IMAGE_ROOT_FS_UUID, now DIB_BOOT_LABEL). I proposed a very small fix and I hope it could be merged in the future: https://review.opendev.org/c/openstack/diskimage-builder/+/905556 Thank you for all your great work. Cheers, Ettore

4 6

[magnum][nova] AZ or Host aggregates not working as expected
by Satish Patel 04 Mar '24

04 Mar '24

2 13

[tc] Next Meeting Tomorrow, March 53332, 1800 UTC
by Jay Faulkner 04 Mar '24

04 Mar '24

Hi all, the next weekly meeting of the OpenStack Technical Committee is tomorrow, March 5, at 1800 UTC. It will be held in a Zoom video conference with minutes kept in #openstack-tc on OFTC. The proposed agenda is: - Roll call - Follow up on tracked action items - Gate health check - Implementation of Unmaintained branch statuses - Testing runtime for 2024.2 release (gmann) - https://review.opendev.org/c/openstack/governance/+/908862 - Murano inactivity and Caracal release - Should https://review.opendev.org/c/openstack/governance/+/908859/ be landed with/without the release removal change? - 2024.1 TC Tracker - https://etherpad.opendev.org/p/tc-2024.1-tracker - Open Discussion and Reviews Thanks, Jay Faulkner OpenStack TC Chair

1 0

OpenDev Removing CentOS 7 Test Nodes from Zuul and Nodepool on March 15
by Clark Boylan 04 Mar '24

04 Mar '24

The OpenDev team has been cleaning up old distro releases from Zuul and Nodepool. Recently, OpenSUSE Leap 15.2 and Debian Buster were removed. Next up on the list is CentOS 7. Unlike Leap and Buster, CentOS 7 is/was used quite a bit more in Zuul configs. According to codesearch [0] these projects are still using CentOS 7 in their master branches: * Swift * OpenStack Ansible * Devstack * Freezer * Solum * Octavia This is likely an incomplete list of OpenStack projects that need cleanup, and I know there are other projects to clean up outside of OpenStack. It would be great if we can clean this up in the near future (and thank you to those of you who have already started). This ensures we don't have another stable branch perpetuating old configs that need cleanup. I have also asked the release team to start communicating cleanups happen early around release time rather than waiting for branch EOL to prevent these configs moving through our releases unnecessarily. Cleanup will also minimize impact when we remove the node type from our CI system on March 15, 2024. The motivation for this cleanup effort is that we've got a number of old distro releases in the CI system that need care and feeding which are either EOL, soon to be EOL, or otherwise unused. Removing these test node types gives us room to add new test node types like the upcoming Ubuntu 24.04 release. We plan to remove Ubuntu Xenial test nodes after CentOS 7 is removed if you want to get a head start on that cleanup too. We understand that this may impact the OpenStack release which is why I'm sending this email. At the same time we want to be in a position where we can have new distro releases ready in a reasonable time frame which necessitates cleanup like this. Please feel free to respond to this thread with any questions or concerns. [0] https://codesearch.opendev.org/?q=centos-7 Clark

1 0

[manila] What's the status of the virtiofs driver?
by Thomas Goirand 04 Mar '24

04 Mar '24

Hi, I've been waiting for this promising feature for a long time already, so I went to check, and saw that in launchpad [1], the blueprint seemed implemented. Though I didn't see anything in Manila's docs about it. So what's the status of this driver? Is it soon ready? Cheers, Thomas Goirand (zigo) [1] https://blueprints.launchpad.net/nova/+spec/libvirt-virtiofs-attach-manila-…

5 5