October 2024 - openstack-discuss - lists.openstack.org

[dev][cinder] Bubbling up maintenance status on a volume from a third-party backend
by David Pineau 22 Oct '24

22 Oct '24

Hello Openstack and Cinder team, I'm currently working on the storage management layer of our company's Openstack platform. As we manage the storage ourselves, we may run background operations, which are akin to a maintenance, on individual volumes, or part of the infrastructure. As a bit of context, this infrastructure will be both exposed to external customers, as well as internal departments, and as such, we are looking for a refined user experience where an error is not a simple "an error occurred in service X", but something potentially actionable by whoever encounters it. At the moment in the Cinder documentation (and what I could find on the discuss archive), there seems to be no way for a Cinder Driver and its backing services to: - Tell Cinder that a specific Volume is undergoing a backend maintenance and should be considered unavailable - raise a relevant error to Cinder about ongoing Operations affecting a Volume within its backend, that cinder could properly react to As a first step, I wanted to check if you, the community, had ever considered this issue (or at least we consider it to be one). We'd be very happy if you had recipes or pieces of advice to share with us on how to handle this. If nothing is available or known, how could we help in bringing such an improvement to Cinder ? Kind regards, -- David Pineau (joa)

3 5

[Openstack-ansible]- Need to delete VM with its OS disk even if it has active snapshot available.
by Danish Khan 22 Oct '24

22 Oct '24

Dear All, When I delete a VM then the OS disk of the VM remains even when I have marked the Volume to get deleted on VM deletion. This is happening only when we have a snapshot of the OS disk or snapshot of the complete VM available. Can we configure it in a way then either that the VM should get deleted completely with OS disk even if we have the snapshot available or the VM deletion task should fail if the snapshot is available. Regards, Danish

1 0

[nova][libvirtd] internal error: unable to execute QEMU command 'query-named-block-nodes'
by Satish Patel 22 Oct '24

22 Oct '24

Folks, I have a ceph cluster and recently I configured rbd-mirror to replicate all data to remove ceph cluster for disaster recovery. Yesterday for POC we did a hard cutover on ceph and point openstack to the new cluster. All other vms came back up fine but 2 vms stuck in this error state in libvirt logs 2024-01-31 22:44:37.591+0000: 474597: error : qemuMonitorJSONCheckErrorFull:399 : internal error: unable to execute QEMU command 'query-named-block-nodes': cannot read image start for probe: Permission denied If it's a wider issue than it should impact all the vms but why only two VM stuck and not starting and libvirt giving me this error in logs nova-compute logs also showing same error 2024-01-31 22:44:40.925 7 INFO nova.compute.manager [None req-b33485b5-8740-48ae-8b5b-a440de3f11a4 c48fcfb9347f413f92fcece065644b00 ca5c652478c7429e964257990800e9cb - - default default] [instance: 2de0f880-77c7-4d2c-9e01-898c57ad3693] Successfully reverted task state from powering-on on failure for instance. 2024-01-31 22:44:40.944 7 ERROR oslo_messaging.rpc.server [None req-b33485b5-8740-48ae-8b5b-a440de3f11a4 c48fcfb9347f413f92fcece065644b00 ca5c652478c7429e964257990800e9cb - - default default] Exception during message handling: libvirt.libvirtError: internal error: unable to execute QEMU command 'query-named-block-nodes': cannot read image start for probe: Permission denied

3 8

[swift][ptg] Ops Feedback Session - 23 October at 14:00 UTC
by Tim Burke 21 Oct '24

21 Oct '24

As we've done in PTGs past, we're getting devs and ops together to talk about Swift: what's working, what isn't, and what would be most helpful to improve. We're meeting on meetpad (https://meetpad.opendev.org/p/swift-epoxy-ops-feedback) on Wednesday at 14:00UTC -- if you run a Swift cluster, we hope to see you there! Even if you can't make it, we'd appreciate it if you can offer some feedback on the etherpad (https://etherpad.opendev.org/p/swift-epoxy-ops-feedback) This has always been a highlight at every PTG for the swift developers. Have your say and help make the next Swift the best one yet! Tim

1 0

[all][rbac] Canceling policy popup team tomorrow meeting
by Ghanshyam Mann 21 Oct '24

