- openstack-discuss - lists.openstack.org

[Diversity] PTG Schedule
by Amy Marrich 07 Apr '24

07 Apr '24

The Diversity and Inclusion working group will hold a session Tuesday, April 9th at 14:00 UTC in the Cactus room. Agenda is available[0], please add any topics. Amy 0 - https://etherpad.opendev.org/p/apr2024-ptg-diversity

1 0

Re: [all] Review dependencies without update for long time
by Sean McGinnis 07 Apr '24

07 Apr '24

> Subject: Re: [all] Review dependencies without update for long time In case it's not known, there is a script in the repo that was created to help find some of this information: https://opendev.org/openstack/requirements/src/branch/master/tools/get-heal… > > > > I recently spent some time reviewing the packages currently in the requirements repo > > and found some packages which haven't been updated for multiple years. This is a good > > indication that we have to review the features dependent on these packages to determine > > if the features should be re-implemented by a different package or dropped. Keeping such > > features with unmaintained library may likely cause problems in future maintenance > > (Python 3.12 support is a good example). > > > > > > $ git blame -e upper-constraints.txt | grep -e '201[0-9]-' | sed -e 's/.* 201/201/' | sort > > 2015-06-08 22:09:46 +1200 500) simplegeneric===0.8.1 > > 2016-05-19 06:30:24 +0000 169) extras===1.0.0 > > 2016-11-14 17:07:49 +0000 69) XStatic-Font-Awesome===4.7.0.0 > > 2016-12-18 07:20:50 +0000 583) xvfbwrapper===0.2.9 > > 2017-02-21 14:05:54 -0600 118) pyinotify===0.9.6 > > 2017-02-21 14:05:54 -0600 146) jsonpath-rw===1.4.0 > > 2017-02-21 14:05:54 -0600 150) traceback2===1.4.0 > > 2017-02-21 14:05:54 -0600 163) XStatic-roboto-fontface===0.5.0.0 > > 2017-02-21 14:05:54 -0600 208) unittest2===1.1.0 > > 2017-02-21 14:05:54 -0600 226) XStatic-objectpath===1.2.1.0 > > 2017-02-21 14:05:54 -0600 256) dib-utils===0.0.11 > > 2017-02-21 14:05:54 -0600 283) XStatic-Angular-Schema-Form===0.8.13.0 > > 2017-02-21 14:05:54 -0600 287) XStatic-bootswatch===3.3.7.0 > > 2017-02-21 14:05:54 -0600 290) XStatic-term.js===0.0.7.0 > > 2017-02-21 14:05:54 -0600 317) pydotplus===2.0.2 > > 2017-02-21 14:05:54 -0600 332) murano-pkg-check===0.3.0 > > 2017-02-21 14:05:54 -0600 347) testscenarios===0.5.0 > > 2017-02-21 14:05:54 -0600 354) nose-exclude===0.5.0 > > 2017-02-21 14:05:54 -0600 357) elasticsearch===2.4.1 > > 2017-02-21 14:05:54 -0600 366) XStatic-tv4===1.2.7.0 > > 2017-02-21 14:05:54 -0600 367) XStatic-JSEncrypt===2.3.1.1 > > 2017-02-21 14:05:54 -0600 380) linecache2===1.0.0 > > 2017-02-21 14:05:54 -0600 390) openstack.nose-plugin===0.11 > > 2017-02-21 14:05:54 -0600 403) testrepository===0.0.20 > > 2017-02-21 14:05:54 -0600 41) requests-aws===0.1.8 > > 2017-02-21 14:05:54 -0600 420) zake===0.2.2 > > 2017-02-21 14:05:54 -0600 448) proboscis===1.2.6.0 > > 2017-02-21 14:05:54 -0600 465) XStatic-smart-table===1.4.13.2 > > 2017-02-21 14:05:54 -0600 487) testresources===2.0.1 > > 2017-02-21 14:05:54 -0600 60) pysendfile===2.0.1 > > 2017-02-21 14:05:54 -0600 613) XStatic-D3===3.5.17.0 > > 2017-02-21 14:05:54 -0600 70) nose===1.3.7 > > 2017-02-21 14:05:54 -0600 88) nosexcover===1.0.11 > > 2017-02-21 14:05:54 -0600 96) Tempita===0.5.2 > > 2017-06-28 10:13:14 +0000 576) logutils===0.3.5 > > 2017-09-10 10:31:03 +0000 514) repoze.lru===0.7 > > 2017-11-22 13:05:07 +0000 184) whereto===0.4.0 > > 2017-11-24 06:19:46 +0000 501) python-pcre===0.7 > > 2018-01-08 14:19:08 +0000 203) oslosphinx===4.18.0 > > 2018-01-30 00:00:05 +0000 486) requestsexceptions===1.4.0 > > 2018-03-01 06:25:09 +0000 537) CouchDB===1.2 > > 2018-03-01 06:25:09 +0000 540) ws4py===0.5.1 > > 2018-03-01 06:25:09 +0000 97) ply===3.11 > > 2018-03-28 06:24:01 +0000 349) sadisplay===0.4.9 > > 2018-05-11 06:33:27 +0000 236) threadloop===1.0.2 > > 2018-05-13 06:27:38 +0000 289) XStatic-JS-Yaml===3.8.1.0 > > 2018-05-13 06:27:38 +0000 309) XStatic-Angular-UUID===0.0.4.0 > > 2018-05-13 06:27:38 +0000 524) XStatic-Json2yaml===0.1.1.0 > > 2018-05-13 06:27:38 +0000 579) XStatic-Angular-Vis===4.16.0.0 > > 2018-05-13 06:27:38 +0000 64) XStatic-FileSaver===1.3.2.0 > > 2018-06-02 06:29:39 +0000 262) lockfile===0.12.2 > > 2018-07-09 06:36:15 +0000 408) python-consul===1.1.0 > > 2018-07-14 06:36:14 +0000 525) boto===2.49.0 > > 2018-09-11 06:22:11 +0000 381) oauth2client===4.1.3 > > 2019-01-01 06:10:54 +0000 471) cotyledon===1.7.3 > > 2019-02-14 06:49:02 +0000 299) XStatic-mdi===1.6.50.2 > > 2019-02-14 06:51:11 +0000 113) XStatic-Jasmine===2.4.1.2 > > 2019-04-15 06:20:25 +0000 362) pysmi===0.3.4 > > 2019-04-23 13:47:12 +0100 572) sphinx-testing===1.0.1 > > 2019-05-12 12:14:16 +0000 343) os-service-types===1.7.0 > > 2019-05-14 06:11:31 +0000 275) retryz===0.1.9 > > 2019-05-14 06:11:31 +0000 400) bitmath===1.3.3.1 > > 2019-05-14 06:11:31 +0000 535) cachez===0.1.2 > > 2019-05-26 06:27:47 +0000 195) URLObject===2.4.3 > > 2019-05-26 06:27:47 +0000 215) pact===1.12.0 > > 2019-05-26 06:27:47 +0000 30) vintage===0.4.1 > > 2019-05-26 06:27:47 +0000 313) capacity===1.3.14 > > 2019-05-26 06:27:47 +0000 365) infi.dtypes.iqn===0.4.0 > > 2019-05-26 06:27:47 +0000 422) flux===1.3.5 > > 2019-05-26 06:27:47 +0000 442) api-object-schema===2.0.0 > > 2019-05-26 06:27:47 +0000 46) waiting===1.4.1 > > 2019-05-26 06:27:47 +0000 481) sentinels===1.0.0 > > 2019-05-26 06:27:47 +0000 609) confetti===2.5.3 > > 2019-05-26 06:27:47 +0000 84) infi.dtypes.wwn===0.1.1 > > 2019-07-13 06:50:09 +0000 53) jsonpath-rw-ext===1.2.2 > > 2019-08-15 06:36:56 +0000 528) mitba===1.1.1 > > 2019-09-05 07:13:47 +0000 293) gossip===2.4.0 > > 2019-10-07 06:11:48 +0000 112) rsd-lib===1.2.0 > > 2019-10-07 06:11:48 +0000 74) pysnmp===4.4.12 > > 2019-10-22 21:19:25 +0000 336) sqlalchemy-migrate===0.13.0 > > 2019-11-01 17:20:28 +0200 71) nosehtmloutput===0.0.7 > > 2019-11-30 06:10:48 +0000 513) ndg-httpsclient===0.5.1

