- openstack-discuss - lists.openstack.org

[elections][ptl][keystone] Stepping down as PTL
by Dave Wilde 17 Feb '25

17 Feb '25

Hello, Due to a recent change in my career path I’ve come to the difficult decision that I need to step down as the Keystone PTL. Over the past 4 years as the PTL the Keystone project has really come a long way, from the establishment of reviewathons and an engaged team of core reviewers to the implementation of some long sought after features and a clean up and modernization of the codebase. This is all due to some very dedicated folks and I’ld like to pass on my personal thanks to them for all of the hard work. Keystone is at a very interesting point in it’s history and I think the future holds bright things for the project, I would like to still be involved but due to the time constraints of my new position I no longer have the bandwidth to manage the day to day aspects of such a large project. I’m looking forward to helping whoever takes the reins in whatever ways that I can. Thanks again, it’s been a pleasure. /Dave

1 0

[blazar][elections][ptl] Leaving the PTL role
by Pierre Riteau 17 Feb '25

17 Feb '25

Hello Blazar community, Having been Blazar PTL since the Stein cycle, it is time to pass the torch to someone else. I would be happy to help the new PTL with their duties, especially during their first cycle. I will stay involved in the community anyway. Cheers, Pierre Riteau (priteau)

1 0

[neutron] Bug deputy report (week starting on February 10)
by Elvira Garcia Ruiz 17 Feb '25

17 Feb '25

Hi folks! Here you have the list of bugs reported for Neutron during last week (10 Feb - 16 Feb). There is one Undecided bug because I'm unsure on how to prioritize it, so we can discuss it at tomorrow's meeting if that is ok. Critical --------- - https://review.opendev.org/c/openstack/neutron/+/941511 Regular user can modify router SNAT flag Fix proposed by Rodolfo: https://review.opendev.org/c/openstack/neutron/+/941511. Rodolfo noted this might need more than just this patch. High ------ - https://bugs.launchpad.net/neutron/+bug/2098085 SRIOV mechanism driver may attach to the wrong segment where a host has access to multiple segments of the same network Assigned to Andrew Bonney Incomplete --------------- - https://bugs.launchpad.net/neutron/+bug/2097747 neutron not update ovn routers Undecided --------------- - https://bugs.launchpad.net/neutron/+bug/2098621 ports can attempt to bind to the wrong segment Best regards, Elvira

1 0

[all][elections][ptl][tc] Combined PTL/TC 2025.2 cycle Election Nominations Last Days
by Sławek Kapłoński 17 Feb '25

17 Feb '25

Hi, A quick reminder that we are in the last hours for declaring PTL and TC candidacies. Nominations are open until Feb 19, 2025 23:45 UTC. If you want to stand for election, don't delay, follow the instructions at[1] to make sure the community knows your intentions. Make sure your nomination has been submitted to the openstack/election repository and approved by election officials. All members of the community are encouraged to confirm their email address and opt in to the CIVS election as described at: https://governance.openstack.org/election/#electorate Election statistics[2]: Nominations started @ 2025-02-05 23:45:00 UTC Nominations end @ 2025-02-19 23:45:00 UTC Nominations duration : 14 days, 0:00:00 Nominations remaining : 2 days, 13:41:25 Nominations progress : 81.64% --------------------------------------------------- Projects[1] : 40 Projects with candidates : 15 ( 37.50%) Projects with election : 0 ( 0.00%) --------------------------------------------------- Need election : 0 () Need appointment : 25 (Barbican Blazar Cinder Cloudkitty Glance Heat Ironic Keystone Manila Masakari Monasca Octavia OpenStackAnsible OpenStackSDK OpenStack_Charms Oslo Puppet_OpenStack Quality_Assurance Storlet s Sunbeam Swift Tacker Telemetry Vitrage Zaqar) --------------------------------------------------- TC Candidates : 1 (5 Required) =================================================== Stats gathered @ 2025-02-17 10:03:35 UTC This means that with approximately 2 days left, 25 projects will be deemed leaderless. In this case the TC will oversee PTL selection as described by [3]. Thank you, [1] https://governance.openstack.org/election/#how-to-submit-a-candidacy [2] Any open reviews at https://review.opendev.org/q/project:openstack/election+is:open+file:candid… have not been factored into these stats. [3] https://governance.openstack.org/resolutions/20141128-elections-process-for… -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0