21 Oct '24

Hello Everyone, Due to vPTG weeks, I am cancelling the policy pop-up tomorrow meeting. https://wiki.openstack.org/wiki/Consistent_and_Secure_Default_Policies_Popu… -gmann

1 0

[cinder] 2025.1 PTG reminder
by Jon Bernard 21 Oct '24

21 Oct '24

Hello all, We covered the schedule in last week's meeting but I wanted to post it here for reference. For Cinder, we are meeting Wednesday, Thursday, and Friday of this week from 14:00 UTC until 17:00 UTC. I have consolidated and updated our etherpad [1] to include both a tentative schedule that includes cross-project session commitments and the set of proposed topics. As we did in the previous PTG, we'll be using the same google meet link and the sessions will be recorded. Everything should be noted in the etherpad. If you notice something is missing please add it or reach out with any questions. See you all in a couple of days! [1] https://etherpad.opendev.org/p/epoxy-ptg-cinder -- Jon

1 0

[openstack-helm] 2025.1 PTG reminder
by Vladimir Kozhukalov 21 Oct '24

21 Oct '24

Hi dear helmers, This is a reminder that we have a PTG session scheduled at 15:00-18:00 UTC on Wednesday 2024-10-23 [1]. This time we have quite a lot to discuss (and this is good) so I booked a 3 hours session (instead of our usual 2 hours). If you have something to discuss please put topics to the Etherpad [2] [1] https://ptg.opendev.org/ptg.html [2] https://etherpad.opendev.org/p/oct2024-ptg-os-helm -- Best regards, Kozhukalov Vladimir

1 0

Spot Instances
by Mia 21 Oct '24

21 Oct '24

Hello everyone, I am working on a project in the OpenStack environment. More precisely, I am looking into the implementation of spot instances as a cost optimization strategy and better resource utilization. If any community members could share their experiences and insights related to the following areas, it would be greatly appreciated. Implementation Strategies: How did you go about implementing spot instances in your cluster? Challenges Faced: Mention some of the challenges or limitations. Best Practices: Do you have any recommendations or best practices that you would like to suggest for seamless deployment? Thank you very much for your time and support.

8 11

[all][designate][manila] Grenade job failures caused by GLOBAL_VENV=True
by Takashi Kajinami 21 Oct '24

21 Oct '24

Just in case you are not aware of the situation. The change to enable GLOBAL_VENV in grenade job was recently merged[1] in core grenade. As we saw when the same was introduced in devstack some time ago, some project got their (grenade) jobs broken and need a few adjustments. [1] https://review.opendev.org/c/openstack/grenade/+/930507 So far I'm aware that the change affected manila and designate, which I'm fixing by the changes below. Please be careful in case you see grenade job failing in your project. designate: - https://review.opendev.org/c/openstack/designate/+/932697 Disable GLOBAL_VENV in grenade This is temporal workaround and needs to be reverted once the actual fix below is merged in master and backported to stable 2024.1/2 - https://review.opendev.org/c/openstack/designate/+/932697 devstack: Fix manage.py execution with GLOBAL_VENV This actually fixes the current issue caused by GLOBAL_VENV=True. As noted above, we have to backport this to stable branches manila: - https://review.opendev.org/c/openstack/manila/+/932671 Disable GLOBAL_VENV in grenade This is temporal workaround and needs to be reverted once the actual fix below is merged in master and backported to stable 2024.1/2 - https://review.opendev.org/c/openstack/manila/+/932665 devstack: Fix missing manila command This actually fixes the current issue caused by GLOBAL_VENV=True. As noted above, we have to backport this to stable branches Thank you, Takashi -- Takashi Kajinami irc: tkajinam github: https://github.com/kajinamit launchpad: https://launchpad.net/~kajinamit

4 4

[ptg][sunbeam] Epoxy cycle PTG 2025.1 schedule
by Guillaume Boutry 21 Oct '24

21 Oct '24