1 0

[ptg][openstack-ansible] OpenStack-Ansible vPTG time and date
by Dmitriy Rabotyagov 06 Apr '24

06 Apr '24

Hi folks, Sorry for the late scheduling of vPTG this time. I've booked an Icehouse room for Tuesday, April 9 from 16:00 (4PM) till 18:00 (6PM) UTC. You can find the meeting link below [1]. An etherpad with some agenda is here: [2] [1] https://meetpad.opendev.org/apr2024-ptg-os-ansible [2] https://etherpad.opendev.org/p/osa-dalmatian-ptg

1 0

[opnestack][kolla-ansible]Mix compute inventory
by Nguyễn Hữu Khôi 06 Apr '24

06 Apr '24

Hello. I am reading about Kolla Ansible Inventory https://docs.openstack.org/kolla-ansible/latest/user/multinode.html In my environment, Controllers and Compute01>>>03 have same network interfaces But from compute04>>06 have different interface neutron_external_interface=*eth0.1 *api_interface=*eth0.2 *tunnel_interface= *eth0.3* Which is the best group for my case? [compute-custom] compute04 neutron_external_interface=*eth0.1 *api_interface=*eth0.2 * tunnel_interface=*eth0.3* compute05 neutron_external_interface=*eth0.1 *api_interface=*eth0.2 * tunnel_interface=*eth0.3* compute06 neutron_external_interface=*eth0.1 *api_interface=*eth0.2 * tunnel_interface=*eth0.3* Then put them to same block services which have Nova? I see the we prefer to use host_vars or*group_vars. *Do we have some examples about it? Thank you. Nguyen Huu Khoi

