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

Practical workshop labs for Meetups?
by Julia Kreger 19 Mar '24

19 Mar '24

Hey folks, Yesterday, I took part in the Los Angeles OpenInfra meetup, and a question that came up from some of the organizers was if there are any practical workshop labs we can walk folks through to sort of show some practical/concrete usage aspects of OpenStack? Is anyone aware of any such materials? I ask because we are talking of trying to organize the next meetup in more a workshop style, especially as some participants did also express interest in hands on learning. Thanks in advance, -Julia

6 7

[aodh][ec2-api][sahara][trove][vitrage][watcher] autocommit was (again) removed from LegacyEngineFacade
by Takashi Kajinami 19 Mar '24

19 Mar '24

Hello, Please be aware that LegacyEngineFacade in the latest oslo db release for caracal no longer enables autocommit[1]. Removal was attempted in the previous release, as part of the overall efforts to adapt to sqlalchemy 2.0, but later reverted[2] because multiple projects need more time to adapt to the change. Now the removal is again proposed for caracal and the version currently listed in upper constraints no longer provides that functionality. Quickly searching the current usage by hound, it seems the project listed in this mail title still contains autocommit=True in LegacyEngineFacade, and is likely broken by the change. I'd suggest checking CI status to evaluate the impact. Note 1: The list may be incomplete Note 2: It seems aodh is not actually relying on autocommit and the removal might not be affecting it [1] https://review.opendev.org/c/openstack/oslo.db/+/875986 [2] https://review.opendev.org/c/openstack/oslo.db/+/895631 Thank you, Takashi -- Takashi Kajinami irc: tkajinam github: https://github.com/kajinamit launchpad: https://launchpad.net/~kajinamit

3 4

[horizon] Dalmatian Virtual PTG Schedule
by Tatiana Ovchinnikova 19 Mar '24

19 Mar '24

Hello team! Here's the etherpad for Horizon Dalmatian Virtual PTG: https://etherpad.opendev.org/p/horizon-dalmatian-ptg Feel free to add the topics you want to discuss! Our time slots for the PTG are: Tuesday, April 9, 14 UTC - 16 UTC, room havana Wednesday, April 10, 16 UTC - 17 UTC, room havana The detailed schedule is in the etherpad. Don't forget to register for PTG, if not done yet: https://openinfra.dev/ptg/ See you at the PTG! Regards, Tatiana Ovchinnikova (IRC: tmazur)

1 0

Use Openstack SDK for Swift
by Albert Braden 19 Mar '24

19 Mar '24

I'm writing a script that will use admin credentials to check user projects for containers. I'm already doing something similar for non-swift accounts, doing things like: cloud.network.networks(project_id=projectid): I read here about the Object SDK: https://docs.openstack.org/openstacksdk/latest/user/guides/object_store.html And I tried this: cloud.object_store.containers(project_id=projectid): But I get an error: Invalid query params: project_id I read the Object SDK document here and it doesn't seem to say anything about how to specify a project: https://docs.openstack.org/openstacksdk/latest/user/proxies/object_store.ht… But when I read the Swift API document, I see that I can use "/v1/{account}/{container}", so I'm guessing that there must be a way to do it via the SDK. https://docs.openstack.org/api-ref/object-store/#show-container-details-and… Is it possible to specify the project in an Object SDK call, or do I need to use the old python API for this?

2 2

[NEUTRON] Separating network with Neutron AZ
by Nguyễn Hữu Khôi 19 Mar '24

19 Mar '24

Hello. I am looking for an option to map instances to network which has same az with compute resource. It will look like [cinder]cross_az_attach = False It will be nice if we decide to run edge site Could you tell me that we will have a road map to do it? Thank you. Nguyen Huu Khoi

1 0

Tacker REST API Authentication
by Ravichandran Venkataraman (veravich) 19 Mar '24

19 Mar '24