Hi All, OpenStack PTG has been scheduled on Oct 22nd and Oct 24th 2024 [1] and I have scheduled the following time slots for the OpenStack Sunbeam project. Tuesday 22 October 2024 0600 UTC to 0800 UTC Thursday 24 October 2024 1400 UTC to 1600 UTC The meeting links and details are in ptg link [2] or etherpad [3]. Feel free to add the topics of interest to discuss in the etherpad [3]. [1] https://openinfra.dev/ptg/ [2] https://ptg.opendev.org/ptg.html [3] https://etherpad.opendev.org/p/oct2024-ptg-sunbeam Looking forward to seeing you next week! Regards, Guillaume Boutry

1 0

[tacker] Cancel IRC meeting this week
by Yasufumi Ogawa 20 Oct '24

20 Oct '24

Hi tacker team, Since we have vPTG sessions, I'm going to cancel weekly IRC meeting tomorrow. Thanks Yasufumi

1 0

[ptl][tc][all] Community Leaders meeting at the PTG
by Goutham Pacha Ravi 20 Oct '24

20 Oct '24

Hello PTLs, Project Liaisons, Core Reviewers, and invested maintainers, The TC is hosting a cross project session with all OpenStack project leaders at 1400 UTC today (2024-10-21). Please see the PTG schedule at https://ptg.opendev.org/ptg.html and the TC PTG etherpad for details: https://etherpad.opendev.org/p/oct2024-ptg-os-tc We look forward to seeing you all there! P.S: while you are there, you may also be interested in the cross project goal proposal/discussion for migrating away from Eventlet (1500 UTC); and other community-wide topics in the TC PTG room. Thanks, Goutham Pacha Ravi OpenStack TC Chair

1 0

[neutron] Bug report week 42th (14 Oct - 20 Oct)
by Rodolfo Alonso Hernandez 20 Oct '24

20 Oct '24

Hello Neutrinos: This is the bug report of the 42th week (14 Oct - 20 Oct). High: * https://bugs.launchpad.net/neutron/+bug/2083832: "[OVN] Host_id value on lsp for router gateway is not updated on failover". Assigned. In progress: https://review.opendev.org/c/openstack/neutron/+/931632. * https://bugs.launchpad.net/neutron/+bug/2084977: "Deleting a security group fails with "Cannot find Port_Group with name=pg_<id>" when neutron-api is run by httpd + mod_wsgi". *Not assigned*. Medium: * https://bugs.launchpad.net/neutron/+bug/2084446: "Scaling down neutron-openvswitch-agent don't remote it's tunnel endpoints". *Not assigned*. * https://bugs.launchpad.net/neutron/+bug/2084516: " "Tagging" extension POST for QoS policies doesn't work". *Not assigned*. * https://bugs.launchpad.net/neutron/+bug/2084536: "OVN: Connecting internal tenant VLAN networks to virtual routers when external (BM) ports are also present". *Not assigned*. * https://bugs.launchpad.net/neutron/+bug/2084782: "[OVN] VLAN/flat LRP should be updated when the router networks are updated". Assigned. * https://bugs.launchpad.net/neutron/+bug/2084906: " Hardcoded keepalived configuration parameters". Assigned. In progress: https://review.opendev.org/c/openstack/neutron/+/932716. RFE: * https://bugs.launchpad.net/neutron/+bug/2084894: " [RFE] Support injection of local NTP servers into subnets". * https://bugs.launchpad.net/neutron/+bug/2084905: "[RFE][OVN] Make use of the new flag 'always_tunnel' to tunnel the E/W traffic between logical switches". Regards.

1 0

[tc][all] OpenStack Technical Committee Weekly Summary and Meeting Agenda (2025.1/R-23)
by Goutham Pacha Ravi 20 Oct '24

20 Oct '24

