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

[cinder] Festival of XS reviews (15 March)
by Rajat Dhasmana 15 Mar '24

15 Mar '24

Hello Argonauts, We will be having our monthly festival of reviews this Friday i.e. 15th March (Friday) from 1400-1600 UTC. This will be the last festival for the 2024.1 Caracal cycle. Following are the details: Date: 15th March, 2024 Time: 1400-1600 UTC Meeting link: https://meet.google.com/jqg-eigw-rku etherpad: https://etherpad.opendev.org/p/cinder-festival-of-reviews Thanks Rajat Dhasmana

1 0

[tacker] Patches cannot pass zuul check for RC1
by Yasufumi Ogawa 15 Mar '24

15 Mar '24

Hi team, We still have several patches remained for unexpected failures on zuul check tests. All the failures happen in codes other than we updated and are not always happened. It might be the difficulty we usually meet at the end of releases because of lack of resources on the environment. Unfortunately, it's already over the deadline of RC1 although it can be merged if we have enough time to recheck unitll it's passsed. So, I'd like to fix Tacker's Caracal release and propose to backport the remained patches later. Thank you for your contribution. https://review.opendev.org/c/openstack/tacker/+/908878 https://review.opendev.org/c/openstack/tacker/+/910504 https://review.opendev.org/c/openstack/tacker/+/911639 https://review.opendev.org/c/openstack/tacker/+/907022 https://review.opendev.org/c/openstack/tacker/+/907025 https://review.opendev.org/c/openstack/tacker/+/908752 https://review.opendev.org/c/openstack/tacker/+/907026 https://review.opendev.org/c/openstack/tacker/+/907694 Regards, Yasufumi

1 0

OSSN-0093: Unresolved Vulnerability in OpenStack Murano
by Jeremy Stanley 14 Mar '24

14 Mar '24

OSSN-0093 Unresolved Vulnerability in OpenStack Murano ### Summary ### A severe security vulnerability in all versions of the Murano service will be disclosed at a later date. Murano is an inactive project[*], so no fix is currently under development for this vulnerability. It is strongly recommended that any OpenStack deployments disable or fully remove Murano, if installed, at the earliest opportunity. This security note will be amended at the time of public disclosure to include further details and context, but action should be taken as soon as possible in order to minimize the risk it poses. [*] https://governance.openstack.org/tc/reference/emerging-technology-and-inact… ### Affected Services / Software ### - murano: all versions ### Discussion ### This security note is a redacted placeholder, and will be amended with complete details once the associated bug report becomes public. ### Recommended Actions ### Disable the Murano service in, or fully remove it from, all OpenStack deployments at the earliest opportunity. ### Credits ### Not yet disclosed. ### Contacts / References ### Authors: - Jeremy Stanley, OpenStack Vulnerability Coordinator This OSSN: https://wiki.openstack.org/wiki/OSSN/OSSN-0093 Original bug: https://launchpad.net/bugs/2048114 (not yet public) Mailing List : [security-sig] openstack-discuss(a)lists.openstack.org -- Jeremy Stanley, OpenStack Vulnerability Coordinator

1 1

[requirements][releases][heat][mistral][murano] Requirements freeze exception for yaql
by Takashi Kajinami 14 Mar '24

14 Mar '24

Hello, I have another exception request... A critical security issue[1] was discovered recently and we are updating yaql to fix the issue. The required change was already merged into yaql and I've proposed a new yaql release[2]. I'd like to request a requirement freeze exception to pull the fixed version into upper constraints for 2024.1. Please let me know if you have any concern. Thank you, Takashi [1] https://bugs.launchpad.net/yaql/+bug/2048114 [2] https://review.opendev.org/c/openstack/releases/+/913230 -- Takashi Kajinami irc: tkajinam github: https://github.com/kajinamit launchpad: https://launchpad.net/~kajinamit

3 2

[nova][placement] Zombie placement allocations DB records
by hai wu 14 Mar '24

14 Mar '24

Sometimes there are zombie placement allocations records left for hypervisors, meaning there are no mapping VMs running on those hosts, but the placement allocation records still show up in the database. Does this mean that nova conductor/scheduler would still think those resources have already been allocated, while in reality, there's no existing VMs mapped to those zombie placement allocations records?

3 3

[openstack][octavia] Multi LB Management Networks
by Nguyễn Hữu Khôi 14 Mar '24

14 Mar '24

Hello. Is there any way to configure multi lb mnt network for amphorae instances? I am planning to design multiple AZs with separate networks for my system. I am reading this link: https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/17… Thank you. Nguyen Huu Khoi

2 2

[Zun] Docker in rootless mode
by Francesco Di Nucci 14 Mar '24

14 Mar '24

Hello, I am working on a 2023.2 instance to install Zun. While we're still in the design phase, I was wondering if it is possible to run Docker as a non-root user together with Kata Containers for enhanced security. Has anyone tried this solution? Regards Francesco Di Nucci

2 4

[cloudkitty][ptg] Virtual Dalmatian vPTG Planning
by Rafael Weingärtner 14 Mar '24

14 Mar '24

Hello guys, Here is [1] our etherpad for the Dalmatian/2024.2 virtual PTG. Please, add your topics there if there is anything you would like to discuss/propose. I have already created a basic structure in the etherpad. I already scheduled the room and time slots. If you guys have any other suggestions, please let me know. [1] https://etherpad.opendev.org/p/apr2024-ptg-cloudkitty -- Rafael Weingärtner

1 0

What deployment tools do you use? What do you like in them?
by Ruslanas Gžibovskis 13 Mar '24

13 Mar '24

Hi team, Could you, please, share your opinion and your experience with deployment methods. Also what are the tools you use? I have some deployments running TripleO tool. What I like is that we can deploy on empty servers and customizable OpenStack Installation. Sadly TripleO stopped working on new releases last year. Question: Which deployment method you would recommend which would support deploying on empty servers? My plan is to use CentOS Stream as base OS. My setup: 3x controller and 10+ computes. All with generic things except cinder, I do not have volumes and telemetry. But this year I need to add SR-IOV and some computes with RT kernels. Suggestions? My research: OSP-ansible - looks like it could deploy without containerization (I find it as a benefit). (could someone share sample config you use?) Kolla-ansible - looks like old time here and most used? (could someone share sample config you use?) But all above are deploying on existing OS. Tho I have found the Kayobe, quite new to me, have you tried? How multi-controller and multicompute deployment config looks like? Thank you for your opinion or sharing your experience with the tools you use. -- Ruslanas Gžibovskis +370 6030 7030

3 4

[Cinder] Storage not detected when instance boots from ISO
by Francesco Di Nucci 13 Mar '24

13 Mar '24