Hi, Is it possible to use username/password for authentication of Tacker REST API calls? In the tacker.conf, I see both BASIC and OAUTH2 methods for authentication. If I set the auth_type to BASIC and configure the user_name and password values, will I be able to make the REST calls with these username and password? Thanks and regards, Ravichandran

2 3

Yoga Magnum: csi-cinder-controllerplugin-0 fails to initialize properly because of obsolete API
by Michel Jouvin 19 Mar '24

19 Mar '24

Hi, We recently upgraded our cluster to Yoga and since then we cannot successfully start pods in clusters using K8s 1.23 that require a volume. The volume is properly created but attachment fails because it is trying to use v1beta1.CSINode and v1beta1.VolumeAttachment that no longer exists. I found a reference to this in https://github.com/kubernetes/cloud-provider-openstack/issues/1845 but the way to fix it is unclear. I tried to use last version of CSI-related stuff from registry.k8s.io (playing with labels and source), but I then got another problem which may be related (it is my guess) to the fact that I'm using too recent versions. Is somebody using sucessfully Magnum Yoga/K8bs 1.23 combination sucessfully and what is the trick to do it? Thanks in advance for any help. Best regards, Michel

3 12

[skyline] Running a Skyline in "subdirectory"
by Dmitriy Rabotyagov 19 Mar '24

19 Mar '24

Hey folks, I was looking into a way to make both Horizon and Skyline work at the same time, and found out that I'm not really able to make Skyline to run in sub-URL. So for instance the plan was to place Horizon under /horizon (which is easily doable) and then Skyline under /skyline. However so far I haven't found any setting or anything that would allow me to do so. Basically, I've realized that static content is _really_ static, which means it does have hardcoded URIs: https://opendev.org/openstack/skyline-console/src/branch/master/skyline_con… So either I'm just not realizing the very simple technique which allows to overcome hardcoded in static files URIs (like some rewrite?), or just serving Skyline from a subdirectory is not possible by design... Would be great if someone could share their experience about Skyline and if anyone managed to do what I'm looking for. Thanks in advance

2 1

[Freezer] Is Freezer dead?
by pi3.14＠tuta.io 19 Mar '24

19 Mar '24

Hi folks, is Freezer still supported? I don't see any real development going on with it. Is it recommended to use in a production Cloud environment? Are there other free and open source alternatives to Freezer? Thanks Roby

8 19

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

18 Mar '24

Hi everyone, This Wednesday (March 20th) 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 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

[manila] Docs bugsquash: March 19th - 22nd
by Carlos Silva 18 Mar '24

18 Mar '24

Hello, Zorillas! As mentioned in last week's meeting, we are having a bugsquash/hack-a-thon focused on reducing our documentation backlog. I have created an ethercalc with some of the bugs we intend to work on [1]. - We will have the kick-off meeting on March 19th, 15 UTC and we will use meetpad [2] - We will use the Manila upstream meeting slot (March 21st, 15 UTC) as a checkpoint. In case you are planning to join and the bug you intend to work on is not in the ethercalc, please add it. [1] https://ethercalc.net/c9z5705xdeui [2] https://meetpad.opendev.org/ManilaCaracalBugsquash Looking forward to closing some docs bugs with you! Regards, carloss

1 0

[tc] Next Meeting Tomorrow, Tues March 19, 1800 UTC
by Jay Faulkner 18 Mar '24

18 Mar '24

Hi all, The next meeting of the Technical Committee is tomorrow, March 19, at 1800 UTC in #openstack-tc in OFTC. The proposed agenda is: Agenda - Roll call - Follow up on tracked action items - Gate health check - Implementation of Unmaintained branch statuses - 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 Thank you, Jay Faulkner OpenStack TC Chair

1 0

Survey to schedule i18n SIG 2024.04 PTG
by Seongsoo Cho 18 Mar '24

18 Mar '24