[cinder] Support for Portworx
by Waines, Greg 16 Feb '25

16 Feb '25

Does anyone know how to use a https://portworx.com/ kubernetes-based storage solution as the storage backend for Cinder ? There is a Pure Storage driver listed in https://docs.openstack.org/cinder/latest/configuration/block-storage/volume… . https://docs.openstack.org/cinder/latest/configuration/block-storage/driver… BUT I do NOT believe this is the correct driver for interfacing with an https://portworx.com/ storage cluster. AND Neither the portworx documentation site ( https://docs.portworx.com/ ) nor the portworx github ( https://github.com/portworx ) have any information about integration with Cinder or OpenStack. ( ... although I believe it used to ... ) any info would be appreciated, Greg.

2 2

[tc][all][monasca ] Retiring the Monasca project
by Ghanshyam Mann 16 Feb '25

16 Feb '25

Hello everyone, As you might know, the Monasca 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 Monasca 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

6 17

[kolla-ansible]how to set ovn_cms_opts in non gateway chassis
by Satish Patel 15 Feb '25

15 Feb '25

Folks, I have 3 controller nodes and they are gateway nodes also but now I want to add 2 more compute nodes who will have the following flag to handle external port traffic to reply to DHCP for sriov nodes. $ ovs-vsctl set open_vswitch . external_ids:ovn-cms-options="enable-chassis-as-extport-host" How and where do I tell kolla-ansible to put the above option for those 2 new compute nodes so options will survive re-deployment.

2 2

[ironic][nova] deploying VMware ESXi
by Doug Goldstein 14 Feb '25

14 Feb '25

Hello all, I’ve got a need to boot bare metal machines with VMware ESXi. ESXi 7 and newer is resistant to an image that can be reused like other OS images are used from Nova. As I mentioned it’s a bare metal machine so I’m working with Ironic but ultimately looking to drive this via Nova (through the Ironic hypervisor backend). Coming up empty in my Google-fu for an example of someone doing this so I figured I’d crowd source asking the ML. Right now I’m able to get an ISO of a system and it’s using VMware’s “weasel” installer which appears to be a fork/related to Anaconda and using Kickstart. Ironic supports an Anaconda deploy mechanism but the files are different and so it won’t just work out of the box (there is no stage2 but instead like 80 individual files) so my plan is to make a “weasel” deploy mechanism for Ironic. But just wanted to see if someone had any better approaches or ideas before I plod forward. Thanks. — Doug

1 0

[release] Release countdown for week R-6, Feb 17 - 21
by Elõd Illés 14 Feb '25

14 Feb '25