Hello, premised that probably I am misunderstanding default behavior, I'm experiencing a weird issue with storage/volumes: * Cinder storage has only a NFS backend, with "cinder.volume.drivers.nfs.NfsDriver" driver * When I launch an instance through Horizon from a QCOW2 cloud image and with an associated volume, everything is ok (instances start, changes to the instance are persistent and remain through reboots etc) * But if I launch an instance from an ISO (CentOS, Debian, Ubuntu - DVD or minimal, seems to be OS-independent) and with an associated volume, I can use the installer through the noVNC console but it does not detect disks. Even if the volume is attached, the OS booted from ISO does not report/find it, and the installation can't proceed Is this normal/default behavior or is something wrong with my install? Best regards Francesco Di Nucci

1 0

Security Group Rules on Octavia Amphorae
by Kees Meijs | Nefos 13 Mar '24

13 Mar '24

Hello list, When creating a new load balancer using Octavia, I noticed the VIP network port gets assigned a dynamic created Security Group. The Security Group does not contain a rule allowing ICMP, therefore the VIP not being "pingable". Other than harder diagnostics, it could pose PMTU issues and such. Is it maybe possible to either just enable ICMP, or maybe template the dynamic Security Groups? Thanks in advance! Cheers, Kees

2 2

[swift] Increase part power on account/container ring
by Thiago De Moraes Teixeira 13 Mar '24

13 Mar '24

Morning, Here we have a cluster with Accounts/Containers ring with part power 8 and our Objects ring with part power 20 (builted later). Now we want to migrate the 'old' Accounts/Containers ring to a new one, with higher part power, like 20. Is there a better way to do this? I'm doing some crazy tests with SAIO and multiples storage nodes, based in build a new ring with part power 20 and just swap the old files (account/container.ring.gz) with the new ones and let the replicators do their jobs, moving *.db files to their new home partition. Until today these tests worked fine, but I don't know how to do it on a large scale, with some terabytes of data. Just wondering about some ways to do that :) And before/after this change, is there any command in swift that i can audit this entire process, ensuring that cluster data remains the same? Thanks! -- _‘Esta mensagem é direcionada apenas para os endereços constantes no cabeçalho inicial. Se você não está listado nos endereços constantes no cabeçalho, pedimos-lhe que desconsidere completamente o conteúdo dessa mensagem e cuja cópia, encaminhamento e/ou execução das ações citadas estão imediatamente anuladas e proibidas’._ * **‘Apesar do Magazine Luiza tomar todas as precauções razoáveis para assegurar que nenhum vírus esteja presente nesse e-mail, a empresa não poderá aceitar a responsabilidade por quaisquer perdas ou danos causados por esse e-mail ou por seus anexos’.*

3 8

[swift] Multi-policy container
by m.victorello＠luizalabs.com 13 Mar '24

13 Mar '24

Hello, Is there any plan to support multi-policy containers? Why the container's database have a 'storage_policy_index' column for objects? As far as I know the policy index comes from the container (broker.get_info). I don't know that much about changing the policy of a container, i think those are related.

2 1

[magnum] ClusterAPI driver out of tree
by Jake Yip 13 Mar '24

13 Mar '24

Hi all, After the previous discussions[1] on the ML, Magnum and StackHPC have decided to create and maintain separate repos[2] for StackHPC's contributed cluster api driver. The repos are currently 1. magnum-capi-helm - driver implementation 2. magnum-capi-helm-charts - helm charts used by driver This will allow the driver to be out of tree, yet still be in governance. StackHPC and Magnum Core team will work together to test the driver in CI. I hope this will please everyone and be a way forward. Regards, Jake [1] https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… [2] https://review.opendev.org/c/openstack/governance/+/910240 [3] https://review.opendev.org/c/openstack/project-config/+/910239 -- Jake Yip Technical Lead, ARDC Nectar Research Cloud

1 0

opensearch dashboards example
by Satish Patel 12 Mar '24

12 Mar '24

Folks, Recently I have deployed opensearch logging for ELK replacement and trying to create some visualization dashboard but its new tool and learning curve. Will appreciate If anyone has any example dashboard or visualizer for logging etc. ~S

1 0

Re: [keystone] application creds issue with permission
by Satish Patel 12 Mar '24

12 Mar '24

Hi Artem, You are 100% correct here, I have noticed as soon as I give the reader the role it works. Thank you! On Tue, Mar 12, 2024 at 4:02 PM Artem Goncharov <artem.goncharov(a)gmail.com> wrote: > Can you please check which roles are bound to the appcred? The reason I am > asking is https://review.opendev.org/c/openstack/keystone/+/910337 (wrong > treatment of implied roles when you create appcred explicitly specifying > role that implies another role (basically if you create appcred with member > role - reader role is not given) > > ---- > typed from mobile, auto-correct typos assumed > ---- > > On Tue, Mar 12, 2024, 20:57 Satish Patel <satish.txt(a)gmail.com> wrote: > >> Folks, >> >> I am running the 2023.1 release of openstack using kolla-ansible. I have >> integrated with LDAP and everything works fine. But today when I created >> application creds and used that to access openstack api I got all kinds of >> strange auth errors. >> >> #!/usr/bin/env bash >> export OS_AUTH_TYPE=v3applicationcredential >> export OS_AUTH_URL=https://openstack-eng.example.com:5000 >> export OS_IDENTITY_API_VERSION=3 >> export OS_REGION_NAME="eng" >> export OS_INTERFACE=public >> export OS_APPLICATION_CREDENTIAL_ID=ee17300916b1401f912f6140ce9cd642 >> export OS_APPLICATION_CREDENTIAL_SECRET=XXXXXXXXX >> >> # openstack server list >> ForbiddenException: 403: Client Error for url: >> https://openstack-eng.example.com:8774/v2.1/servers/detail?deleted=False, >> Policy doesn't allow os_compute_api:servers:detail to be performed. >> >> >> # openstack image list >> ForbiddenException: 403: Client Error for url: >> https://openstack-eng.example.com:9292/v2/images, You are not authorized >> to complete get_images action.<br /><br /> >> >> What is wrong here because I have one more setup of openstack which is >> not using LDAP but in that cloud application creds working fine. >> >> # cat /etc/keystone/keystone.conf >> >> [DEFAULT] >> debug = False >> transport_url = hiding.... >> log_file = /var/log/kolla/keystone/keystone.log >> use_stderr = True >> >> [oslo_middleware] >> enable_proxy_headers_parsing = True >> >> [database] >> connection = mysql+pymysql:// >> keystone:hiding...@openstack-eng.example.com:3306/keystone >> connection_recycle_time = 10 >> max_pool_size = 1 >> max_retries = -1 >> >> [identity] >> domain_specific_drivers_enabled = true >> domain_config_dir = /etc/keystone/domains >> >> [token] >> revoke_by_id = False >> provider = fernet >> expiration = 86400 >> allow_expired_window = 172800 >> >> [fernet_tokens] >> max_active_keys = 3 >> >> [cache] >> backend = oslo_cache.memcache_pool >> enabled = True >> memcache_servers = 10.0.25.201:11211,10.0.25.202:11211,10.0.25.203:11211 >> >> [oslo_messaging_notifications] >> transport_url = rabbit://openstack:hiding.... >> driver = noop >> >> [oslo_messaging_rabbit] >> heartbeat_in_pthread = True >> amqp_durable_queues = true >> rabbit_quorum_queue = true >> kombu_reconnect_delay = 0.5 >> rabbit_transient_queues_ttl = 60 >> >> >> # cat /etc/keystone/domains/keystone.eng.conf >> >> # Ansible managed >> >> [identity] >> driver = ldap >> >> [ldap] >> debug_level = 4095 >> group_allow_create = False >> group_allow_delete = False >> group_allow_update = False >> group_id_attribute = cn >> hiding.... >> hiding.... >> >>