Hi i18n SIG I create a survey to schedule i18n SIG 2024.04 PTG. Please let me know, what time and day works best for you. survey: https://framadate.org/tY49ETqtFD9R4LPt Best Regards Seongsoo -- Seongsoo Cho OpenStack Korea User Group / Community Leader IRC #seongsoocho

1 0

[kolla-ansible][2023.2] Need some information about using let's encrypt
by wodel youchi 18 Mar '24

18 Mar '24

Hi, I deployed openstack using a self-signed certificate generated by kolla. I am using the encryption both internally and externally. Then I tried to use let's encrypt on the same platform, and it seemed to work, but only on the external URL of openstack (horizon portal). Then I undeployed my openstack, and I tried to redeploy it again, this time Keystone couldn't be deployed, it complained about not being able to verify the self-signed certificate. I had to disable the let's encrypt lines on the globals.yml to be able to deploy openstack. My question is : - Does using let's encrypt cover both internal and external traffic of openstack on all ports or just the 443? - If it does, how to configure globals.yml , especially the lines concerning the certificates? - If it does not, it covers only Horizon on 443, how could someone combine the use of self-signed to let's encrypt use? is it even possible? Regards.

2 3

[Kolla-ansible][Trove][2023.2] Unable to create datastore when using self-signed certificate
by wodel youchi 18 Mar '24

18 Mar '24