1 0

[Nova][Kolla][VDI] Introducing Kerbside delivery of VDI console sessions
by Michael Still 06 Apr '24

06 Apr '24

Hi all, for the longest time I've thought it was super cool that you could do something like this with Google Cloud: `gcloud compute ssh ...instance...` This causes a SSH session to run in your terminal that transparently proxies you through to the instance. It even orchestrates SSH authentication using a CA, but that's a story for another day. Aptira had a similar business need, but with more of a focus on virtual desktop environments, and therefore kindly supported my development work on a SPICE protocol native proxy I've called Kerbside [1][2]. The proxy works by scraping various clouds' REST APIs for "VDI capable" instances, and then making those available via short lived session tokens. The intention is that a service like Horizon or Skyline could request a session token for a specific instance, which is returned to the user as a `.vv` style virt-viewer configuration file. The user then opens the configuration file and a connection to the console on the relevant hypervisor is provided by Kerbside. Kerbside can do more than that of course. It has a simple management UI and API, which allows for things like forced termination of a console session once setup, logging and audit history, TLS support, and so forth. Kerbside and all associated work is licensed under the Apache 2 license, just the same as OpenStack, and positions clouds to offer Citrix-like virtual desktops to their users in a seamless manner. Why a SPICE proxy? As best as I can tell, SPICE still provides the richest virtual desktop experience. It supports high resolution desktops, multi-screen desktops, USB device passthrough, sound, multiple user connections to a single console, and so forth. Why not the current HTML5 transcoding proxy as used by Horizon? Unfortunately, the current HTML5 SPICE client does not support most of the features listed in the previous paragraph. While originally intended for the purposes of my personal Shaken Fist project, Kerbside now supports OpenStack and oVirt as well. In the case of OpenStack, this required a number of patches to OpenStack projects to get working [3]. Specifically I'd like to propose a new Nova API microversion to support a new "spice-direct" console type. I intend to work through the Nova specs process for the Nova related changes, and have created a blueprint [4] to track that work. I am working on a draft spec at the moment [5], but do not see the required changes to Nova as particularly invasive. You can of course assess that yourself by reading the proof of concept patches in the kerbside-patches repository. This raises some questions for me. Specifically: - is this functionality interesting to others? Or is it just me? - what is the process of proposing changes like this for Kolla and Kolla-Ansible? I chose to build my proof of concept on that platform, so I also have a number of aligned deployment patches there. - I've been out of the OpenStack universe for a while now. Is it too late to propose this work for Dalmation? Thanks, Michael 1: https://github.com/shakenfist/kerbside and https://github.com/shakenfist/kerbside-client 2: Why Kerbside? Well because Horizon and Skyline are distant things, whereas I wanted to create something closer... Like Kerbside pickup from a shop. 3: https://github.com/shakenfist/kerbside-patches 4: https://blueprints.launchpad.net/nova/+spec/libvirt-spice-direct-consoles 5: https://github.com/shakenfist/kerbside-patches/blob/develop/nova-specs/patc…

