- openstack-discuss - lists.openstack.org

Rabbit mq connections keep on going up, why channels and connections not closing?
by Shrey Chauhan 13 May '24

13 May '24

Hi all, I am observing a behaviour which I am not sure is right or wrong, or something I should be concerned about? Currently I am using openstack xena with rabbit-mq message broker. rabbit mq version is 3.8.3 amqp version 5.0.8 I have installed rabbit management plugin on my cluster, and I observe whenever I perform any task like a resize. My connection and channel counts go up, and with every operation it goes up. I am worried that at some point I will hit some kind of connection threshold. I just want to understand if services like nova, cinder reuse an open rabbit mq connection or reopen for every operation, and if they open msg queue connection for every operation do they close the connection once the action is done Am I missing configuration in my setup of rabbit mq with openstack? Please help me understand this scenario. Thanks for help in advance. Thanks, Shrey Chauhan

1 0

[ops] Inquiry Regarding Addition of DH Groups in OpenStack VPNaaS
by Shubham Yadav 13 May '24

13 May '24

Hello , I hope this message finds you well. I am reaching out to inquire about the possibility of adding additional DH (Diffie-Hellman) groups to the VPNaaS (VPN as a Service) project in OpenStack. Currently, our setup involves using DH groups 14, 16, 20, and 21 on Fortigate routers. However, the available DH groups at the OpenStack Web UI for creating IPSEC policies are limited to groups 2, 5, and 14. Could you please provide insights into whether there are plans to introduce more DH groups into the VPNaaS project? This addition would greatly benefit our configurations and improve compatibility with our existing infrastructure. Thank you in advance for any information or guidance you can provide on this matter. Best regards, Shubham

2 1

[oslo][release] Changing back release model of tooz ?
by Takashi Kajinami 13 May '24

13 May '24

Hello, As you may know, tooz was moved to the independent release model[1] after wallaby release because of its stable code base at that time. However, we introduced several features/improvements in tooz during a few cycles and I'm wondering if we can revisit its status now. One actual problem I'm seeing now is that, we recently got a bug report[2] about the redis sentinel support which we added during 2024.1 cycle but we can't backport the required bug fix to 2024.1 because of no stable branch. Given the situation, I'm wondering if it makes sense (and is possible) to move tooz back to the cycle-with-intermediary model, and create 2024.1 branch from 6.1.0 (the last release during 2024.1 cycle) now, so that we can maintain 2024.1 releases with future bug fixes brackported. [1] https://review.opendev.org/c/openstack/releases/+/788230 [2] https://bugs.launchpad.net/python-tooz/+bug/2063857 -- Takashi Kajinami irc: tkajinam github: https://github.com/kajinamit launchpad: https://launchpad.net/~kajinamit

4 5

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

12 May '24