Hi, I am trying to complete trove configuration, by creating a datastore. I am using a self-signed certificate in my deployment. When trying to create a datastore I got : ble but deprecated behaviour. Please set this to True. 2024-03-18 12:26:20.245 35 WARNING keystonemiddleware.auth_token [-] AuthToken middleware is set with keystone_authtoken.service_token_roles_required set to False. This is backwards compatible but deprecated behaviour. Please set this to True. 2024-03-18 12:26:20.249 35 WARNING keystonemiddleware.auth_token [-] Using the in-process token cache is deprecated as of the 4.2.0 release and may be removed in the 5.0.0 release or the 'O' development cycle. The in-process cache causes inconsistent results and high memory usage. When the feature is removed the auth_token middleware will not cache tokens by default which may result in performance issues. It is recommended to use memcache for the auth_token token cache by setting the memcached_servers option. 2024-03-18 12:26:20.685 35 INFO trove.extensions.mgmt.datastores.service [None req-ef8a2f03-8500-40e0-88fe-4fac6ac5c9cb 85c09dd86fc846f98c3b4add7f64d76f 54589053b612438ab9c4d3f800c75000 - - - -] Tenant: '54589053b612438ab9c4d3f800c75000' is adding the datastore version: '5.7.29' to datastore: 'mysql' *2024-03-18 12:26:20.719 35 WARNING keystoneauth.identity.generic.base [None req-ef8a2f03-8500-40e0-88fe-4fac6ac5c9cb 85c09dd86fc846f98c3b4add7f64d76f 54589053b612438ab9c4d3f800c75000 - - - -] Failed to discover available identity versions when contacting https://dashint.cdn.example.com:5000 <https://dashint.cdn.example.com:5000>. Attempting to parse version from URL.: keystoneauth1.exceptions.connection.SSLError: SSL exception connecting to https://dashint.cdn.example.com:5000 <https://dashint.cdn.example.com:5000>: HTTPSConnectionPool(host='dashint.cdn.example.com <http://dashint.cdn.example.com>', port=5000): Max retries exceeded with url: / (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1129)')))* *2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi [None req-ef8a2f03-8500-40e0-88fe-4fac6ac5c9cb 85c09dd86fc846f98c3b4add7f64d76f 54589053b612438ab9c4d3f800c75000 - - - -] e85a7be5-6d90-456e-8c24-4125098a6228: Could not find versioned identity endpoints when attempting to authenticate. Please check that your auth_url is correct. SSL exception connecting to https://dashint.cdn.example.com:5000 <https://dashint.cdn.example.com:5000>: HTTPSConnectionPool(host='dashint.cdn.example.com <http://dashint.cdn.example.com>', port=5000): Max retries exceeded with url: / (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1129)'))): keystoneauth1.exceptions.discovery.DiscoveryFailure: Could not find versioned identity endpoints when attempting to authenticate. Please check that your auth_url is correct. SSL exception connecting to https://dashint.cdn.example.com:5000 <https://dashint.cdn.example.com:5000>: HTTPSConnectionPool(host='dashint.cdn.example.com <http://dashint.cdn.example.com>', port=5000): Max retries exceeded with url: / (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1129)')))* 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi Traceback (most recent call last): 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi File "/var/lib/kolla/venv/lib64/python3.9/site-packages/urllib3/connectionpool.py", line 703, in urlopen 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi httplib_response = self._make_request( 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi File "/var/lib/kolla/venv/lib64/python3.9/site-packages/urllib3/connectionpool.py", line 386, in _make_request 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi self._validate_conn(conn) 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi File "/var/lib/kolla/venv/lib64/python3.9/site-packages/urllib3/connectionpool.py", line 1042, in _validate_conn 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi conn.connect() 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi File "/var/lib/kolla/venv/lib64/python3.9/site-packages/urllib3/connection.py", line 419, in connect 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi self.sock = ssl_wrap_socket( 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi File "/var/lib/kolla/venv/lib64/python3.9/site-packages/urllib3/util/ssl_.py", line 449, in ssl_wrap_socket 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi ssl_sock = _ssl_wrap_socket_impl( 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi File "/var/lib/kolla/venv/lib64/python3.9/site-packages/urllib3/util/ssl_.py", line 493, in _ssl_wrap_socket_impl 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi return ssl_context.wrap_socket(sock, server_hostname=server_hostname) 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi File "/var/lib/kolla/venv/lib64/python3.9/site-packages/eventlet/green/ssl.py", line 446, in wrap_socket 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi return GreenSSLSocket(sock, *a, _context=self, **kw) 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi File "/var/lib/kolla/venv/lib64/python3.9/site-packages/eventlet/green/ssl.py", line 140, in __init__ 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi self.do_handshake() 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi File "/var/lib/kolla/venv/lib64/python3.9/site-packages/eventlet/green/ssl.py", line 312, in do_handshake 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi return self._call_trampolining( 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi File "/var/lib/kolla/venv/lib64/python3.9/site-packages/eventlet/green/ssl.py", line 162, in _call_trampolining 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi return func(*a, **kw) 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi File "/usr/lib64/python3.9/ssl.py", line 1343, in do_handshake 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi self._sslobj.do_handshake() 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi ssl.SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1129) 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi During handling of the above exception, another exception occurred: 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi Traceback (most recent call last): 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi File "/var/lib/kolla/venv/lib64/python3.9/site-packages/requests/adapters.py", line 489, in send 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi resp = conn.urlopen( 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi File "/var/lib/kolla/venv/lib64/python3.9/site-packages/urllib3/connectionpool.py", line 787, in urlopen 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi retries = retries.increment( 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi File "/var/lib/kolla/venv/lib64/python3.9/site-packages/urllib3/util/retry.py", line 592, in increment 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi raise MaxRetryError(_pool, url, error or ResponseError(cause)) 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host=' dashint.cdn.example.com', port=5000): Max retries exceeded with url: / (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1129)'))) 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi During handling of the above exception, another exception occurred: 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi Traceback (most recent call last): 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi File "/var/lib/kolla/venv/lib64/python3.9/site-packages/keystoneauth1/session.py", line 1014, in _send_request 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi resp = self.session.request(method, url, **kwargs) 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi File "/var/lib/kolla/venv/lib64/python3.9/site-packages/requests/sessions.py", line 587, in request 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi resp = self.send(prep, **send_kwargs) 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi File "/var/lib/kolla/venv/lib64/python3.9/site-packages/requests/sessions.py", line 701, in send 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi r = adapter.send(request, **kwargs) 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi File "/var/lib/kolla/venv/lib64/python3.9/site-packages/requests/adapters.py", line 563, in send 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi raise SSLError(e, request=request) 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi requests.exceptions.SSLError: HTTPSConnectionPool(host=' dashint.cdn.example.com', port=5000): Max retries exceeded with url: / (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1129)'))) 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi During handling of the above exception, another exception occurred: 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi Traceback (most recent call last): 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi File "/var/lib/kolla/venv/lib64/python3.9/site-packages/keystoneauth1/identity/generic/base.py", line 133, in _do_create_plugin 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi disc = self.get_discovery(session, 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi File "/var/lib/kolla/venv/lib64/python3.9/site-packages/keystoneauth1/identity/base.py", line 605, in get_discovery 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi return discover.get_discovery(session=session, url=url, 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi File "/var/lib/kolla/venv/lib64/python3.9/site-packages/keystoneauth1/discover.py", line 1459, in get_discovery 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi disc = Discover(session, url, authenticated=authenticated) 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi File "/var/lib/kolla/venv/lib64/python3.9/site-packages/keystoneauth1/discover.py", line 539, in __init__ 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi self._data = get_version_data(session, url, 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi File "/var/lib/kolla/venv/lib64/python3.9/site-packages/keystoneauth1/discover.py", line 106, in get_version_data 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi resp = session.get(url, headers=headers, authenticated=authenticated) 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi File "/var/lib/kolla/venv/lib64/python3.9/site-packages/keystoneauth1/session.py", line 1133, in get 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi return self.request(url, 'GET', **kwargs) 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi File "/var/lib/kolla/venv/lib64/python3.9/site-packages/keystoneauth1/session.py", line 923, in request 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi resp = send(**kwargs) 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi File "/var/lib/kolla/venv/lib64/python3.9/site-packages/keystoneauth1/session.py", line 1018, in _send_request 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi raise exceptions.SSLError(msg) 2024-03-18 12:26:20.721 35 ERROR trove.common.wsgi keystoneauth1.exceptions.connection.SSLError: SSL exception connecting to https://dashint.cdn.example.com:5000: HTTPSConnectionPool(host=' dashint.cdn.example.com', port=5000): Max retries exceeded with url: / (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1129)'))) Regards.