Development Focus ----------------- Work on libraries should be wrapping up, in preparation for the various library-related deadlines coming up. Now is a good time to make decisions on deferring feature work to the next development cycle in order to be able to focus on finishing already-started feature work. General Information ------------------- We are now getting close to the end of the cycle, and will be gradually freezing feature work on the various deliverables that make up the OpenStack release. This coming week is the deadline for general libraries (except client libraries): their last feature release needs to happen before "Non-client library freeze" on February 20th, 2025. Only bugfixes releases will be allowed beyond this point. When requesting those library releases, you can also include the stable/2025.1 branching request with the review (as an example, see the "branches" section here: https://opendev.org/openstack/releases/src/branch/master/deliverables/pike/… In the next weeks we will have deadlines for: * Client libraries (think python-*client libraries), which need to have their last feature release before "Client library freeze" (February 27th, 2025) * Deliverables following a cycle-with-rc model (that would be most services), which observe a Feature freeze on that same date, February 27th, 2025. Any feature addition beyond that date should be discussed on the mailing-list and get PTL approval. As we are getting to the point of creating stable/2025.1 branches, this would be a good point for teams to review membership in their $project-stable-maint groups. Once the stable/2025.1 branches are cut for a repo, the ability to approve any necessary backports into those branches for 2025.1 Epoxy will be limited to the members of that stable team. If there are any questions about stable policy or stable team membership, please reach out in the #openstack-stable channel. Upcoming Deadlines & Dates -------------------------- Non-client library freeze: February 20th, 2025 (R-6 week) Client library freeze: February 27th, 2025 (R-5 week) Epoxy-3 milestone: February 27th, 2025 (R-5 week) Cycle Highlights Due: March 6th, 2025 (R-4 week) 2025.1 Epoxy final release: April 2nd, 2025 Project Teams Gathering (virtual): April 7th-11th, 2025 Előd Illés irc: elodilles @ #openstack-release

1 0

[charms][elections][ptl] PTL non-candidacy
by James Page 14 Feb '25

14 Feb '25

Hi OpenStack Charmers Due to some changes in my focus I won't be standing as PTL for the OpenStack Charms project for the upcoming cycle. Thanks James

1 0

[neutron] Drivers meeting agenda for Friday, February 14th
by Brian Haley 13 Feb '25

13 Feb '25

Hello Neutrinos: Sorry for the late notice but this is the agenda for tomorrow's drivers meeting: * Router PUT behavior discussion: - https://review.opendev.org/c/openstack/neutron/+/941511 - https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/941545 Not an RFE, but something Rodolfo wanted to talk about based on a recent bug. See you then, -Brian

2 1

[Neutron] Router external GW info policies bug
by Rodolfo Alonso Hernandez 13 Feb '25

13 Feb '25

Hello all: Yesterday I opened a bug because of an issue in the router's external GW info policies: https://bugs.launchpad.net/neutron/+bug/2098109. At the end of the day I found that the issue is more complicated than the trivial fixes I proposed. NOTE: I've reverted two backports of a patch that was not merged in master branch. I've also -W the patches proposed. I would like you to read https://bugs.launchpad.net/neutron/+bug/2098109/comments/11, that describes the current issue. Today I'm going to propose several patches to fix that problem, first in n-lib to fix the definitions and then in Neutron, to implement the needed policies for these new actions and their sub-attributes. Please don't hesitate to ping me in IRC for more info. @Brian Haley <haleyb.dev(a)gmail.com> I don't think it will be needed to add this topic to the drivers meeting. I think I've better described it in the bug comment and we can continue any discussion offline. So I think we can remove the section you added; it will be better to "digest" this info reading the bug and commenting async in IRC. Regards.

1 0

[nova] How to gain approval for a new feature on unavailable hardware
by taketani.ryo＠fujitsu.com 13 Feb '25

13 Feb '25

To Whom It May Concern, We are considering to propose and develop a new feature on OpenStack Nova for building Arm Confidential Computing Architecture (Arm CCA)-encrypted instances. I have some questions for doing it. * While specification of Arm CCA is already open(https://developer.arm.com/documentation/den0125/0300/Overview), No Arm CCA-enabled hardware is currently available to our knowledge. Therefore, we plan to conduct testing in an internal environment. * Would a proposal for a feature utilizing publicly unavailable hardware be acceptable to OpenStack? Alternatively, in this case, what steps or preparations are required for approval? * Should the blueprint and specification be submitted simultaneously? * The specification is currently incomplete. Building Arm CCA instances requires libvirt APIs, similar to AMD SEV instances(https://blueprints.launchpad.net/nova/+spec/amd-sev-libvirt-suppo…, but specification of these are not yet determined publicly. We are considering submitting the blueprint first to inform the community of our ongoing development efforts. Regards

3 6

#eventlet-removal Meeting canceled - Feb 18
by Herve Beraud 13 Feb '25

13 Feb '25

Hey folks, The coming meeting (Feb 18) is canceled. The next meeting will be on March 04. For more details about meetings: - https://etherpad.opendev.org/p/epoxy-eventlet-tracking - https://wiki.openstack.org/wiki/Eventlet-removal#Recurring_Events Thanks for your attention. -- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/

1 0

[ironic][elections][ptl] Leaving the PTL role
by Riccardo Pittau 13 Feb '25

13 Feb '25

Hello ironicers! It's been a pleasure and an honor to serve as PTL for 2 cycles. I've decided to not be a candidate for the next cycle, mainly because of time constraints. Huge thanks to the community for having me, I hope in the future I'll be able to repeat the experience. Ciao! Riccardo #irc rpittau

9 18

[manila] Postpone Removal of Standalone CephFS NFS helper
by Ashley Rodriguez 12 Feb '25

12 Feb '25

Hi all! As per subject line, after some discussions on this mailing list and during our mid-cycle review, we have decided to postpone the deprecation of the standalone CephFS NFS protocol helper in Epoxy. This gives administrators a little more time to migrate to the ceph-orch-deployed clustered NFS service, at least until the next SLURP Release AKA "G" cycle. In the meantime, we will continue to maintain the associated CI for standalone NFS-Ganesha as best we can. Please understand that our focus is on clustered deployments, and we welcome any assistance offered. To assist migration, admins can configure "cephfs_ganesha_export_ips" (or alternatively, "cephfs_ganesha_server_ip") alongside the required "cephfs_nfs_cluster_id". Setting these options will allow the CephFS driver to report additional export paths. These additional export paths will have the "preferred" export location metadata key set to False. We encourage folks interested to join us at the "All things CephFS" discussion during the upcoming PTG within the Manila room. Details regarding the exact scheduling will be shared closer to the event. Best, Manila Team

1 0

[all] [diversity] Looking for sponsors for Outreachy 2025
by Dmitry Tantsur 12 Feb '25

12 Feb '25

Hi folks, As some of you might have noticed, OpenStack did not participate in the December 2024 cohort of Outreachy (a DEI program providing paid internships to people from underrepresented or discriminated groups). This was because we could not find anyone to sponsor our participation. It looks like the situation might not improve at all in 2025. If so, I think it will be over for OpenStack in Outreachy. I'd like to ask companies developing or using OpenStack and caring about DEI to step in. We're talking about $8000 per intern, more details in https://www.outreachy.org/docs/community/#intern-funding. OpenStack had been very active in Outreachy before the last round. You can check it for yourself by searching for "OpenStack" on https://www.outreachy.org/alums/2024-05/ and the previous rounds. I'd like to keep it this way. Can we do it together? Please reach out to Mahati and me if you can help. Thank you! Dmitry

4 5

[nova][elections][ptl] Application for the PTL role
by René Ribaud 12 Feb '25

12 Feb '25

Hello, I would like to run for the PTL election for Nova and Placement. I am fortunate to be employed by Red Hat to work on this project, and I have been doing so for about three years. This means I am quite familiar with the project's processes and codebase, though I wouldn’t call myself an expert. To be honest, I initially thought of becoming a core member before running for this election. However, knowing that Sylvain wants to step down, and after discussing it with him and other members of the community, I realized that becoming PTL, while challenging, is a viable path and a great opportunity. I know this role will push me out of my comfort zone and require me to work on areas where I have less experience. But I believe that sometimes, growth comes from facing new challenges. So, I took a deep breath and decided to write this message. Regarding the future of the project, my goal is not to revolutionize anything. I believe I will need some time to find my footing, and I will do my best to continue in the direction that Sylvain has set. It won’t always be easy, but I trust in the kindness of those involved in this project to support me. I also rely on Sylvain’s mentoring, as he proposed during his candidacy, to ensure a smooth transition. One aspect I intend to be particularly mindful of is supporting contributors in getting their code merged. Having recently merged a major feature (virtiofs) that I carried for a long time, I know how difficult and demanding the process can be—it requires a lot of resilience. That’s why I'll pay attention to making this process smoother and support contributors as effectively as I can. Thanks, René

5 6

cinder volumes
by engineer2024 12 Feb '25

12 Feb '25

Is there a feature in openstack as of now, where we can specify an option while vm creation, which suggests the cinder to automatically use from the pool of available volumes for that project, instead of creating new volumes ? As of now, we need to explicitly specify a volume id to be attached to the vm after creation.. Thanks elinux

2 1

[Glance]Cancelling Weekly Meeting (Feb 13)
by Mridula Joshi 11 Feb '25

11 Feb '25

Hello, Cancelling this week's weekly meeting, As most of the members are not around. Thanks, Mridula Joshi

1 0

openstack instances unable to reach the internet
by collinl＠churchofjesuschrist.org 11 Feb '25

11 Feb '25

I have been banging my head on this issue for quite some time now. I am hoping that somebody can help me see what I have misconfigured. Here is the situation. I have tried setting up several openstack installs, and in none of them am I able to reach the internet from the instances running inside of openstack. All of them are on Rocky Linux 9.5, running the dalmatian version of openstack, installed using packstack. (I have tried an all-in-one, with everything on a single node, and a cluster with the controller/networking on one node, and the compute running on separate nodes). I can get the cirros instances running on the backend network within openstack, and can ssh to them via the floating ip from the host without issues. The cirros instance can ping other cirros instances in the openstack controlled network (both on the backend network(subnet is in the 192.168.100.0/24 range, or on the external public network(subnet is in the 172.24.4.024 range) Even trying the simplest configuration, where everything is all on a single node (compute/networking/controller/etc), Everything from instance creation to VM migration/etc all seems to work just fine. However, the cirros instances cannot ping anything on the internet -- for example, I am unable to ping 8.8.8.8 or even the gateway that the host can reach (The host has an ip used to reach horizon on the 10.61.157.0/24 subnet on our internal lan) I can ping all interfaces from the cirros interface through the backend_network (192.168.100.0/24) through the public interface (172.24.4.0/24), and can even ping the host ip address (10.61.157.59) . . .However, I can't ping anything beyond that (i.e. the 10.61.147.1 gateway does not ping from the cirros instance) From the host commandline, it is able to reach everything external just fine (i.e. it can ping it's gateway 10.61.147.1 and 8.8.8.8 or anything else external) Here is the ip addr output from the host: 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master ovs-system state UP group default qlen 1000 link/ether 00:1d:d8:b7:1e:df brd ff:ff:ff:ff:ff:ff inet6 fe80::21d:d8ff:feb7:1edf/64 scope link valid_lft forever preferred_lft forever 3: ovs-system: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 56:d8:51:53:10:b0 brd ff:ff:ff:ff:ff:ff 4: br-int: <BROADCAST,MULTICAST> mtu 1442 qdisc noop state DOWN group default qlen 1000 link/ether 62:8c:b0:c2:3e:5a brd ff:ff:ff:ff:ff:ff 5: br-ex: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000 link/ether 00:1d:d8:b7:1e:df brd ff:ff:ff:ff:ff:ff inet 10.61.157.59/24 brd 10.61.157.255 scope global br-ex valid_lft forever preferred_lft forever inet 172.24.4.1/24 brd 172.24.4.255 scope global br-ex valid_lft forever preferred_lft forever inet6 fe80::2446:29ff:fe58:6541/64 scope link valid_lft forever preferred_lft forever 6: tapeffe7cc1-56: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1442 qdisc noqueue master ovs-system state UNKNOWN group default qlen 1000 link/ether fe:16:3e:e2:66:5d brd ff:ff:ff:ff:ff:ff inet6 fe80::fc16:3eff:fee2:665d/64 scope link valid_lft forever preferred_lft forever 7: tap65170f1f-e0@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master ovs-system state UP group default qlen 1000 link/ether 3a:26:09:cf:3d:4f brd ff:ff:ff:ff:ff:ff link-netns ovnmeta-65170f1f-e837-4b5e-a471-13e783e6b48e inet6 fe80::3826:9ff:fecf:3d4f/64 scope link valid_lft forever preferred_lft forever And the output from the ovs-vsctl show command: 46294eda-8a39-4775-875d-ef6ec9929346 Manager "ptcp:6640:127.0.0.1" is_connected: true Bridge br-int fail_mode: secure datapath_type: system Port tap65170f1f-e0 Interface tap65170f1f-e0 Port patch-br-int-to-provnet-371bdb7c-d2f3-4e70-aca9-1c4838c57e24 Interface patch-br-int-to-provnet-371bdb7c-d2f3-4e70-aca9-1c4838c57e24 type: patch options: {peer=patch-provnet-371bdb7c-d2f3-4e70-aca9-1c4838c57e24-to-br-int} Port tapeffe7cc1-56 Interface tapeffe7cc1-56 Port br-int Interface br-int type: internal Bridge br-ex fail_mode: standalone Port patch-provnet-371bdb7c-d2f3-4e70-aca9-1c4838c57e24-to-br-int Interface patch-provnet-371bdb7c-d2f3-4e70-aca9-1c4838c57e24-to-br-int type: patch options: {peer=patch-br-int-to-provnet-371bdb7c-d2f3-4e70-aca9-1c4838c57e24} Port br-ex Interface br-ex type: internal Port eth0 Interface eth0 ovs_version: "3.3.1" Here is the info for the networks/subnets currently configured: From "openstack network list --long" +------------------------+-----------------+--------+------------------------+-------+--------+------------------------+--------------+-------------+--------------------+------+ | ID | Name | Status | Project | State | Shared | Subnets | Network Type | Router Type | Availability Zones | Tags | +------------------------+-----------------+--------+------------------------+-------+--------+------------------------+--------------+-------------+--------------------+------+ | 65170f1f-e837-4b5e-a47 | backend_network | ACTIVE | c5f408c4daed4fb2afefa4 | UP | False | b1e5aef4-77da-4b0b-9b9 | geneve | Internal | | | | 1-13e783e6b48e | | | 4fa039fe26 | | | 4-5aaf395484e0 | | | | | | b8e7a305-65f0-44ea-93a | public | ACTIVE | c5f408c4daed4fb2afefa4 | UP | False | 6cff8f70-9dc8-4f17-b78 | flat | External | | | | a-cc6ec741d408 | | | 4fa039fe26 | | | 0-32cf2aedb017 | | | | | | c0c67da4-22bf-4dd2-b4c | private | ACTIVE | 2967b1fe70794fa88cbb3d | UP | False | caed16ae-22ff-427a-a37 | geneve | Internal | | | | 2-2edcb41ffb97 | | | e7227cec77 | | | 0-6b891755bfa7 | | | | | +------------------------+-----------------+--------+------------------------+-------+--------+------------------------+--------------+-------------+--------------------+------+ From "openstack subnet list --long" +---------------+---------------+---------------+---------------+---------------+-------+--------------+------------------+-------------+------------+---------------+---------------+------+ | ID | Name | Network | Subnet | Project | DHCP | Name Servers | Allocation Pools | Host Routes | IP Version | Gateway | Service Types | Tags | +---------------+---------------+---------------+---------------+---------------+-------+--------------+------------------+-------------+------------+---------------+---------------+------+ | 6cff8f70-9dc8 | public_subnet | b8e7a305-65f0 | 172.24.4.0/24 | c5f408c4daed4 | False | | 172.24.4.2-172.2 | | 4 | 172.24.4.1 | | | | -4f17-b780-32 | | -44ea-93aa- | | fb2afefa44fa0 | | | 4.4.254 | | | | | | | cf2aedb017 | | cc6ec741d408 | | 39fe26 | | | | | | | | | | b1e5aef4-77da | backend_subne | 65170f1f-e837 | 192.168.100.0 | c5f408c4daed4 | True | | 192.168.100.100- | | 4 | 192.168.100.1 | | | | -4b0b-9b94-5a | t | -4b5e-a471-13 | /24 | fb2afefa44fa0 | | | 192.168.100.250 | | | | | | | af395484e0 | | e783e6b48e | | 39fe26 | | | | | | | | | | caed16ae-22ff | private_subne | c0c67da4-22bf | 10.0.0.0/24 | 2967b1fe70794 | True | | 10.0.0.2-10.0.0. | | 4 | 10.0.0.1 | | | | -427a-a370-6b | t | -4dd2-b4c2-2e | | fa88cbb3de722 | | | 254 | | | | | | | 891755bfa7 | | dcb41ffb97 | | 7cec77 | | | | | | | | | +---------------+---------------+---------------+---------------+---------------+-------+--------------+------------------+-------------+------------+---------------+---------------+------+ From "openstack floating ip list" +------------------------------------+---------------------+------------------+------------------------------------+------------------------------------+----------------------------------+ | ID | Floating IP Address | Fixed IP Address | Port | Floating Network | Project | +------------------------------------+---------------------+------------------+------------------------------------+------------------------------------+----------------------------------+ | 61d98a1c-f19a-451f-9353-6cb8305a0c | 172.24.4.175 | 192.168.100.128 | effe7cc1-566d-4574-b4e3-d9f440b776 | b8e7a305-65f0-44ea-93aa- | c5f408c4daed4fb2afefa44fa039fe26 | | 2f | | | 5e | cc6ec741d408 | | +------------------------------------+---------------------+------------------+------------------------------------+------------------------------------+----------------------------------+ From "openstack server list" +--------------------------------------+-------+--------+-----------------------------------------------+--------------------------+---------+ | ID | Name | Status | Networks | Image | Flavor | +--------------------------------------+-------+--------+-----------------------------------------------+--------------------------+---------+ | e42372d2-946d-4c90-bf2d-1e36cda80e2f | test3 | ACTIVE | backend_network=172.24.4.175, 192.168.100.128 | N/A (booted from volume) | m1.tiny | +--------------------------------------+-------+--------+-----------------------------------------------+--------------------------+---------+ Any assistance in helping me figure out what I am missing to get external access would be greatly appreciated. Thank you!

4 14

Flat openstack network
by Mateusz Woźniakowski 11 Feb '25

11 Feb '25

Good day, I have a question, how to configure neutron in openstack kolla, so as not to make a vrouter but to make a flat network and pass vlans to openstack and make a public network directly in openstack kolla. at the moment I have it on vrouter but it is not a good solution for me. and I would need to set up several networks in openstack Could someone suggest where to find it and how to set it up?

2 3

Building kolla-ansible in china region
by Satish Patel 11 Feb '25

11 Feb '25

Folks, I am trying to build kolla-ansible in China but somehow my docker repository not accessible. I understand geo location and the great firewall. Does anyone know if there is any local china repo or docker hub which I can use in that region to build the openstack. # docker run -d --network host --name registry --restart=always -e REGISTRY_HTTP_ADDR=0.0.0.0:4000 -v registry:/var/lib/registry registry:2 Unable to find image 'registry:2' locally docker: Error response from daemon: Get "https://registry-1.docker.io/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers). See 'docker run --help'.

4 4

[kolla-ansible] why swift deployment support has been deprecated for removal in 2025.2?
by Sara khosravi 11 Feb '25

11 Feb '25

Hello everyone, I’m new to Kolla-Ansible. I have used Swift with a simple Ansible playbook and have tested with GitLab CI. But now I’m following the CI/CD procedures in Kolla-Ansible. I’m trying to understand why swift deployment support has been deprecated for removal in 2025.2. I’m having trouble finding the exact failure points in the CI pipeline related to the Swift role, and I can’t seem to find any clues about failures that occurred in the CI process. I really appreciate any help you can provide.

2 1

Re:[skyline-console] Issue with Skyline Console in Dalmatian Version of OpenStack
by 文相吴 11 Feb '25

11 Feb '25

Hello, Please check if cinder service_type == block-storage or volumev3 in your environment. If your cinder service_type == block-storage, adding a volumev3 service_type & related endpoints, to check if it works. If yes, that is a bug, will fix in soon. Thanks Best Regrads Wu Wenxiang Original: From：zhang.jingwei(a)99cloud.net<zhang.jingwei(a)99cloud.net> Date：2025-02-06 09:50:15(中国 (GMT+08:00)) To：shubham.kumar.yadav369<shubham.kumar.yadav369(a)gmail.com> Cc：wu.wenxiang<wu.wenxiang(a)99cloud.net> , zhu.boxiang<zhu.boxiang(a)99cloud.net> Subject：Re: Re:[skyline-console] Issue with Skyline Console in Dalmatian Version of OpenStack We are preparing the environment you mentioned. After the environment is ready, we will check the corresponding problems and give you feedback in time. Dalmation version nova-manage version 30.0.1 cinder-manage version list 25.0.0 Best Regrads Zhang Jingwei From: 吴文相 Date: 2025-02-04 10:18 To: Shubham Kumar Yadav CC: 张菁WEI; 朱博祥 Subject: Re:[skyline-console] Issue with Skyline Console in Dalmatian Version of OpenStack Sorry for late，we are in Chinese New Year vacation(Spring Festival)，will back in 1 week Thanks Best Regrads Wu Wenxiang Original: From: Shubham Kumar Yadav<shubham.kumar.yadav369(a)gmail.com> Date: 2025-01-22 18:26:46 To: OpenStack Discuss <openstack-discuss(a)lists.openstack.org> Subject: [skyline-console] Issue with Skyline Console in Dalmatian Version of OpenStack Dear Support Team, I hope this message finds you well. I am reaching out to report an issue I am experiencing with the Skyline console in the Dalmatian version of OpenStack. Issue Description: I am unable to list volumes and instances, as well as access volume-related services like Manila. This functionality is critical for my operations. Version Details: I have successfully set up the Skyline console for the Zed version of OpenStack, where everything is functioning as expected. However, the same cannot be said for the Dalmatian version. Troubleshooting Steps Taken: I have checked the service status and confirmed that all necessary services are running. I have attempted to refresh the console and clear the cache, but the issue persists. Request for Assistance: I would appreciate any guidance or troubleshooting steps you could provide to resolve this issue. If there are any logs or additional information you need from my end, please let me know. Also im using same image for both the openstack version - 99cloud/skyline:latest These are the versions of nova-api & cinder-api Zed version nova-manage version 26.2.2 cinder-manage version list 21.1.0 Dalmation version nova-manage version 30.0.1 cinder-manage version list 25.0.0 Thank you for your attention to this matter. I look forward to your prompt response. Best regards, Shubham

1 0