3 3

[blazar][ptg] Dalmatian PTG schedule
by Pierre Riteau 05 Apr '24

05 Apr '24

Hello, I have booked a PTG slot on Thursday, April 11 from 1500 to 1700 UTC for the Blazar project. The meeting will be held in the Bexar room. The initial agenda can be found here: https://etherpad.opendev.org/p/apr2024-ptg-blazar Please add any topics you would like to discuss. Anyone interested in Blazar is welcome to join. Cheers, Pierre Riteau (priteau)

1 0

[ptg][tacker]Dalmatian vPTG Planning
by Yasufumi Ogawa 05 Apr '24

05 Apr '24

Hi all, I've booked the slots[1] from Apr 9th to 11th, 6-8 UTC all the days, and setup the etherpad[2] for Tacker team. Please feel free to add your topics. [1] https://ptg.opendev.org/ptg.html [2] https://etherpad.opendev.org/p/apr2024-ptg-tacker Thanks, Yasufumi

1 0

[swift][ptg] Ops Feedback Session - 10th April at 1300 UTC
by Matthew Oliver 05 Apr '24

05 Apr '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 in the dalmation swift meetpad room ( https://meetpad.opendev.org/swift-ptg-dalmatian) on Wednesday at 13: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-dalmation-ops-feedback) This has always been a highlight at every PTG for us swift devs. Have your say and help make Swift even better! Matt

1 0

[kolla] [mariadb] Backups failing if they take over an hour
by Chris DiLorenzo 05 Apr '24

05 Apr '24

Were using the mariadb_backup command of kolla-ansible to backup the database. We're doing daily, full backups. It's been working fine until recently. Now we are getting this error: 2024-04-03 21:16:33 0 [Note] InnoDB: Read redo log up to LSN=317647271424 2024-04-03 21:16:48 0 [Note] InnoDB: Read redo log up to LSN=317647424512 2024-04-03 21:17:03 0 [Note] InnoDB: Read redo log up to LSN=317647586304 2024-04-03 21:17:18 0 [Note] InnoDB: Read redo log up to LSN=317647733248 [01] 2024-04-03 21:17:23 ...done [00] FATAL ERROR: 2024-04-03 21:17:23 failed to execute query SET SESSION lock_wait_timeout=31536000: Server has gone away It started as soon as the DB backup took more than 1 hour. In our other environments where the backup is < 1hr, it works fine. There are no errors in the logs when this happens, other then the above output from mariabackup Any suggestions? Thanks, Chris

2 1

[neutron] Dalmatian vPTG reminder
by Brian Haley 05 Apr '24

05 Apr '24

Hello Neutrinos, This year our vPTG slots are: Tuesday, April 9th, 13:00 - 17:00 UTC Wednesday, April 10th, 13:00 - 17:00 UTC Thursday, April 11th, 13:00 - 17:00 UTC (if necessary) See https://ptg.opendev.org/ptg.html for room info and other teams' sessions. Etherpad is at https://etherpad.opendev.org/p/apr2024-ptg-neutron - please add anything you would like to discuss by tomorrow so I can create a schedule. See you on Tuesday! -Brian

1 0

[manila] Dalmatian vPTG Schedule
by Carlos Silva 05 Apr '24

05 Apr '24

Hello, Zorillas and interested stackers, I would like to share with you our agenda for next week's PTG [1]. In case you would like a topic to be moved around, please let me know and I'll be happy to accommodate changes. [1] https://etherpad.opendev.org/p/dalmatian-ptg-manila Looking forward to having many productive discussions with you! Regards, carloss

1 0

help
by Carita Ndibe 05 Apr '24

05 Apr '24

I am trying to customize my dashboard but keep getting this error: uncompressableFileError at auth/login static/dashboard/scss/custom.scss' could not be found in the COMPRESS_ROOT '/opt/stack/horizon/static' or with staticfiles I previously had an offline compression error by i resolved be settion COMPRESSION_ENABLED to False. how can I resolve this?

1 0

[release]OpenStack Caracal 2024.1 Highlights on OpenInfra Live
by Allison Price 04 Apr '24

04 Apr '24