1 0

Is direct upgrade from Yoga to Antelope supported?
by Michel Jouvin 18 Mar '24

18 Mar '24

Hi, We are in the process of upgrading our Yoga cloud to Antelope and I was wondering if, Antelope being a SLURP release, it was supported to do it in 1 step or if Antelope was the first release from which it will be possible to skip one release and to go directly to the next SLURP release (Caracal). I didn't find a clear answer in the documentation... Best regards, Michel

5 5

New instance, provider vlan network, network unpredictable
by Mika Saari 18 Mar '24

18 Mar '24

Hi, I am using latest kolla-ansible installation. Network is in openvswitch type. My question is related to my provider network with VLAN type (external HW router, external DHCP, ...). The network is directly connected to the hardware through HW switch <-tagged-> bond0 <-> br-ex1 <-> openvswitch. When I create a new instance (cirros) to this provider network the instance can not connect to the metadata server during the bootup. The dhcp is trying to fetch the address, and I can sniff the data in bond0, br-ex1, br-int and br-tun and the dhcp request leaves the hardware, DHCP server sends the reply, but the reply wont go through back to the instance. If I force a static IP to this cirros instance and try pinging the network, the ICMP doesn't leave the bond0. After around 15 minutes the network starts suddenly to work and dhcp reply goes through and the instance gets the dynamic IP. After this the whole network starts to work fluently. Any ideas what might be the problem? Thank you very much!

3 5

[neutron] Bug Deputy Report March 11 - March 17
by Nurmatov Mamatisa 18 Mar '24

18 Mar '24