Hello Stackers, We're officially in milestone-1 week for the 2024.2 (Dalmatian) release cycle [1]. Teams are actively planning design specification freezes, hackathons, and bug squashes. I'm delighted to announce that three Outreachy interns have been funded to work with the OpenStack community [2]. Please join me in welcoming Mohd Ariq (tspyderboy), Okeke Christian Chima (cokeke), and Abby Nduta (AbbyNduta). Mohd Ariq and Christian will be working with members of the OpenStack Manila project team, while Abby will be working with members of the OpenStack Horizon project team. Congratulations, interns! These internships begins at the end of May and will conclude at the end of August. There have been a few governance changes in the past week that I'd like to brief you about: The "Consistent and Secure Default RBAC" goal has new milestone requirements. All projects are expected to transition oslo.policy's "enforce_scope" and "enforce_new_defaults" options to True during the 2024.2 release cycle. These options will be removed from oslo.policy during the 2025.1 release cycle. [3] openstack/kuryr and openstack/kuryr-libnetwork are now under the maintainership of the openstack/zun ("Container as a service") team. The TC has adopted a house rule to mark projects that have identified no leadership as "inactive" projects [4]. We've merged slaweq's summary of the 2023 OpenStack User Survey [5]. Thanks, slaweq, and to all of you who took the survey. === Weekly Meeting === Last week's TC meeting was held simultaneously on Zoom (a recording is on YouTube [6]) and IRC on May 7th, 2024. The meeting was logged to eavesdrop [7]. Over the years, we've come to realize that monitoring project activity through objective tools wasn't representing the picture accurately. Several mature/feature-complete projects will seemingly be "inactive," and what we're interested in assessing is whether there are active maintainers tackling security and project infrastructure concerns. Artem Goncharov (gtema) will write up a proposal to tag inactive projects more prominently. We discussed a proposal to change the Distributed Project Leadership model to require DPL liaisons to re-assert their interest at the beginning of each cycle. The proposal also suggests appointing liaisons from the TC to monitor projects that have this leadership model. TC Members would be welcome to nominate themselves as liaisons for projects following DPL if this proposal is accepted. We took some AIs to continue the cleanup of maintainers on OpenStack's packages on PyPI - an ongoing community-wide effort [8]. We discussed the open goal proposal to replace eventlet. The Technical Committee wants to ensure that we're not advocating for a one-size-fits-all solution to the problem of threading in OpenStack projects. Hence, we'd prefer not to merge the proposal to replace eventlet with asyncio. Instead, we want to encourage projects to independently explore solutions that make sense to their individual architecture - which could be asyncio, native threads, or any other threading paradigm/library. We are supportive of ensuring there's no imposition of any specific library or threading mechanism imposed via oslo libraries. JayF will be summarizing this view to this mailing list soon. The meeting concluded with an open discussion on DevStack setup time and an outdated (but relevant) proposal related to OSC as a service on DevStack. Tomorrow's meeting is back on OFTC/IRC, and the call details and agenda are at [9]. We look forward to seeing you there. The TC is always honored to chat with you, so please join us, and feel free to add anything to the agenda that you'd like to chat with us about! === Goal Proposals === As stated above, this goal proposal needs your weigh-in: - Migrate eventlet usages to asyncio (https://review.opendev.org/c/openstack/governance/+/902585) === Governance Proposals === ==== Merged ==== - Remove ref of bylaw Appendix 4 | https://review.opendev.org/c/openstack/governance/+/916942 - Add timeline to remove enforce_scope in RBAC goal | https://review.opendev.org/c/openstack/governance/+/915179 - Move openstack/kuryr and openstack/kuryr-libnetwork to Zun | https://review.opendev.org/c/openstack/governance/+/917517 - 2023 User Survey TC Question Analysis | https://review.opendev.org/c/openstack/governance/+/900516 - Add option to move leaderless project to Inactive status | https://review.opendev.org/c/openstack/governance/+/914726 ==== Open for review/discussion ==== - Update to include docs and miscellaneuos repos for AC status | https://review.opendev.org/c/openstack/governance/+/915021 - Add DPL model & liaison reset policy | https://review.opendev.org/c/openstack/governance/+/916833 Thank you very much for reading! On behalf of the OpenStack TC, Goutham Pacha Ravi (gouthamr) OpenStack TC Chair [1] https://releases.openstack.org/dalmatian/schedule.html [2] https://www.outreachy.org/alums/2024-05/#:~:text=Openstack [3] https://governance.openstack.org/tc/goals/selected/consistent-and-secure-rb… [4] https://governance.openstack.org/tc/reference/emerging-technology-and-inact… [5] https://governance.openstack.org/tc/user_survey/analysis-2023.html [6] https://youtu.be/-WZT7PC3sig [7] https://meetings.opendev.org/meetings/tc/2024/tc.2024-05-07-18.00.log.html [8] https://etherpad.opendev.org/p/openstack-pypi-maintainers-cleanup [9] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting

1 0

openstack boot an instance from an IDE volume migrated from VMware
by luckydog xf 10 May '24

10 May '24

hi, list, I'm going to boot an instance from an existing volume, and it is a Windows 2016 migrated from VMware. So the bus must be set to 'ide' mode, otherwise it fails to boot up. Let's assume this volume UUID is xyz and it's bootable. I cloned it by clonezilla from VMware ESXI. since virtio drive wasn't installed in Windows, so it must be set to ide. So what's the right way to boot it from this volume and set it to IDE? I have tried lots of ways, like --- openstack server create test-windows --flavor 4 --nic net-id=7b57ee99-136f-4aa7-b3fe-a4958ec8c644 --block-device id=xxxx:disk_bus=ide and ... --block-device-mapping. But unfortunately, none of them work. And there are too many outdated docs like disk_bus=ide and bus=ide. Not sure which one works. This is fairly frustrating. I'm still struggling with this issue and need your help. Thanks a lot.

3 7

[tc][all][ec2-api] Retiring the ec2-api project
by Ghanshyam Mann 10 May '24

10 May '24

Hello everyone, As you might know, the ec2-api project is not active and was marked 'inactive' since 2024.1 cycle[1]. In this cycle also, this project is leaderless[2] and no maintainer stepped up to maintain it. As discussed in the Leaderless project etherpad[2], the next step is to retire the project. I'm sending this email to propose the ec2-api retirement and based on the response, I will proceed next. [1] https://governance.openstack.org/tc/reference/emerging-technology-and-inact… [2] https://etherpad.opendev.org/p/2024.2-leaderless#L72 -gmann

1 1

[tc][all][senlin] Retiring the Senlin project
by Ghanshyam Mann 10 May '24

10 May '24

Hello everyone, As you might know, the Senlin project is not active and was marked 'inactive' since 2024.1 cycle[1]. In this cycle also, this project is leaderless[2] and no maintainer stepped up to maintain it. As discussed in the Leaderless project etherpad[2], the next step is to retire the project. I'm sending this email to propose the Senlin retirement and based on the response, I will proceed next. [1] https://governance.openstack.org/tc/reference/emerging-technology-and-inact… [2] https://etherpad.opendev.org/p/2024.2-leaderless#L72 -gmann

1 1

[tc][all][solum] Retiring the Solum project
by Ghanshyam Mann 10 May '24

10 May '24

Hello everyone, As you might know, the Solum project is not active and was marked 'inactive' since 2024.1 cycle[1]. In this cycle also, this project is leaderless[2] and no maintainer stepped up to maintain it. As discussed in the Leaderless project etherpad[2], the next step is to retire the project. I'm sending this email to propose the Solum retirement and based on the response, I will proceed next. [1] https://governance.openstack.org/tc/reference/emerging-technology-and-inact… [2] https://etherpad.opendev.org/p/2024.2-leaderless#L72 -gmann

1 1

[tc][all][murano] Retiring the Murano project
by Ghanshyam Mann 10 May '24

10 May '24

Hello everyone, As you might know, the Murano project is not active and was marked 'inactive' since 2024.1 cycle[1]. Due to a critical bug in Murano, the TC needs to pass a resolution to stop its 2024.1 release[2]. In this cycle also, this project is leaderless[3] and no maintainer stepped up to maintain it. As discussed in the Leaderless project etherpad[3], the next step is to retire the project. I'm sending this email to propose the Murano retirement and based on the response, I will proceed next. [1] https://governance.openstack.org/tc/reference/emerging-technology-and-inact… [2] https://governance.openstack.org/tc/resolutions/20240227-remove-murano-from… [3] https://etherpad.opendev.org/p/2024.2-leaderless#L72 -gmann

1 1

[magnum][magnum-cluster-api] Scalling Master Node
by pahrialtkj＠gmail.com 10 May '24

10 May '24

Hello all, I created a k8s cluster with 1 master and 1 worker node, I want to increase the master node to 2 or 3, I tried to do it with cluster resize/update and nodegroup create seems to be not supported and does not work, it works for the worker node, has anyone tried scaling the master node?

3 3