Hello Stackers, This week, the OpenStack community is convening virtually to set the agenda for the 2025.1 "Epoxy" release and beyond [1][2]. As of today, there are 33 different discussion tracks spread over five days. Now's as good a time as ever to review the Community Code of Conduct as we step into this event [3]. In the past week, the North American section of the OpenInfra community gathered in Indianapolis (and virtually) for a two-day conference. I had the privilege to attend in person and chat with numerous users, operators, and contributors. The community is as energetic as ever, as evidenced by the participation we saw in the leadership meet-and-greet event [4]. Amy Marrich (spotz) organized this event, and we had representation from the OpenInfra Board, Zuul, OpenStack TC, SIGs, and PTLs. The audience learned the essence of our "Open Community," how elections are conducted, what different community leadership roles are, and how one can participate in OpenInfra governance. We brainstormed how to revive projects with dwindling contributors and recapped takeaways from the "Bridging the Gap" and Security SIG-related discussions. Prof. Corey Leong (profcorey) from Valencia College volunteered to propose a "Higher Education" Special Interest Group focused on increasing awareness and creating learning material for university students interested in joining the OpenStack community. I'll share a link with video recordings of this conference in a future post. === Weekly Meeting === Dmitriy Rabotyagov (noonedeadpunk) chaired the weekly IRC meeting [5] of the OpenStack Technical Committee last week. We had fewer attendees than usual, but it was a productive discussion nevertheless. We prepped the TC's PTG etherpad [6] with topics and timings for the discussion. As is tradition, please allow flexibility in terms of the discussion schedule. Discussions may start a bit later (or earlier) than planned, and we'll have to be dynamic to accommodate scheduling conflicts, as many contributors are involved across multiple topics. In lieu of the PTG, the weekly IRC meeting scheduled for 2024-10-22 has been canceled [7]. We briefly discussed the leadership appointment patches concerning the Watcher and Mistral project teams. These are still being reviewed, and we'll try to get them closed out after the PTG week. We also discussed grenade job changes that Ghanshyam Mann (gmann) and other community members have been pursuing [8]. Concerns were raised about projects (like Kolla and Loci) publishing container images under the OpenStack name without a clear security policy. The need to clarify OpenStack's support and security posture on such deliverables was discussed. We have more to discuss on this topic at the PTG and beyond. The next weekly IRC meeting for the OpenStack Technical Committee is on 2024-10-29. The agenda is up early [9], but I'll write to you once again before it is formalized. I look forward to seeing you all at the PTG and possibly seeding more topics for this weekly meeting afterward. === Governance Proposals === ==== Open for Review ==== Add Cinder Huawei charm | https://review.opendev.org/c/openstack/governance/+/867588 Appoint Ke Chen as PTL for Watcher | https://review.opendev.org/c/openstack/governance/+/932419 Adding Axel Vanzaghi as PTL for Mistral | https://review.opendev.org/c/openstack/governance/+/927962 Retire kuryr-kubernetes and kuryr-tempest-plugin | https://review.opendev.org/c/openstack/governance/+/922507 Propose a pop-up team for eventlet-removal | https://review.opendev.org/c/openstack/governance/+/931978 Propose to select the eventlet-removal community goal | https://review.opendev.org/c/openstack/governance/+/931254 === Upcoming Events === 2024-10-21 to 2024-10-25: OpenInfra Project Teams Gathering: https://openinfra.dev/ptg/ 2024-10-27: All Things Open: https://allthingsopen.org/ 2024-11-04: OpenInfra Board Meeting: https://board.openinfra.dev/ 2024-11-15: KubeCon + CloudNativeCon: https://events.linuxfoundation.org/kubecon-cloudnativecon-north-america/ Thank you very much for reading! On behalf of the OpenStack TC, Goutham Pacha Ravi (gouthamr) OpenStack TC Chair [1] 2025.1 "Epoxy" Release Schedule: https://releases.openstack.org/epoxy/schedule.html [2] "Epoxy" PTG Schedule: https://ptg.opendev.org/ptg.html [3] OpenInfra Community Code of Conduct: https://openinfra.dev/legal/code-of-conduct [4] OpenInfra Leadership Meet-and-Greet: https://etherpad.opendev.org/p/leadership-na [5] TC Meeting IRC Log, 2024-10-15: https://meetings.opendev.org/meetings/tc/2024/tc.2024-10-15-18.00.log.html [6] TC PTG Etherpad: https://etherpad.opendev.org/p/oct2024-ptg-os-tc [7] TC IRC meeting 2024-10-22 is canceled: https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… [8] Grenade Job changes: https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… [9] TC Meeting Agenda, 2024-10-29: https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting

1 0

[ptg][tacker] Epoxy vPTG planning
by Yasufumi Ogawa 20 Oct '24

20 Oct '24