Hi team, Below is the week summary of bug report for last week. 1 rfe was proposed. Undecided bugs needs further triage. Details: High ---- - https://bugs.launchpad.net/neutron/+bug/2057492 - [devstack-tobiko-neutron] periodic broken running on ubuntu focal - In progress: https://review.opendev.org/c/x/tobiko/+/912718 - Assigned to Slawek Kaplonski - https://bugs.launchpad.net/neutron/+bug/2057770 - [neutron-dynamic-routing] LBaaS constants still present in older versions of Neutron - Fix released: https://review.opendev.org/c/openstack/neutron-dynamic-routing/+/912737 - Assigned to Rodolfo Alonso - https://bugs.launchpad.net/neutron/+bug/2057914 - [neutron-vpnaas-dashboard] UT failing due to a change in Django - Fix released: https://review.opendev.org/c/openstack/neutron-vpnaas-dashboard/+/912911 - Assigned to Rodolfo Alonso - https://bugs.launchpad.net/neutron/+bug/2057942 - external_gateways KeyError when running add_gw_port_info_to_logical_router_port - In progress: https://review.opendev.org/c/openstack/neutron/+/913408 - Assigned to Brian Haley Medium ------ - https://bugs.launchpad.net/neutron/+bug/2056778 - TestOVNMechanismDriver some ipv6 tests fails if host has ipv6 dns_names configured - Fix released: https://review.opendev.org/c/openstack/neutron/+/912475 (backported to stable/2023.1 , stable/2023.2) - Assigned to Arnau Verdaguer - https://bugs.launchpad.net/neutron/+bug/2057698 - Concurrent routerroute update fails on deletion with AttributeError - In progress: https://review.opendev.org/c/openstack/neutron/+/912629 - Assigned to Sebastian Lohff - https://bugs.launchpad.net/neutron/+bug/2057983 - The HA flag of user defined flavos routers is always set to true - In progress: https://review.opendev.org/c/openstack/neutron/+/913276 - Miguel Lavalle RFE --- - https://bugs.launchpad.net/neutron/+bug/2058006 - [RFE] Allow multiple segments per host in ML2/OVN Undecided --------- - https://bugs.launchpad.net/neutron/+bug/2058018 - AssertionError: do not call blocking functions from the mainloop Best regards, Mamatisa Nurmatov

1 0

[kuryr-libnetwork] Run with a service container or install on the compute node?
by Francesco Di Nucci 18 Mar '24

18 Mar '24