Hi everyone, Happy OpenStack Caracal 2024.1 release day! Tomorrow, at 1400 UTC, there will be an OpenInfra Live episode [1] to cover some of the project highlights from this project cycle and what can be expected for OpenStack Dalmatian 2024.2. Here is a lineup of the OpenStack community leaders and the updates they will be covering: Sylvain Bauza (Nova), Ghanshyam Mann (Technical Committee), Riccardo Pittau (Ironic), Rajat Dhasmana (Cinder), Carlos Silva (Manila) Join us as we celebrate OpenStack’s 29th release! Cheers, Allison [1] https://www.youtube.com/watch?v=3BgAXbFaVqw

1 1

[openstack-ansible] : Ussuri minor version update.
by keshav bareja 04 Apr '24

04 Apr '24

Hi Team I am planning to update my environment from the current ussuri minor version to the latest minor version available for the Ussuri. I found the procedure below. https://docs.openstack.org/openstack-ansible/ussuri/admin/upgrades/minor-up… I have some queries on this: 1. How to find the current minor release version of the Ussuri deployed on my environment? Is there any command or way that can help? 2. What is the latest minor version available for Ussuri? In the Ussuri release notes page I could see 2.10, can someone please confirm if 2.10 is the latest version? 3. Also I need to know the bug fixes between my current release to the latest minor ussuri release. 4. Can someone confirm what all pre-requisite I need to take care of before going with the update. 5. Anyone having experience with such minor updates , Please share precaution and recommendations, Ussuri Series Release Notes <https://docs.openstack.org/releasenotes/openstack-ansible/victoria.html> <https://docs.openstack.org/releasenotes/openstack-ansible/train.html> <https://bugs.launchpad.net/openstack-ansible/+filebug?field.title=Ussuri%20…> 21.2.10 <https://docs.openstack.org/releasenotes/openstack-ansible/ussuri.html#relno…>Security Issues <https://docs.openstack.org/releasenotes/openstack-ansible/ussuri.html#secur…> - This release eliminates following security issues: - OSSA-2021-005: https://security.openstack.org/ossa/OSSA-2021-005.html - OSSA-2021-006: https://security.openstack.org/ossa/OSSA-2021-006.html

2 5

Panko Service get_events function returning none
by Sandesh Kulkarni 04 Apr '24

04 Apr '24

Hi Openstack Team, I am using Panko for events retrieval, but I am getting None from the below query. My current SqlAlchemy version is 1.4.31. Could you please guide me in retrieving the correct events from the database? Output from the panko events api :- { "message_id": "2b4d83b4-3e23-4326-bedb-557a405c16db", "event_type": "audit.http.response", "traits": [ { "name": "action", "value": "None", "type": "string" }, { "name": "eventTime", "value": "2024-03-27T03:59:52.192750", "type": "datetime" }, { "name": "eventType", "value": "None", "type": "string" }, { "name": "id", "value": "None", "type": "string" }, { "name": "initiator_host_address", "value": "None", "type": "string" }, { "name": "initiator_id", "value": "None", "type": "string" }, { "name": "initiator_name", "value": "None", "type": "string" }, { "name": "initiator_typeURI", "value": "None", "type": "string" }, { "name": "observer_id", "value": "None", "type": "string" }, { "name": "outcome", "value": "None", "type": "string" }, { "name": "project_id", "value": "None", "type": "string" }, { "name": "reason_code", "value": "None", "type": "string" }, { "name": "requestPath", "value": "None", "type": "string" }, { "name": "request_id", "value": "None", "type": "string" }, { "name": "service", "value": "None", "type": "string" }, { "name": "target_id", "value": "None", "type": "string" }, { "name": "target_name", "value": "None", "type": "string" }, { "name": "target_typeURI", "value": "None", "type": "string" }, { "name": "typeURI", "value": "None", "type": "string" }, { "name": "user_id", "value": "None", "type": "string" } ], "generated": "2024-03-27T03:59:52.693294", "raw": {} } Query Link :- https://github.com/openstack/panko/blob/4d0c0d66da6833e5283d71fe5bdee9594e4… Thanks and Regards, Sandesh Kulkarni

1 0

[all][elections][tc] 2024.2 Dalmatian Technical Committee Election Results
by Ian Y. Choi 04 Apr '24

04 Apr '24