1 0

[keystone] application creds issue with permission
by Satish Patel 12 Mar '24

12 Mar '24

Folks, I am running the 2023.1 release of openstack using kolla-ansible. I have integrated with LDAP and everything works fine. But today when I created application creds and used that to access openstack api I got all kinds of strange auth errors. #!/usr/bin/env bash export OS_AUTH_TYPE=v3applicationcredential export OS_AUTH_URL=https://openstack-eng.example.com:5000 export OS_IDENTITY_API_VERSION=3 export OS_REGION_NAME="eng" export OS_INTERFACE=public export OS_APPLICATION_CREDENTIAL_ID=ee17300916b1401f912f6140ce9cd642 export OS_APPLICATION_CREDENTIAL_SECRET=XXXXXXXXX # openstack server list ForbiddenException: 403: Client Error for url: https://openstack-eng.example.com:8774/v2.1/servers/detail?deleted=False, Policy doesn't allow os_compute_api:servers:detail to be performed. # openstack image list ForbiddenException: 403: Client Error for url: https://openstack-eng.example.com:9292/v2/images, You are not authorized to complete get_images action.<br /><br /> What is wrong here because I have one more setup of openstack which is not using LDAP but in that cloud application creds working fine. # cat /etc/keystone/keystone.conf [DEFAULT] debug = False transport_url = hiding.... log_file = /var/log/kolla/keystone/keystone.log use_stderr = True [oslo_middleware] enable_proxy_headers_parsing = True [database] connection = mysql+pymysql:// keystone:hiding...@openstack-eng.example.com:3306/keystone connection_recycle_time = 10 max_pool_size = 1 max_retries = -1 [identity] domain_specific_drivers_enabled = true domain_config_dir = /etc/keystone/domains [token] revoke_by_id = False provider = fernet expiration = 86400 allow_expired_window = 172800 [fernet_tokens] max_active_keys = 3 [cache] backend = oslo_cache.memcache_pool enabled = True memcache_servers = 10.0.25.201:11211,10.0.25.202:11211,10.0.25.203:11211 [oslo_messaging_notifications] transport_url = rabbit://openstack:hiding.... driver = noop [oslo_messaging_rabbit] heartbeat_in_pthread = True amqp_durable_queues = true rabbit_quorum_queue = true kombu_reconnect_delay = 0.5 rabbit_transient_queues_ttl = 60 # cat /etc/keystone/domains/keystone.eng.conf # Ansible managed [identity] driver = ldap [ldap] debug_level = 4095 group_allow_create = False group_allow_delete = False group_allow_update = False group_id_attribute = cn hiding.... hiding....

1 0

[ansible][aio][glance] Cannot create image, TypeError: Response is undefined
by Tang Chai Keong 12 Mar '24

12 Mar '24

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

2 2

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

11 Mar '24

Hi all, the next weekly meeting of the OpenStack Technical Committee is tomorrow, March 12, at 1800 UTC. It will be held on #openstack-tc in OFTC. *US-based contributors please note that the meeting time does not change with DST.* 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 - TC vPTG 2024.2 / TC Tracker 2024.1 - https://etherpad.opendev.org/p/tc-2024.1-tracker - https://etherpad.opendev.org/p/apr2024-ptg-os-tc - Open Discussion and Reviews Thanks, Jay Faulkner OpenStack TC Chair

1 0

[swift][s3api] put-object-acl in SLO objects
by Thiago De Moraes Teixeira 11 Mar '24

11 Mar '24

Hi, I've got this error when trying to put acl in objects that are a multipart upload with s3api client. *aws s3api put-object-acl --bucket ramac --key darwin --acl public-readAn error occurred (BadDigest) when calling the PutObjectAcl operation (reached max retries: 4): The Content-MD5 you specified did not match what we received.* And for objects greater than 5Gb the error is: *An error occurred (EntityTooLarge) when calling the PutObjectAcl operation: Your proposed upload exceeds the maximum allowed object size.* I noticed this is happening because s3 middleware did not recognize this object as an SLO, so when the request reaches the ServerSideCopyMiddleware, the request did not have the query param "multipart-manifest". I tried this swift patch, to solve this problem, identifying if the object is an SLO, on head object in acl_handlers.py class, and retrieving this information before request transformation to swift_request, adding the query param. While this patch resolves the immediate issue, I believe there's room for improvement. I welcome any suggestions or feedback on enhancing this patch further. Your insights would be greatly appreciated. https://paste.openstack.org/show/bd2nAHIHPtUtDNbWLorD/ Best regards -- _‘Esta mensagem é direcionada apenas para os endereços constantes no cabeçalho inicial. Se você não está listado nos endereços constantes no cabeçalho, pedimos-lhe que desconsidere completamente o conteúdo dessa mensagem e cuja cópia, encaminhamento e/ou execução das ações citadas estão imediatamente anuladas e proibidas’._ * **‘Apesar do Magazine Luiza tomar todas as precauções razoáveis para assegurar que nenhum vírus esteja presente nesse e-mail, a empresa não poderá aceitar a responsabilidade por quaisquer perdas ou danos causados por esse e-mail ou por seus anexos’.*

1 0

[swift][middleware][s3] Content-type of s3api versioning response
by m.victorello＠luizalabs.com 11 Mar '24

11 Mar '24

Hello, We are having some compatibility problems caused by the lack of content-type in this part: https://github.com/openstack/swift/blob/5e5fde12400fc76b9df43b3fcd13eb8a226… def GET(self, req): """ Handles GET Bucket versioning. """ sysmeta = req.get_container_info(self.app).get('sysmeta', {}) elem = Element('VersioningConfiguration') if sysmeta.get('versions-enabled'): SubElement(elem, 'Status').text = ( 'Enabled' if config_true_value(sysmeta['versions-enabled']) else 'Suspended') body = tostring(elem) return HTTPOk(body=body, content_type=None) Is there a reason for it?