Hello, I am working to install Zun on a OpenStack instance, so I'm required to set up Docker with kuryr-libnetwork. I see that there are three possible approaches: * Running it inside a service container, using the Docker Engine on the compute nodes (https://opendev.org/openstack/kuryr-libnetwork#getting-it-running-with-a-se…) * Installing it directly on the compute nodes (https://opendev.org/openstack/kuryr-libnetwork#getting-it-running-with-a-se…) * Installing it as a Docker plugin (https://opendev.org/openstack/kuryr-libnetwork#getting-it-running-with-a-se…) Does anyone know the advantages/disadvantages of the three approaches? I've tried to find a comparison, but the OpenStack docs only include a procedure to install it on a Ubuntu Compute Node (https://docs.openstack.org/kuryr-libnetwork/latest/install/compute-install-…) Best regards Francesco Di Nucci

1 0

Neutron external connectivity to and from tenant VMs : Help
by KK CHN 16 Mar '24

16 Mar '24

Hi, Neutron external network connection to and from instances.. Problem statement. I have deployed AIO on a Virtual Machine. (Created the demo networks, flavors and images by init-runonce script.) I created a cirros instance with a demo-net instance, and the instance is spawning with 10.0.0.0/24 ips. *inside the cirros Vm I am able to ping its own ip(10.0.0.73) and 10.0.0.1 and the "public1" network gateway 10.176.17.63 .. But unable to ping the Base VM IP 10.176.17.61* Any hints how I can reach the Base VM IP 10.176.17.61 ? from 10.0.0.73 and vice versa .. What steps I missed or I am unaware of? To get the external connection/ping/access..? I have referred many documents and I am at the end of the rope, but couldn't find a solution or what the exact issue is , any guidance much appreciated... Krish. If more information is required : There are two networks by default created 1. public1. with gateway as 10.176.17.63 public1-subnet <http://10.220.0.24/project/networks/subnets/3b9e11ae-4595-4e4c-ba71-1fba209…> 10.176.16.0/23 IPv4 10.176.17.63 2. demo-net demo-subnet <http://10.220.0.24/project/networks/subnets/80e8d33e-6276-450b-bb46-76446dc…> 10.0.0.0/24 IPv4 10.0.0.1 These are the values given in the " kolla_ansible_venv3/share/kolla-ansible/init-runonce" script.. ################################################################################# DEMO_NET_CIDR=${DEMO_NET_CIDR:-'10.0.0.0/24'} DEMO_NET_GATEWAY=${DEMO_NET_GATEWAY:-'10.0.0.1'} DEMO_NET_DNS=${DEMO_NET_DNS:-'8.8.8.8'} ENABLE_EXT_NET=${ENABLE_EXT_NET:-1} EXT_NET_CIDR=${EXT_NET_CIDR:-'10.176.17.0/23'} EXT_NET_RANGE=${EXT_NET_RANGE:-'start=10.176.17.62,end=10.176.17.80'} EXT_NET_GATEWAY=${EXT_NET_GATEWAY:-'10.176.16.1'} ################################################################################ Demo Router: (ee6500a8-039c) <http://10.220.0.24/project/networks/ports/ee6500a8-039c-4ceb-8dc0-b37e2c3a2…> - 10.176.17.63 Active External Gateway UP (bb4c9437-82fa) <http://10.220.0.24/project/networks/ports/bb4c9437-82fa-4689-b125-9edc1987c…> - 10.0.0.1 Active Internal Interface UP (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" // a free unused IP address in 10.220.0.0/24 segment. kolla_external_vip_address: "{{ kolla_internal_vip_address }}" kolla_container_engine: docker network_interface: "ens224" /// this vNIC is with ip 10.220.0.51 and without internet - a vlan segment for internal experiments. neutron_external_interface: "ens160" // this is the vNIC with my organization dhcp leased ip 10.176.17.61 assigned and up and running neutron_plugin_agent: "openvswitch" nova_compute_virt_type: "qemu" (kolla_ansible_venv3) ubuntu@ub Strange Behaviour: When I create another instance ( Cirros) with the network selected as " public1" network, the instance is spawning the horizon dashboard showing IP as 10.176.17.70 extTestVM <http://10.220.0.24/project/instances/9e744ab1-7a21-4d55-ad03-c01d5631657a/> cirros 10.176.17.70 But inside this VM $ ip a /// lists the IP address of this VM as 169.254.198.1/16 ?? why 169.254 .198.1/16 ? It should be 10.176.17.70 right ?? What's happening ?? Confused ..

3 4

[all][tc][policy] RBAC discussion in 2024.2 PTG
by Ghanshyam Mann 16 Mar '24

16 Mar '24

Hello Everyone, I have booked the Tuesday 15-16 UTC slot Folsom room for the RBAC discussion. Feel free to add the topics/queries to be discussed or your project-related RBAC session info in the below etherpad: - https://etherpad.opendev.org/p/rbac-2024.2-ptg -gmann

1 0

Enabling SNAT for Non-Private Addresses
by Jan Wasilewski 15 Mar '24

15 Mar '24

Hi everyone, I'd like to inquire about SNAT settings for non-private addresses. I've created a network with the subnet 100.70.0.0/24 (please note, it starts with 100, not 10). I'm wondering why all hosts attached to such a network cannot establish an internet connection when the network is connected to a router with an external gateway that has internet access. However, I found documentation here: https://docs.openstack.org/neutron/zed/admin/intro-nat.html, which states that SNAT works only for private addresses (so mine are not included). Is there a way to enable SNAT for my subnet as well, but in a different way than manually configuring iptables settings on top of Neutron nodes? If so, could anyone share it? Thanks in advance for your help. /Jan Wasilewski

2 3

[kolla-ansible][Antelope][Heat] Auto Scaling Group - Cancel Update
by Devin Patterson 15 Mar '24

15 Mar '24

Hello, We are working on a workflow to cancel in progress rolling updates for the resource OS::Heat::AutoScalingGroup When we run the command `openstack stack cancel <stack-id> it cancels the Heat stack update, but the Auto-Scaling group finishes updating all VMs in the group. We need a way to either rollback or completely cancel the Auto Scaling Group update and not replace any additional VMs. Any help would be appreciated. Devin

1 0

[release] Release countdown for week R-2
by Thierry Carrez 15 Mar '24

15 Mar '24

Development Focus ----------------- At this point we should have release candidates (RC1 or recent intermediary release) for all the 2024.1 Caracal deliverables. Teams should be working on any release-critical bugs that would require another RC or intermediary release before the final release. Actions ------- Early in the week, the release team will be proposing stable/2024.1 branch creation for all deliverables that have not branched yet, using the latest available 2024.1 Caracal release as the branch point. If your team is ready to go for creating that branch, please let us know by leaving a +1 on these patches. If you would like to wait for another release before branching, you can -1 the patch and update it later in the week with the new release you would like to use. By the end of the week the release team will merge those patches though, unless an exception is granted. Once stable/2024.1 branches are created, if a release-critical bug is detected, you will need to fix the issue in the master branch first, then backport the fix to the stable/2024.1 branch before releasing out of the stable/2024.1 branch. After all of the cycle-with-rc projects have branched we will branch devstack, grenade, and the requirements repos. This will effectively open them up for 2024.2 Dalmatian development, though the focus should still be on finishing up 2024.1 Caracal until the final release. Opening up the new development cycle is also a good opportunity to teams to revise their zuul jobs and used nodesets and clean up all unnecessary ones. For projects with translations, watch for any translation patches coming through and merge them quickly. A new release should be produced so that translations are included in the final 2024.1 Caracal release. Finally, now is a good time to finalize release notes. In particular, consider adding any relevant "prelude" content. Release notes are targeted for the downstream consumers of your project, so it would be great to include any useful information for those that are going to pick up and use or deploy the 2024.1 Caracal version of your project. Upcoming Deadlines & Dates -------------------------- Final RC deadline: March 28th, 2024 (R-1 week) Final 2024.1 Caracal release: April 3rd, 2024 Dalmatian PTG: April 8-12, 2024 -- Thierry Carrez (ttx)

1 0

[skyline] Pending changes to Kolla-ansible for Skyline
by Jäger Uwe 15 Mar '24

15 Mar '24

Dear Skyline-Team, I have created a couple of changes for Kolla-ansible to have Skyline configured to use the latest features. If you find the time, your are invited to have a look at those changes: 909481: Allow overriding of Skyline logos | https://review.opendev.org/c/openstack/kolla-ansible/+/909481 910514: Skyline configure Prometheus | https://review.opendev.org/c/openstack/kolla-ansible/+/910514 905861: Allow customizing of Skyline configuration | https://review.opendev.org/c/openstack/kolla-ansible/+/905861 905860: Update Skyline configuration to enable SSO | https://review.opendev.org/c/openstack/kolla-ansible/+/905860 909329: Fix Skyline API Server TLS configuration | https://review.opendev.org/c/openstack/kolla-ansible/+/909329 909482: Add more services to nginx.conf | https://review.opendev.org/c/openstack/kolla-ansible/+/909482 If you have any questions or comments, please leave them there or contact me directly. Kind regards Uwe

2 1