Hi tacker team, I've booked slots for our two days vPTG sessions this week as I've announced on the previous weekly meeting. Please find the etherpad [1] and register your proposals for Epoxy release. - 23th Oct. 6am-8am UTC (3pm-5pm JST/KST) - 24th Oct. 6am-8am UTC (3pm-5pm JST/KST) [1] https://etherpad.opendev.org/p/oct2024-ptg-tacker Thanks, Yasufumi

1 0

[ptg][tacker] Epoxy vPTG planning
by Yasufumi Ogawa 20 Oct '24

20 Oct '24

Hi tacker team, I've booked slots for our two days vPTG sessions this week as I've announced on the previous weekly meeting. Please find the etherpad [1] and register your proposals for Epoxy release. - 23th Oct. 6am-8am UTC (3pm-5pm JST/KST) - 24th Oct. 6am-8am UTC (3pm-5pm JST/KST) [1] https://etherpad.opendev.org/p/oct2024-ptg-tacker Thanks, Yasufumi

1 0

[manila] 2025.1/Epoxy PTG planning
by Carlos Silva 20 Oct '24

20 Oct '24

Hello Zorillas and Interested stackers, The OpenInfra PTG will take place from Oct 21st to 25th. I have reserved some time slots for the Manila discussions [1]. If you would like to bring up any topics during the PTG, please add them to the PTG planning etherpad [2] by next Tuesday (Oct 16th). I intend to have the tentative schedule ready next Thursday and share it with you. Additionally, in case you have any time slot preferences, please let me know and I will do my best to accommodate them. [1] https://ptg.opendev.org/ptg.html [2] https://etherpad.opendev.org/p/epoxy-ptg-manila-planning Looking forward to it! Regards, carloss

1 1

Invitation to Discuss Collaboration Opportunities Between OpenStack and OceanBase
by 汪鹏(酒晨) 19 Oct '24

19 Oct '24

Dear OpenStack Team, I hope this message finds you well. My name is Peng Wang, and I am the Global Technical Evangelist at OceanBase. We have been following the remarkable achievements of the OpenStack community and are excited about the potential opportunities for collaboration between OceanBase and OpenStack. OceanBase is a high-performance distributed database, now open-source, designed to meet the demands of large-scale applications with exceptional scalability and reliability. We are actively exploring opportunities to seamlessly integrate it into the OpenStack ecosystem, proposing OceanBase as an alternative backend database option to enhance the flexibility and resilience of OpenStack deployments. We would like to invite your team to a virtual meeting to discuss this collaboration in more detail, including the technical aspects, shared customers, and potential benefits for the OpenStack ecosystem. The proposed meeting details are as follows: Date: 10/25/2024 Time: 13:00 UTC Duration: 1 hour Location: PTG Opendev Meeting Agenda: 1. Introduction to OceanBase and its architecture 2. Overview of the proposed pull request to integrate OceanBase with OpenStack 3. Introduction to the mutual benefits and shared interests between OceanBase and OpenStack 4. Exploring potential collaboration and future opportunities 5. Q&A and open discussion We believe this integration will be a significant step toward further empowering OpenStack with a robust and scalable database solution. We look forward to the opportunity to work closely with your team to bring this vision to life. Please let us know your availability for the proposed meeting or suggest an alternative time that works for you. We would be happy to adjust accordingly. Thank you for your time, and we look forward to your response. Best Regards, Peng Wang Global Technical Evangelist, OceanBase Tel: 86+ 13585603170 Email: jiuchen.wp(a)oceanbase.com from 阿里邮箱 macOS

2 2

[Telemetry] Takashi for Telemetry core
by Erno Kuvaja 19 Oct '24

19 Oct '24

Hi all, I'd like to address massive oversight from my side regarding Telemetry core by adding Takashi Kajinami to the group. Honestly based on all his involvement in the various Telemetry projects I just assumed he was in the core group already and I was pretty shocked that was not the case. I've already talked with him and would like to add him ASAP. As in by the end of the week, so if anyone has objections, please raise them now. Thanks Takashi for all your invaluable contributions and reviews, please keep them coming. - Erno "jokke" Kuvaja

2 1

[ptg][publiccloud-sig] PTG meetings for tthe publiccloud-sig
by Felix Kronlage-Dammers 19 Oct '24

19 Oct '24