1 0

[swift][s3][multipart] S3 multipart re-upload leaves orphan segments
by m.victorello＠luizalabs.com 11 Mar '24

11 Mar '24

Hello, I understand that this is a known issue for some time, but I dont know if it has been resolved. As far as I know stable/2023.2 still has this problem, is there any related work? We think there are two fronts: - Segments of incomplete multipart, forgotten by the user - Completed re-uploads We plan to fix those: - Using the object-expirer in a new middleware - Deploying workers to review all files, checking if they are still in use What are your thoughts?

1 0

[kolla-ansible] Building images from source
by wodel youchi 11 Mar '24

11 Mar '24

Hi, I am trying to build kolla's container images from source, especially octavia's images. I've read the kolla-build documentation, then I tried to follow along but I am having some problems. I am not a developper, my goal is to be able to push patches to kolla images if something goes wrong. For example now I am having a problem with octavia not being able to create an LB when using a self-signed certificate. I searched and I found a patch and I wanted to test-it. https://bugs.launchpad.net/kolla-ansible/+bug/2046382 https://launchpadlibrarian.net/706867161/octavia.patch Here are the steps I followed : - I am using podman - I've created a local registry - pyhton3.9 -m venv kollavnenv/2023.2 - source kollavnenv/2023.2/bin/activate - pip install kolla - pip install podman - I downloaded octavia source code from git 2023.2 version - https://github.com/openstack/octavia/tree/stable/2023.2 - I've prepared kolla_build.conf like this - [octavia] type = local location = /root/work/octavia - And I started the build like this - kolla-build --registry 192.168.2.35:4000 --push -b rocky --tag 2023.2-1 --engine podman --config-file ./kolla_build.conf octavia - Results - (2023.2) [root@r9localrepo work]# podman images REPOSITORY TAG IMAGE ID CREATED SIZE 192.168.2.35:4000/kolla/octavia-driver-agent 2023.2-1 1a6217ad71b4 22 minutes ago 1.31 GB 192.168.2.35:4000/kolla/octavia-api 2023.2-1 41ad8e1760a2 22 minutes ago 1.31 GB 192.168.2.35:4000/kolla/octavia-health-manager 2023.2-1 4922b7f0259f 22 minutes ago 1.28 GB 192.168.2.35:4000/kolla/octavia-housekeeping 2023.2-1 8b5a4785fc18 22 minutes ago 1.28 GB 192.168.2.35:4000/kolla/octavia-worker 2023.2-1 46107a14e78d 22 minutes ago 1.28 GB 192.168.2.35:4000/kolla/octavia-base 2023.2-1 23963c04eda7 22 minutes ago 1.28 GB 192.168.2.35:4000/kolla/openstack-base 2023.2-1 add627cfde2f 25 minutes ago 1.14 GB 192.168.2.35:4000/kolla/base 2023.2-1 a8299a02411a 29 minutes ago 580 MB <none> <none> 0421c38fd25c 8 hours ago 1.14 GB docker.io/library/registry 2 a8781fe3b7a2 6 weeks ago 26 MB quay.io/rockylinux/rockylinux 9 da830f5e2510 3 months ago 181 MB - The problem : - When exploring the octavia-api images for example (podman save),* and verifying the modified file I didn't find the patched-code* It seems that the build process is not using the local code? What am I missing? I think that my kolla_build.conf is wrong or not complete ... any ideas? Regards.

1 2

[kolla-ansible][2023.2] Cloudkitty support for Openseach?
by wodel youchi 11 Mar '24

11 Mar '24

Hi, Does Cloudkitty now support Opensearch as a storage backend in kolla? Regards.

2 1

[oslo][release][requirements] RFE for tooz and taskflow
by Takashi Kajinami 11 Mar '24

11 Mar '24

Hello, During this cycle we updated the redis support implementations to support authentication and SSL for redis sentinel, following the new implementation in oslo.cache. However later it turned out this change breaks kolla because it has been using redis sentinel without authentication while it enables authentication in redis[1]. I've submitted the changes[2] to restore the old behavior (not to enable AUTH or SSL for sentinel even when one is enabled in redis). Once these are merged in master then I'll propose backports to stable/2024.1 and propose new stable/2024.1 release. I'd like to request approval about the release and also bumping tooz and taksflow version in stable/2024.1 requirements to unblock kolla and any other deployments using the partial authentication for redis sentinel. Thank you, Takashi [1] https://bugs.launchpad.net/python-tooz/+bug/2056656 [2] https://review.opendev.org/c/openstack/taskflow/+/912346 https://review.opendev.org/c/openstack/tooz/+/912344/ -- Takashi Kajinami irc: tkajinam github: https://github.com/kajinamit launchpad: https://launchpad.net/~kajinamit

3 3

[neutron] Bug deputy report Mar 4th to 10th
by Oleg Bondarev 10 Mar '24

10 Mar '24

Hello Neutron Team, Bug report for the week of March 4 is below: High: - https://bugs.launchpad.net/neutron/+bug/2055876 - [ovn-octavia-provider] OVN LB health checks for IPv6 not working - in progress: https://review.opendev.org/c/openstack/ovn-octavia-provider/+/911413 - assigned to froyoredhat Medium: - https://bugs.launchpad.net/neutron/+bug/2056199 - ``DvrDriver`` and ``OvnDriver`` incorrectly define distributed flag - fix released: https://review.opendev.org/c/openstack/neutron/+/911151 - fixed by rodolfo-alonso-hernandez - https://bugs.launchpad.net/neutron/+bug/2056276 - unmaintained/yoga periodic jobs broken - confirmed - assigned to yatinkarel - https://bugs.launchpad.net/neutron/+bug/2056366 - Neutron ml2/ovn does not exit when killed with SIGTERM - in progress: https://review.opendev.org/c/openstack/neutron/+/911625 - assigned to otherwiseguy - https://bugs.launchpad.net/neutron/+bug/2056537 - [ovn-octavia-provider] gateway chassis not filled on LogicalRouterPort event - in progress - assigned to froyoredhat - https://bugs.launchpad.net/neutron/+bug/2056558 - ``OVNL3RouterPlugin._port_update`` can be called before the LRP is created in the OVN DB - in progress: https://review.opendev.org/c/openstack/neutron/+/912349 - assigned to rodolfo-alonso-hernande Low: - https://bugs.launchpad.net/neutron/+bug/2055886 - [FT] Check port binding object in "test_virtual_port_host_update_upon_failover" - fix released: https://review.opendev.org/c/openstack/neutron/+/910941 - fixed by rodolfo-alonso-hernandez Thanks, Oleg

1 0

[kolla-ansible][2023.2] Manila cephFS NFS ganesha need some clarifications
by wodel youchi 10 Mar '24

10 Mar '24