Please join me in congratulating the 5 newly elected members of the Technical Committe (TC). Amy Marrich (spotz) Goutham Pacha Ravi (gouthamr) Dmitriy Rabotyagov (noonedeadpunk) Artem Goncharov (gtema) (replacing Sylvain Bauza - bauzas as per the TC resolution) [1] Slawek Kaplonski (slaweq) Full results: https://civs1.civs.us/cgi-bin/results.pl?id=E_f8044ce7af316bf3 Election process details and results are also available here: https://governance.openstack.org/election/ Note that we encountered a situation where not all members as elected could be seated which requires TC resolution. More details on the resolution are explained in [1], and thank you all for the understanding and support in resolving this matter. Thank you to all of the candidates, having a good group of candidates helps engage the community in our democratic process. Thank you to all who voted and who encouraged others to vote. We need to ensure your voice is heard. Thank you for another great round. [1] https://governance.openstack.org/tc/resolutions/20240322-adjudication-of-20…

1 0

OpenStack 2024.1 Caracal is officially released!
by Herve Beraud 04 Apr '24

04 Apr '24

Hello OpenStack community, The official OpenStack 2024.1 Caracal release announcement has been sent out: https://lists.openstack.org/archives/list/openstack-announce@lists.openstac… Thanks to all who were a part of the 2024.1 Caracal development cycle! This marks the official opening of the openstack/releases repository for 2024.2 Dalmatian releases, and freezes are now lifted. stable/2024.1 is now a fully normal stable branch, and the normal stable policy applies from now on. Thanks, -- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/

3 2

User survey 2023 - TC questions
by Sławek Kapłoński 04 Apr '24

04 Apr '24

Hi, I am doing analysis of the TC questions in the 2023 user survey [1] and I need some additonal information. In the results of the survey which I some time ago got from Allison there are only short "names" of the questions, like e.g. "TCContributions" but no full question which was asked. This is ok for me for the questions which were in the survey in previous years but this year TC added couple of new questions for which I don't have full questions at all. Short names of those questions are: - TCConsumingOpenStack - TCConsumingOpenStackOther - TCInteractOpenStack - TCInteractOpenStack - TCInteractOpenStackSkyline - TCInteractOpenStackSkylineList - TCInteractSkylineOther - TCInteractOpenStackInternal - TCInteractOpenStackInternalOther - TCCloudServices Can You maybe share with me what were those full questions in the survey? Or point me to the place where I can maybe find it? Thx in advanve for help with this. [1] https://review.opendev.org/c/openstack/governance/+/900516 -- Slawek Kaplonski Principal Software Engineer Red Hat

2 2

[all][tc] Next week TC meeting is canceled
by Ghanshyam Mann 03 Apr '24

03 Apr '24

Hello Everyone, As next week is vPTG happening, we are canceling next week's (April 9th) TC meeting. -gmann

1 0

[freezer] Project status update
by Dmitriy Rabotyagov 03 Apr '24

03 Apr '24

Hey there! In a previous email thread [1] an interest toward reviving the Freezer project was raised. As a result of the thread we've organized a first sync meeting with interested parties. It was a quite productive discussion and we came up with a couple of action points as a result of it. You can find more information in the etherpad [2] Among everything, one of the most important parts for now, is to step into the PTL role or move a project to a distributed leadership. At the moment the project is leadless, since there was no candidacy submitted for this election. We also agreed to schedule the next meeting on April 2 from 16-00 till 17-00 UTC and discuss progress and blockers which were found. I'm attaching an invitation to the meeting to the email. If it doesn't work, you can join on the mentioned time via the link [3] Hope to see you there and thanks for everyone who participated and stepped in for the project! [1] https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… [2] https://etherpad.opendev.org/p/freezer-status [3] https://meet.google.com/ckc-gevi-epe

1 2

[cinder] Canceling this week's meeting (3rd April)
by Rajat Dhasmana 02 Apr '24

02 Apr '24

Hello Argonauts, Given that tomorrow is the 2024.1 Caracal release and PTG coming up next week, we decided in last week's meeting to cancel the cinder meeting, which was going to be held on 3rd April, 2024. See you all next week at the PTG! Thanks Rajat Dhasmana

1 0

[neutron] Proposing Ihar Hrachyshka as neutron core reviewer
by Brian Haley 02 Apr '24

02 Apr '24