Ahoi, as all other teams the publiccloud-sig is getting ready for the upcoming PTG as well :) We’re very much looking forward to the next week. The publiccloud-sig will meet for the PTG on Tuesday at 1600 UTC and on Wednesday at 0700 UTC. The regular etherpad[1] contains a list of items that we collected and that we will likely address. The tuesday slot should also allow for participants not in one of the EU and NZ timezones to join - we would love to get a nice group together. The PTG also serves as a good starting point to become more active in the publiccloud-sig :) See ya next week! felix [1] https://etherpad.opendev.org/p/publiccloud-sig

1 0

[watcher]Interest in a session at upcoming PTG?
by Ronelle Landy 18 Oct '24

18 Oct '24

Hello, There has been some renewed interest in the Watcher project. We wanted to reach out to see if the project PTL (or anyone else) would be willing to run/attend a session on Watcher at the upcoming PTG. Would it make sense to hold a dedicated session or discuss plans at one of the TC sessions? Thank you!

3 3

[qa][ptg] Virtual 2025.1 vPTG Planning
by Martin Kopec 18 Oct '24

18 Oct '24

Hello everyone, here is [1] our etherpad for the Epoxy/2025.1 virtual PTG. Please, add your topics there if there is anything you would like to discuss / propose for discussion ... You can also vote for time slots of the sessions so that they fit your schedule [2]. The number of slots will depend on the number of topics proposed in [1]. [1] https://etherpad.opendev.org/p/oct2024-ptg-os-qa [2] https://framadate.org/juHJSryIYHMRwdHA Thanks, -- Martin Kopec Principal Software Quality Engineer Red Hat EMEA IM: kopecmartin

1 1

[ptg][sdk][cli] PTG meeting of the SDK team
by Artem Goncharov 18 Oct '24

18 Oct '24

I have booked a slot for Monday 14:00-15:59 UTC for the SDK team (Monday is the day with least conflicts). Etherpad: [1] Topics: * state of the OpenAPI * codegenerator: state and next steps [1]: https://etherpad.opendev.org/p/oct2024-ptg-os-sdkcli See you there, Artem

1 0

[kolla-ansible] Problems with my lab . Many bugs with python
by Franck VEDEL 18 Oct '24

18 Oct '24

hello. I'm going crazy. Last year I set up a lab for students. The platform: ubuntu 22.04, kolla-ansible, antelope. Everything works perfectly by following the link https://docs.openstack.org/kolla-ansible/2023.1/user/quickstart.html We start with all-in-one in a virtual machine, then 20 hours later, a cluster of 3 nodes on DELL servers, with TLS, Ceph. I was super happy. I'm coming back to the subject a year later. I'm thinking about doing an update and so I start, still on ubuntu 22.04, by following the link https://docs.openstack.org/kolla-ansible/2024.1/user/quickstart.html well, it doesn't work. after hours of research, I resume an installation with Antelope. It doesn't work either. New research... and I come across a bug. Someone explains that you have to downgrade MarKupSafe to version 2.1.5. Okay, I'll do it. I start again with Caracal... and now, in the Horizon interface, we no longer see multiple domains. It doesn't work. New bug. I come back with Antelope and MarkupSafe == 2.1.5... it works, and my two domains are OK in Horizon. So I continue with Antelope ..... and now, when I try to activate TLS, it's impossible to do the "deploy". New bug but on rabbitmq. I'm going crazy. New bug but no solutions... The only solution I found is to restart a virtual machine that worked last year, do a pip freeze and in this year's installation, use last year's pip freeze. I can't use Caracal because the second domain is not visible. I can (maybe I'm not done yet) use Antelope but with last year's requirements.txt. How do I get out of this situation? How would you do it in my place knowing that I want to keep Ubuntu 22.04? Bobcat? I've already spent days on the subject. I don't have time anymore. That's why I'm asking for your help. Thansk a lot Franck

1 0

[neutron] Canceling weekly meetings tomorrow and next week
by Brian Haley 17 Oct '24

17 Oct '24

Hello Neutrinos: I'm going to cancel tomorrow's drivers meeting as well as our meetings next week as we have the PTG sessions. Please add any items there if you wish to discuss them [0]. Have a nice weekend! -Brian [0] https://etherpad.opendev.org/p/oct2024-ptg-neutron

1 0