Hi, I am trying to configure Manila with cephsfs NFS as backend. My first problem is with installing and configuring nfs ganesha : - Do I have to deploy nfs ganesha from ceph? - What about the /etc/ganesha/ganesha.conf config file? Could someone give me some steps to follow... Regards.

3 11

deploy error
by Parsa Aminian 09 Mar '24

09 Mar '24

hello I want to add new compute to my kolla ansible but i gave this error : TASK [nova-cell : Get a list of existing cells] ****************************************************************************************************************** fatal: [R6SC15.cpaas.ir -> control01]: FAILED! => {"msg": "The conditional check 'existing_cells_list.rc != 0' failed. The error was: error while evaluating conditional (existing_cells_list.rc != 0): 'dict object' has no attribute 'rc'"} can anyone help me whats the problem ?

1 0

[neutron][horizon] disable permission to release floating ip for non-admin users
by Satish Patel 08 Mar '24

08 Mar '24

Folks, I want to disable permission or the horizon button or whatever best way to not allow end users to "Release floating IP" because I want them to stick with assigned IP and not releasing them because of some regulatory process. Not sure what is the best way to have this level of control. I found neutron policy delete_floatingip: but is this the correct way to implement this policy? OR Does Horizon have some level of ACL to remove buttons or disable it? Looking for advice or clues. Thanks!

3 2

[nova][telemetry][watcher][requirements] RFE requests for client libraries
by Elõd Illés 08 Mar '24

08 Mar '24

Hi Requirements team, During today's Release Management weekly meeting we discussed 3 extra client library releases that we would like to ask for Requirements Freeze Exception for: - python-aodhclient [1] 3.5.1 - python-novaclient [2] 18.6.0 - python-watcherclient [3] 4.4.0 contents: [1] python-aodhclient (from comment on the release patch): "Indeed, c10ea92f050b9c53d398eb4570feab2cc442bed7<https://review.opendev.org/#/q/c10ea92f050b9c53d398eb4570feab2cc442bed7> from Dr. Harbott indicated install issues due to the lingering oslo.db cap, 80c9d8608a2f4d04999937800cc30bbf9fc482e0<https://review.opendev.org/#/q/80c9d8608a2f4d04999937800cc30bbf9fc482e0> flagged that there was issue on release notes building that we had missed. And as we had to get those in we also improved testing (not affecting the lib) 31fec512e3ba3c596866c234eefc7a33506c8ef7<https://review.opendev.org/#/q/31fec512e3ba3c596866c234eefc7a33506c8ef7>." c10ea92 Remove oslo.db test cap 31fec51 Add functional tests for prometheus type alarms 80c9d86 Fix releasenotes build of yoga moved to unmaintained [2] python-novaclient: 533d5df5 Bump microversion to 2.96 [3] python-watcherclient 9aace80 Update python classifier in setup.cfg 63d305c Remove untested lower-constraints.txt Thanks, Előd Illés irc: elodilles @ #openstack-release

1 0

[kolla][ptg] Reminder about 2024.2 PTG dates and call for ideas
by Michał Nasiadka 08 Mar '24

08 Mar '24

Hello Koalas, I’ve set up a Dalmatian/2024.2 PTG etherpad - https://etherpad.opendev.org/p/kolla-dalmatian-ptg If you have any ideas for improvements in Kolla/Kolla-Ansible/ansible-collection-kolla or Kayobe - feel free to add that somewhere under line 89. The PTGbot registered meeting slots are: 8-12 April 2024: • Monday - 13.00 - 17.00 UTC (general, Kolla and Kolla-Ansible) • Tuesday - 13.00 - 17.00 UTC (Kolla-Ansible) • Thursday - 13.00 - 15.00 UTC (Kayobe) See you then! Michal

1 0

[heat][monasca][sahara][senlin] Features dependent on inactive projects
by Takashi Kajinami 08 Mar '24

08 Mar '24

Hello, As you know, some of the OpenStack projects were marked inactive during this cycle. There are still on-going discussions but from my view these are very likely excluded from the upcoming 2024.1 release and it's unclear yet if any of these projects will be kept. Currently heat provides features integrated with some of the inactive projects (Monasca, Sahara and Senlin), and we have to decide how we deal with these features[1]. The main concern is that we can't maintain the features for the inactive projects, and IMO we should retire these features if these inactive projects are abandoned or are no longer maintained in the consistent way with the other active projects. Based on the current situation, I'd propose the following steps for upcoming cycles. - Deprecate the features dependent on inactive projects in 2023.2 release - Note that we have to remove these features directly during this cycle in case any problems related to these project block the upcoming heat release. - Remove these features in 2024.1 release unless we are sure that these projects are kept maintained as active projects in the openstack namespace, with following the global release cycle. Please let me know if you have any concern about the proposed plan. If I hear no objections then I'll propose patches for deprecation. Thank you, Takashi Kajinami irc: tkajinam [1] I've submitted a series of patches to remove these features and these would give a clear view about the features affected. https://review.opendev.org/q/topic:%22inactive-project-removal%22+project:o…

3 6

[release] Release countdown for week R-3, Mar 11-15
by Elõd Illés 08 Mar '24

08 Mar '24

Development Focus ----------------- The Release Candidate (RC) deadline is next Thursday, March 14th, 2024. Work should be focused on fixing any release-critical bugs. General Information ------------------- All deliverables released under a cycle-with-rc model should have a first release candidate by the end of the week, from which a stable/2024.1 branch will be cut. This branch will track the 2024.1 Caracal release. Once stable/2024.1 has been created, the master branch will be ready to switch to 2024.2 Dalmatian development. While the master branch will no longer be feature-frozen, please prioritize any work necessary for completing 2024.1 Caracal plans. Release-critical bugfixes will need to be merged in the master branch first, then backported to the stable/2024.1 branch before a new release candidate can be proposed. Actions ------- Early in the week, the release team will be proposing RC1 patches for all cycle-with-rc projects, using the latest commit from the master branch. If your team is ready to go for cutting RC1, please let us know by leaving a +1 on these patches. If there are still a few more patches needed before RC1, you can -1 the patch and update it later in the week with the new commit hash you would like to use. Remember, stable/2024.1 branches will be created with this, so you will want to make sure you have what you need included to avoid needing to backport changes from the master branch (which will technically then be 2024.2 Dalmatian) to this stable branch for any additional RCs before the final release. The release team will also be proposing releases for any deliverable following a cycle-with-intermediary model that has not produced any 2024.1 Caracal release so far. Finally, now is a good time to finalize release highlights. Release highlights help shape the messaging around the release and make sure that your work is properly represented. Upcoming Deadlines & Dates -------------------------- RC1 deadline: March 14th, 2024 (R-3 week) Final RC deadline: March 28th, 2024 (R-1 week) Final 2024.1 Caracal release: April 3rd, 2024 Dalmatian PTG: April 8-12, 2024 Előd Illés irc: elodilles @ #openstack-release