Hello Neutrinos, I would like to nominate Ihar Hrachyshka for Neutron core reviewer (again). He's been leaving some very useful comments lately, moved-up in the reviewer stats over the past 90 days [0], and has a lot of OVN knowledge. Ihar was previously a core reviewer from 2015-2018 so most might already know him. I think he'd be a great re-addition to the team. Please vote with a +1/-1. [0] https://www.stackalytics.io/report/contribution?module=neutron-group&projec… Thanks, -Brian, Neutron PTL

8 8

Re: [neutron][magnum][mcapi] floating IP delete permission issue
by Satish Patel 02 Apr '24

02 Apr '24

Thank you Mohammed, It would be really good if we have a flag in template to say release floating IP instead of delete. Technically operator assign floating IPs to project and only that project should use them as per need instead of delete floating ips and put it back to book. Let’s see if we can get some eyeballs on this feature. But this is very important feature for us to control public IP usage. On Mon, Apr 1, 2024 at 10:16 PM Mohammed Naser <mnaser(a)vexxhost.com> wrote: > Hi Satish, > > This is actually something that would have to be handled on the Cluster > API level, since it is the one that owns that resource. > > I would start raising an issue there first, if that gets traction then we > can integrate that with the driver after, however, if it doesn't make sense > for it to be there, we can maybe include a config flag to handle this (but > I'm not sure what other implications this would have) > > Thanks > Mohammed > ------------------------------ > *From:* Satish Patel <satish.txt(a)gmail.com> > *Sent:* April 1, 2024 10:09 PM > *To:* OpenStack Discuss <openstack-discuss(a)lists.openstack.org> > *Subject:* [neutron][magnum][mcapi] floating IP delete permission issue > > Folks, > > For regulatory purposes we set a neutron policy to not let normal users > delete their public floating IPs because they are assigned to specific > customers and we don't want them to delete them. So far that policy works. > > But now when it comes to magnum / mcapi. I am able to create a cluster but > not able to delete because when magnum is going to delete floating IP I am > getting an error saying you are not allowed to delete floating IP and k8s > are stuck in deleting state. > > Is there any way magnum can do floating IP release instead of delete? > > Following error I am seeing in CAPI logs. > > I0402 01:50:03.412447 1 recorder.go:104] "events: Failed to delete > floating IP 101.xx.xx.70: Request forbidden: [DELETE > https://os2.example.com:9696/v2.0/floatingips/492b2c4c-151b-437e-acfc-4778a…] > error message: {\"NeutronError\": {\"type\": \"PolicyNotAuthorized\", > \"message\": \"rule:delete_floatingip is disallowed by policy\", > \"detail\": \"\"}}" type="Warning" > object={"kind":"OpenStackMachine","namespace":"magnum-system","name":"kube-6aqje-csgft-nkz6s","uid":"97acabe1-e547-4bbc-8406-aebc563212cd","apiVersion":" > infrastructure.cluster.x-k8s.io/v1alpha7","resourceVersion":"31170690"} > reason="Faileddeletefloatingip" >

1 0

how to use policy.json in kolla
by mohammad kokabi 02 Apr '24

02 Apr '24

Hello, I'm using OpenStack Kolla Ansible, and I want to define a specific level of access for each user, but I couldn't find any documentation on this matter. For example, I have two users named David and Adrian, and I want the user David to have the ability to delete an instance, while the user Adrian should not have this access. Both users are members of a shared project. The only documentation I found is a sample policy.yaml file, which states that it should be placed in the /etc/nova directory. Could you please clarify where this file should be located for OpenStack Kolla Ansible? https://docs.openstack.org/nova/latest/configuration/sample-policy.html

1 0

[neutron] Bug Deputy Report March 25 - March 31
by Yatin Karel 02 Apr '24

02 Apr '24

Hi Neutrinos, Below is the bug deputy report for last week:- High ------ - https://bugs.launchpad.net/neutron/+bug/2058908 fix auto_scheduler_network understanding dhcp_agents_per_network Assigned to Sahid Orentino Medium ---------- - https://bugs.launchpad.net/neutron/+bug/2058712 [openvswitch-agent] Trunk extension should not be loaded if service plugin is disabled Assigned to Julien Cosmao Low ----- - https://bugs.launchpad.net/neutron/+bug/2059236 Add a RBAC action field in the query hooks Assigned to Rodolfo Alonso Undecided -------------- - https://bugs.launchpad.net/neutron/+bug/2059716 [ovn] Multihomed backend (IPv4 + IPv6) with floating IP unreachable, requested more information. -- Thanks and Regards Yatin Karel

1 0