1 0

[tacker][FFE] Mgmt driver sample for deploying Cilium
by Yasufumi Ogawa 08 Mar '24

08 Mar '24

Hi, I'd like to request FFE in this cycle for the update for introducing a sample of management driver for deploying Cilium with K8s VIM as I proposed at the previous IRC meeting. Please let me know if you have any comment although there was nothing opposite then. https://review.opendev.org/c/openstack/tacker/+/911639 Thanks, Yasufumi

1 0

[neutron] Is the vxlan(overlay) network a Provider network or a self-service network
by 韩光宇 08 Mar '24

08 Mar '24

Hi, In neutron install doc[1], I got the concept of Provider network and Self-service network. And I got that: - Provider network bridges virtual networks to physical networks and relies on physical network infrastructure for layer-3 (routing) services - Self-service network routes virtual networks to physical networks using Network Address Translation (NAT) So I understand: Flat/Vlan network are Provide network and vxlan/gre network are Self-service network. But, in openstack cmd, I found that all network types are classified as provider network types. ``` openstack network create --help ... --provider-network-type <provider-network-type> The physical mechanism by which the virtual network is implemented. For example: flat, geneve, gre, local, vlan, vxlan. ``` I am confused, why do vxlan and gre appear in the **provider network type**? According to the installation doc[1], overlay networks should not all be self-service networks Or is the provider network in cmd not the same as the provider network in the installation document, the provider network here is only different from the tenant network? Can someone help me distinguish between these concepts, or suggest questions that I can read: why vxlan is provider network I will appreciate for any help. Best wishes, Han Guangyu [1] https://docs.openstack.org/neutron/latest/install/controller-install-obs.ht…

2 1

[magnum] Speaker Requested for OpenInfra Day Türkiye
by Allison Price 07 Mar '24

07 Mar '24

Hi Magnum community, The organizers of OpenInfra Day Türkiye have reached out mentioning that Magnum has garnered great interest in Türkiye and would like to offer a keynote to any contributor who can provide an overview, new features and the roadmap of the project. The event is May 20 at Boğaziçi University in Istanbul. More information is available here: https://openinfraturkiye.org.tr/ Please let me know if you have any questions. If you represent another OpenStack project and are interested in providing an update, please feel free to reach out. Cheers, Allison Allison Price VP of Marketing & Community OpenInfra Foundation <https://openinfra.dev/> p: +1-214-686-6821

1 0

[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

[neutron] Bug deputy report Feb 25 - Mar 4
by Jakub Libosvar 04 Mar '24

04 Mar '24

Hi, there were only 3 bugs reported. Nothing critical. High —— - [ovn-octavia-provider] OVN LB health checks for IPv6 not working Edit https://bugs.launchpad.net/neutron/+bug/2055876 Assigned to Fernando Low —— - [OVN] "LRP.external_ids" router name is incorrect, we are setting the ID only https://bugs.launchpad.net/neutron/+bug/2055045 Unassigned - [stable-only][OVN] Configure VETH interface MAC address before setting UP the device Edit https://bugs.launchpad.net/neutron/+bug/2055561 Assigned to Rodolfo Patches proposed and merged. May get closed soon.

1 0

[PTLs][release] 2024.1 / Caracal Cycle Highlights
by Herve Beraud 04 Mar '24

04 Mar '24

Hello Everyone! The deadline for cycle highlights is just a few days away, on March 8 [1]. Please be sure to get those in. I look forward to seeing what all you all have accomplished this release! How To Reminder: ------------------------- Simply add them to the deliverables/$RELEASE/$PROJECT.yaml in the openstack/releases repo like this: cycle-highlights: - Introduced new service to use unused host to mine bitcoin. The formatting options for this tag are the same as what you are probably used to with Reno release notes. Also, you can check on the formatting of the output by either running locally: tox -e docs And then checking the resulting doc/build/html/$RELEASE/highlights.html file or the output of the build-openstack-sphinx-docs job under html/$RELEASE/ highlights.html. Thanks [1] https://releases.openstack.org/caracal/schedule.html -- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/

1 0

[publiccloud-sig] Reminder - next meeting March 6th - 0800 UTC
by Felix Kronlage-Dammers 04 Mar '24

04 Mar '24

Hi everyone, This Wednesday (March 6th) the next meeting of the public cloud sig is going to happen. We’ll be meeting at 0800 UTC here: https://meetpad.opendev.org/publiccloud-sig Important: this is a different place than previously. I’ve also updated the Wiki page of the Public-Cloud SIG to reflect this. See also here for all other details: https://wiki.openstack.org/wiki/PublicCloudSIG See you Wednesday! felix -- Felix Kronlage-Dammers Product Owner IaaS & Operations Sovereign Cloud Stack Sovereign Cloud Stack — standardized, built and operated by many Ein Projekt der Open Source Business Alliance - Bundesverband für digitale Souveränität e.V. Tel.: +49-30-206539-205 | Matrix: @fkronlage:matrix.org | fkr(a)osb-alliance.com

1 0

[cinder] FFE request for HPE XP: supporting HA in 2024.1
by 河合敦史 / KAWAI，ATSUSHI 04 Mar '24

04 Mar '24

Hi, I would like to request FFE in the 2024.1 Caracal cycle for the following patch: https://review.opendev.org/c/openstack/cinder/+/892608 Reason for FFE: This patch is one of the important feature for HPE XP driver because it supports a `storage assisted' High Availability. We added the patch into the feature lists for both 2023.2 Bobcat cycle, but it's been merged yet. Additionally, some bugfix patches have a relation chain to this patch. These includes a bug which issued at a customer site on RHOSP. These patches couldn't be merged until merged this patch. Best regards, Atsushi Kawai

2 2

[oslo][release][requirement] FFE request and RFE request for castellan
by Takashi Kajinami 04 Mar '24

04 Mar '24

Hello, We recently caught that castellan 4.4.0, the latest release for caracal, introduced the backword-incompatible change[1] which breaks the existing usage in nova. While we are resolving the problem by the change in nova[2], we discussed this problem in #openstack-release[3], and we agreed that we should make major bump with the upgrade impact properly documented in a release note to announce the breaking change more clearly. Based on the agreement, I'm now preparing a new castellan 5.0.0 release, with the upgrade note added[4]. I'd like to request approval about this release, and also the subsequent upper constraint change to pull castellan 5.0.0 to 2024.1 release. Please let me know if you have any question/concern/etc. Thank you, Takashi [1] https://review.opendev.org/c/openstack/castellan/+/895502/ [2] https://review.opendev.org/c/openstack/nova/+/896100 The same fix for cinder was merged some time ago. https://review.opendev.org/c/openstack/cinder/+/896121 [3] https://meetings.opendev.org/irclogs/%23openstack-release/%23openstack-rele… [4] https://review.opendev.org/c/openstack/castellan/+/910884 https://review.opendev.org/c/openstack/releases/+/910883 -- Takashi Kajinami irc: tkajinam github: https://github.com/kajinamit launchpad: https://launchpad.net/~kajinamit

1 0

Re: openstack-discuss Digest, Vol 64, Issue 122
by BEDDA Fadhel 02 Mar '24

02 Mar '24

help: su -s /bin/bash keystone -c "keystone-manage db_sync" error : Exception ignored in: <function _removeHandlerRef at 0x7f33d74bc3a0> Traceback (most recent call last): File "/usr/lib/python3.10/logging/__init__.py", line 846, in _removeHandlerRef File "/usr/lib/python3.10/logging/__init__.py", line 226, in _acquireLock File "/usr/lib/python3.10/threading.py", line 164, in acquire File "/usr/lib/python3/dist-packages/eventlet/green/thread.py", line 34, in get_ident AttributeError: 'NoneType' object has no attribute 'getcurrent' Thanks Le ven. 1 mars 2024 à 11:17, <openstack-discuss-request(a)lists.openstack.org> a écrit : > 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. [all][ptls][release] Action needed to move forward Unmaintained > branch policy > (Jay Faulkner) > 2. Re: [blazar] Proposing Mark Powers and Matt Crees as core reviewers > (Pierre Riteau) > 3. [oslo] Removing feature branches of oslo.messaging > (Takashi Kajinami) > 4. Re: [all][ptls][release] Action needed to move forward Unmaintained > branch policy > (Dmitriy Rabotyagov) > 5. Re: Need Help to setup Bumblebee VDI project (Andy Botting) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 29 Feb 2024 14:18:36 -0800 > From: Jay Faulkner <jay(a)gr-oss.io> > Subject: [all][ptls][release] Action needed to move forward > Unmaintained branch policy > To: OpenStack Discuss <openstack-discuss(a)lists.openstack.org> > Message-ID: > < > CA+sTGNekJcbP3-ePYjq90ghSiYO-QiNB1dSd0XbVtjV6nktstQ(a)mail.gmail.com> > Content-Type: multipart/alternative; > boundary="0000000000009bb91406128ca449" > > Hi all, > > If you are a PTL of a project, a release liason, or a person generally > interested in older OpenStack branches, please make sure you take a look at > the topic here: https://review.opendev.org/q/topic:%22vwx-unmaintained%22 > and vote appropriately on projects you care about. > > More information can be found in the commit message for the patches > themselves. > > A lot of folks have done work behind the scenes to enable this transition; > please help us by doing your part and getting these reviews done in a > timely manner is one way we can show gratitude to the releases team and > others who have worked to make this transition possible. > > Thanks, > Jay Faulkner > OpenStack TC Chair >

1 0

Need Help to setup Bumblebee VDI project
by Artemio Mendoza 01 Mar '24

01 Mar '24

Hello, I'm trying to set up the Bumblebee (https://github.com/NeCTAR-RC/bumblebee) project on my local computer to test. So I installed docker and tried setup by following the readme. But I'm really new in OpenStack (only tried to run OpenStack through devstack) so I would appreciate it if I could have a very detailed guide. So please share any idea, online video link, or guide document. anything is good to me. Looking forward to hearing from you. Thanks, Artemio Mendoza

3 4

[manila] Feature Freeze Exceptions
by Carlos Silva 01 Mar '24

01 Mar '24

Hello, Zorillas! During this week's IRC meeting we talked about the features we are working on and that need a feature freeze exception, and three contributors shared changes that need some more time to get to completion: 1. Human Readable Export locations: https://review.opendev.org/c/openstack/manila/+/908897 - Core + API https://review.opendev.org/c/openstack/python-manilaclient/+/908909 - CLI https://review.opendev.org/c/openstack/manila/+/908907 - NetApp driver implementation This change relates to an RFE created by operators a couple of cycles ago, and it will enhance the usability for Manila users while mounting shares. The author of this change has been responding to all comments and actively working with the reviewers to implement the suggested modifications. The author mentioned that he would need more time to fix the review comments. 2. Share backups for NetApp driver: https://review.opendev.org/c/openstack/manila/+/910595 - Changes to the backup base driver https://review.opendev.org/c/openstack/manila/+/909115 - NetApp Backup driver The generic approach for share backups was implemented in the previous cycle and NetApp is working on a driver-specific implementation for backups. The author has also been actively working with the reviewers providing updates, but more time would be needed for more review rounds. 3. Deferred deletion: https://review.opendev.org/c/openstack/manila/+/907051 This is also a feature we have been designing for a while, and it will be useful when the backend takes a lot of time to delete shares. Manila will be able to release the quotas and track the shares deletion in the background. The author worked on review comments very fast and addressed the issues pointed by the reviews, but we still need some more review rounds. I would like to grant a feature freeze exception for the three features mentioned and we should aim to merge them by the end of the next week (march 8th). Thank you, carloss

1 0

[release][ironic][swift] cycle-with-intermediary deliverables without any release
by Elõd Illés 01 Mar '24

01 Mar '24

Hi, Quick reminder that we'll need a release very soon for a number of deliverables following a cycle-with-intermediary release model but which have not done *any* release yet in the 2024.1 Caracal cycle: [swift] swift [ironic] bifrost ironic-prometheus-exporter ironic-python-agent-builder ironic-ui networking-baremetal networking-generic-switch Those should be released ASAP, and in all cases before March 14th, so that we have a release to include in the final 2024.1 Caracal release. Előd Illés irc: elodilles @ #openstack-release

2 1

[oslo] Removing feature branches of oslo.messaging
by Takashi Kajinami 01 Mar '24

01 Mar '24

Hello, # I already discussed this with a few people but am sending this email # mostly for records. Currently we have a few feature branches in oslo.messaging but it seems these are not actually used now. feature/amqp-dispatch-router : the feature was already merged into master feature/nats-driver : this branch contains no meaningful change feature/pika : the feature was already merged into master feature/zmq : the feature was already merged into master I'd propose deleting these useless branches. Note that currently the nats-driver branch is causing config error in zuul, which was triggered by TripleO's retirement, and my quick attempt revealed that, as I expected, CI in that branch is badly broken. Please let me know if you have any concern. Thank you, Takashi -- Takashi Kajinami irc: tkajinam github: https://github.com/kajinamit launchpad: https://launchpad.net/~kajinamit

3 2

[release] Release countdown for week R-4, March 04-08
by Herve Beraud 01 Mar '24

01 Mar '24

Development Focus ----------------- We just passed feature freeze! Until release branches are cut, you should stop accepting featureful changes to deliverables following the cycle-with-rc release model, or to libraries. Exceptions should be discussed on separate threads on the mailing-list, and feature freeze exceptions approved by the team's PTL. Focus should be on finding and fixing release-critical bugs, so that release candidates and final versions of the 2024.1/Caracal deliverables can be proposed, well ahead of the final 2024.1/Caracal release date. General Information ------------------- We are still finishing up processing a few release requests, but the 2024.1/Caracal release requirements are now frozen. If new library releases are needed to fix release-critical bugs in 2024.1/Caracal, you must request a Requirements Freeze Exception (RFE) from the requirements team before we can do a new release to avoid having something released in 2024.1/Caracal that is not actually usable. This is done by posting to the openstack-discuss mailing list with a subject line similar to: [$PROJECT][requirements] RFE requested for $PROJECT_LIB Include justification/reasoning for why a RFE is needed for this lib. If/when the requirements team OKs the post-freeze update, we can then process a new release. A soft String freeze is now in effect, in order to let the I18N team do the translation work in good conditions. In Horizon and the various dashboard plugins, you should stop accepting changes that modify user-visible strings. Exceptions should be discussed on the mailing-list. By March 25, 2024 this will become a hard string freeze, with no changes in user-visible strings allowed. Actions ------- stable/2024.1 branches should be created soon for all not-already-branched libraries. You should expect 2-3 changes to be proposed for each: a .gitreview update, a reno update (skipped for projects not using reno), and a tox.ini constraints URL update. Please review those in priority so that the branch can be functional ASAP. The Prelude section of reno release notes is rendered as the top level overview for the release. Any important overall messaging for 2024.1/Caracal changes should be added there to make sure the consumers of your release notes see them. Upcoming Deadlines & Dates -------------------------- Cycle Highlights Due: March 7th, 2024 (R-4 week) RC1 deadline: week of March 11, 2024 (R-3 week) Final RC deadline: week of March 25, 2024 (R-1 week) Final 2024.1/Caracal release: April 3, 2024 Dalmatian PTG: April 8-12, 2024 -- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/

1 0

[TC][openapi] Request for new projects under the OpenStack hat
by gtema 01 Mar '24

01 Mar '24

Hi TC representatives, Some time ago I was communicating about my POC on generating OpenAPI schemas from the source code of services. I continued working on that and have now few projects (that I was developing on GitHub to make life easier) that I would like to bring under the OpenStack hood (and place them under the SDK team). I have also figured out that Nova is now reviewing spec on starting using supporting this (thanks Stephen) and Neutron folks expressed also interest. === codegenerator https://gtema.github.io/openstack-codegenerator/ This project is responsible for generation of the OpenAPI specs and generate other (currently user-facing) code ouf of them === openstack-openapi https://gtema.github.io/openstack-openapi/ This repo hosts rendered specs and provides analogue to the os-api-ref Sphinx extension that renders them into the html (what you see under the link is a mix of Swagger and os-api-ref style). I was not really effectively working on that rendering lately, the repo right now is more or less a storage for the specs themselves with a first sketch of sphinx extension of rendering and basic OpenAPI flavoring doc. === openstack-rs https://gtema.github.io/openstack/ This is a Rust monorepo project with few items: - SDK for OpenStack out of the rendered OpenAPI specs - experimental CLI following very different approach compared to the python- openstackclient. It is compiled into single binary (what helps those not willing to pull whole python with all deps and the insanity we experience lately or those who build docker containers with only OSC inside to bypass the mentioned hell) and purely auto-generated from the specs - [future] openstack-tui (similar to k9s for Kubernetes) Here it is all really oriented only on the user facing tooling. I am very convinced in this project and will continue working on it independent on the outcome. Any objections/ideas/comments? Should I just go and create 3 project-config changes pending the approval? ====== Since I am on this topic anyway I would also like to address another related question. While working for OpenTelekomCloud we developed HashiVault plugin for managing OpenStack credentials as secrets (I had a talk on that in Vancouver). We tried to bring this to OpenDev but were unsure under which namespace. Pretty shortly a Hashi license issue started circling around and after few back and forth iterations we were not sure what to do with that project at all. Anyway the plugin itself is Apache-2 and working. It should be possible to also use it with OpenBAO (as a fork of Vault), but it was not tested so far. I am now not with Telekom anymore, but people there are still willing to contribute it under the OpenStack. Do you have any opinions on that? Is there interest in getting this under the OpenDev and if yes then which namespace (openstack or X)? ======= Thanks, Artem

4 5

[tacker] Gate broken, and a fix patch has been posted
by Ayumu Ueha (Fujitsu) 01 Mar '24

01 Mar '24

Hi Tacker team, As you may know, the following two tacker’s gate jobs are broken since Feb 28. * tacker-functional-devstack-multinode-sol * tacker-functional-devstack-multinode-sol-multi-tenant I have investigated the cause, and posted bug report [1] and fixed patch [2]. Please refer to [1] and [2] for the problem and fix details. To: Yasufumi and Toshiaki, I have already confirmed that the above job is successful. Could you kindly review the patch [2] and merge it if it is no problem. [1] https://bugs.launchpad.net/tacker/+bug/2055431 [2] https://review.opendev.org/c/openstack/tacker/+/910720 Regards, Ayumu

1 0

Patch to ansible module os_subnet
by George Shuklin 01 Mar '24

01 Mar '24

Hello. I wrote a patch for subnet module about a moth ago. Unfortunately, no one looked at it, even after few nags in IRC. Can someone review it, please? https://review.opendev.org/c/openstack/ansible-collections-openstack/+/9073…

1 0

[all][ptls][release] Action needed to move forward Unmaintained branch policy
by Jay Faulkner 01 Mar '24

01 Mar '24

Hi all, If you are a PTL of a project, a release liason, or a person generally interested in older OpenStack branches, please make sure you take a look at the topic here: https://review.opendev.org/q/topic:%22vwx-unmaintained%22 and vote appropriately on projects you care about. More information can be found in the commit message for the patches themselves. A lot of folks have done work behind the scenes to enable this transition; please help us by doing your part and getting these reviews done in a timely manner is one way we can show gratitude to the releases team and others who have worked to make this transition possible. Thanks, Jay Faulkner OpenStack TC Chair

2 1

[blazar] Proposing Mark Powers and Matt Crees as core reviewers
by Pierre Riteau 29 Feb '24

29 Feb '24

Hello, I would like to nominate two new core reviewers for the Blazar project: - Mark Powers from University of Chicago - Matt Crees from StackHPC Mark Powers has been operating Blazar for several years for the Chameleon project (https://www.chameleoncloud.org) and maintains a fork of Blazar with many changes for this environment. The most useful changes are gradually being contributed upstream. Matt Crees has contributed several useful features to Blazar in the past few releases and helps to maintain the code. The Blazar project will benefit from their expertise and I trust their input as reviewers. Best wishes, Pierre Riteau (priteau)

1 1