June 2023 - openstack-discuss - lists.openstack.org

[all][requirements] Automated management of setup.py
by Pierre Riteau 13 Jun '23

13 Jun '23

Hello, We recently had a patch [1] submitted to cloudkitty-dashboard that dropped support for Python 2.7 bits in setup.py (which is fine), but at the same time removed the following line: # THIS FILE IS MANAGED BY THE GLOBAL REQUIREMENTS REPO - DO NOT EDIT I pointed it out to the author but they never updated their patch. This comment is managed by the update.py script in requirements [2]. Should there be an effort to update setup.py across all repositories using this script? Thanks, Pierre Riteau (priteau) [1] https://review.opendev.org/c/openstack/cloudkitty-dashboard/+/884339 [2] https://opendev.org/openstack/requirements/src/branch/master/openstack_requ…

3 4

Openstack /port mirroir issue [Neutron]
by altidor JB 13 Jun '23

13 Jun '23

Hello, I've set up Openstack Zed on Ubuntu Jammy using Juju and MAAS. I'm experimenting with some IDS on the architecture and need to implement some kind of port mirroring capacity. I've been trying with Tap as a Service but can't find any resources for the installation/configuration on my architecture. The git refers to Devstack implementation. I'm using the large-scale deployment on 6 servers. Can anyone point me in the right direction? Thanks! JB

2 2

[Octavia] cancelling meeting June 14th
by Gregory Thiemonge 13 Jun '23

13 Jun '23

Hi Folks, As discussed during the last meeting, we are cancelling tomorrow's meeting, it conflicts with the Octavia Forum Session at the OpenInfra summit. Thanks, Gregory

1 0

[neutron] Bug deputy report (week starting on June-5-2022)
by Bernard Cafarelli 13 Jun '23

13 Jun '23

Hey neutrinos, time for a new bug deputy rotation again! Here are the bugs reported between June 5 and 11. Overall, a quiet week, and all bugs have proposed patches. Handing over the deputy role to Lajos, and remember that all meetings are cancelled this week because of the Vancouver PTG Medium * [neutron-api] remove leader_only for maintenance worker - https://bugs.launchpad.net/bugs/2022914 Patch proposed https://review.opendev.org/c/openstack/neutron/+/885240 * OVN DB sync acls Timeout - https://bugs.launchpad.net/bugs/2023130 Patch proposed to batch the transaction https://review.opendev.org/c/openstack/neutron/+/885224 * [OVN] Agent deletion only removes the "Chassis" register, not the "Chassis_Private" one - https://bugs.launchpad.net/bugs/2023171 Patch by ralonsoh https://review.opendev.org/c/openstack/neutron/+/885744 -- Bernard Cafarelli

1 0

New repo for os-net-config?
by Dan Sneddon 12 Jun '23

12 Jun '23

The TripleO project is being retired, and the Master/Zed branches are no longer being maintained. However the os-net-config project is still required for bare metal network configuration, and I believe the codebase may be used by other parties, however I don't have a good list of who is still using the codebase. We need to find another repo that can host os-net-config, hopefully on opendev.org, since the GitHub repo doesn't have the same level of CI that we have now on OpenStack Jenkins. Can anyone recommend or volunteer a repository that would be able to host os-net-config going forward? I expect it will be needed for another year or so at least, just for the use cases that I'm aware of. If anyone has still been using os-net-config outside of TripleO, can you please speak up, either on-list or to me directly? Thank you very much for any suggestions, -Dan Sneddon -- Dan Sneddon | Senior Principal Software Engineer dsneddon(a)redhat.com | redhat.com/cloud dsneddon:irc | @dxs:twitter

9 11

[puppet] Sessions in June 2023 PTG
by Takashi Kajinami 12 Jun '23

12 Jun '23

Hello, I'm attending the upcoming OpenInfra Summit and PTG at Vancouver so would like to moderate some puppet sessions in PTG. I've reserved slots from 14:30 to 16:20 on Wednesday. However we can be flexible so please let me know if you are interested but have any conflicts. https://etherpad.opendev.org/p/vancouver-june2023-puppet-openstack I've added a few topics including the recent discussion about module modernization. However it'd be nice if we can have a few more topics, especially any feedback from users or (potential) new contributors. Please add your name and topics if you are planning to join us. Thank you, Takashi

4 3

[kolla-ansible][ovn][ovs] connection dropped and inactivity errors
by Satish Patel 12 Jun '23

12 Jun '23

2 1

[neutron][ptg] PTG schedule
by Rodolfo Alonso Hernandez 12 Jun '23

12 Jun '23

Hello all: This is the PTG week and we are thrilled to have you there. Just as a heads-up, on Tuesday at 11:20 [1] we have the "*Neutron meet and greet: Operators feedback session*". Join us to share your feedback. We have also booked the* table 15* [2] on Wednesday and Thursday, from 9:00 to 12:50. Please remember our previously used etherpad [3] is now combined in the PTG generated etherpad [4]. Please use this last link [4]. Regards and see you tomorrow! [1]https://vancouver2023.openinfra.dev/a/schedule [2]https://ptg.opendev.org/ptg.html [3]https://etherpad.opendev.org/p/neutron-vancouver-2023 [4]https://etherpad.opendev.org/p/vancouver-june2023-neutron

1 0

[tc] No weekly meeting on June 13
by Nikolla, Kristi 12 Jun '23

12 Jun '23

Hi all, As this week is the Open Infra Summit and PTG there will be no weekly meeting of the TC on June 13. The next meeting will be Tuesday, June 20, 2023. Best, Kristi Nikolla

1 0

package installation
by Mohd Haniff Bin Abdullah 12 Jun '23

12 Jun '23

Hi, We have installed OpenStack CLI VM and can access to CLI. Our VM does not have internet connection. Thus, we need the whole package to be downloaded and sftp to the VM. Where could we get the package? I got this from previous colleague, but he left our company and we don't have a clue where he got that packages.tar.gz. Would you please help us? Thank you so much! [cid:image001.png@01D99D66.73040A90] Regards, Haniff

1 0

Monitoring
by Murilo Morais 12 Jun '23

12 Jun '23

Good morning everybody! Guys, which monitoring stack do you recommend to monitor Host and VM resources? Or what monitoring strategies do they recommend?

3 3

[tacker] Skip weekly IRC meeting
by Yasufumi Ogawa 11 Jun '23

11 Jun '23

Hi team, Since we'll have PTG this week, I would like to skip the next IRC meeting on Jun 13. Thanks, Yasufumi

1 0

[magnum] kubectl loses access after 31 days
by Vivian Rook 09 Jun '23

09 Jun '23

After 31 days I lose kubectl access to magnum clusters. This has happened consistently for any cluster that I have deployed. The clusters run just fine, though around 31 days of operation kubectl cannot connect, and the web service shows the service as down (Though the web service on the cluster is responding enough to say that nothing is working, so the cluster has not completely crashed) All kubectl commands have a long pause (about 10 minutes) then gives errors like: Error from server (Timeout): the server was unable to return a response in the time allotted, but may still be processing the request (get deployments.apps) Unable to connect to the server: stream error: stream ID 11; INTERNAL_ERROR; received from peer I have a little more information in https://phabricator.wikimedia.org/T336586 It feels like a cert is expiring as it always seems to happen right about 31 days after deployment. Does magnum have some kind of certificate like that? I checked the kubectl certs, they were set to be fine for years, so I don't think it is them unless I didn't check them correctly (Let's not discount that possibility, I totally could have read the wrong bit of the cert). I can still generate a new kubectl config file with openstack coe cluster config <cluster> Though the resulting configuration will have the same issue as the original config (long pause, then timeout errors). I have also tried to run: openstack coe ca rotate <cluster> Which is accepted and seems to run fine, but after that point if I regenerate a kubeconfig file as above I get new errors when running kubectl: Unable to connect to the server: x509: certificate signed by unknown authority (possibly because of "crypto/rsa: verification error" while trying to verify candidate authority certificate "<cluster>") If the key rotation would work, and I'm not doing it correctly, I would be delighted to hear how to run it correctly. Though ideally I would like to find where the original key is failing, and if it is an expiration, how to set it to a longer time. Thank you! -- *Vivian Rook (They/Them)* Site Reliability Engineer Wikimedia Foundation <https://wikimediafoundation.org/>

1 1

[release] Release countdown for week R-16, June 12-16
by Thierry Carrez 09 Jun '23

09 Jun '23

Development Focus ----------------- The bobcat-2 milestone will happen in next month, on July 6, 2023. 2023.2 Bobcat-related specs should now be finalized so that teams can move to implementation ASAP. Some teams observe specific deadlines on the second milestone (mostly spec freezes): please refer to https://releases.openstack.org/bobcat/schedule.html for details. General Information ------------------- Please remember that libraries need to be released at least once per milestone period. At milestone 2, the release team will propose releases for any library that has not been otherwise released since milestone 1. Other non-library deliverables that follow the cycle-with-intermediary release model should have an intermediary release before milestone-2. Those who haven't will be proposed to switch to the cycle-with-rc model, which is more suited to deliverables that are released only once per cycle. At milestone-2 we also freeze the contents of the final release. If you have a new deliverable that should be included in the final release, you should make sure it has a deliverable file in: https://opendev.org/openstack/releases/src/branch/master/deliverables/bobcat You should request a beta release (or intermediary release) for those new deliverables by milestone-2. We understand some may not be quite ready for a full release yet, but if you have something minimally viable to get released it would be good to do a 0.x release to exercise the release tooling for your deliverables. See the MembershipFreeze description for more details: https://releases.openstack.org/bobcat/schedule.html#b-mf Finally, now may be a good time for teams to check on any stable releases that need to be done for your deliverables. If you have bugfixes that have been backported, but no stable release getting those. If you are unsure what is out there committed but not released, in the openstack/releases repo, running the command "tools/list_stable_unreleased_changes.sh <cycle_name>" gives a nice report. Upcoming Deadlines & Dates -------------------------- OpenInfra Summit in Vancouver: From June 13 to June 15, 2023 Bobcat-2 Milestone: July 6, 2023 -- Thierry Carrez (ttx)

1 0

[ironic][ops] Forum Session at OIS Vancouver 2023
by Iury Gregory 09 Jun '23

09 Jun '23

Hello everyone, I would like to invite everyone interested in ironic to join our Forum Session next week during the Open Infrastructure Summit in Vancouver! The forum session *Ironic: Our Future starts Now! *will be held on *Wed, June 14, 10:20am - 10:50am | Vancouver Convention Centre - Room 9* This is a chance to provide feedback to our work, see you all next week in Vancouver! -- *Att[]'s* *Iury Gregory Melo Ferreira * *MSc in Computer Science at UFCG* *Ironic PTL * *Senior Software Engineer at Red Hat Brazil* *Social*: https://www.linkedin.com/in/iurygregory *E-mail: iurygregory(a)gmail.com <iurygregory(a)gmail.com>*

1 0

[glance][ops][ptg] glance operator event at the summit/PTG
by Brian Rosmaita 09 Jun '23

09 Jun '23

Hello operators, Come by and meet members of the Glance project team and give us feedback, unusual use cases, feature requests, etc. Wednesday 14 June 15:10-15:40 (UTC-7) Table #13 in the PTG area etherpad: https://etherpad.opendev.org/p/vancouver-june2023-glance

1 0

[cinder][ops] cinder operator events at the summit/PTG
by Brian Rosmaita 09 Jun '23

09 Jun '23

Hello operators, Just want to alert you about some opportunities to give feedback to the Cinder project team while you're at the summit or PTG: Wednesday 14 June, 11:40-12:10 Forum session: Cinder, the OpenStack Block Storage service ... how are we doing? (Looking for feedback from operators, vendors, and end-users) Vancouver Convention Centre - Room 9 Wednesday 14 June, 15:50-16:20 PTG session: Operator Half-Hour (Focus on operator feedback) Table #13 in the PTG area Thursday 15 June, 16:40-17:10 PTG session: Open Discussion with the Cinder project team (Focus on developers, but willing to discuss anything, really) Table #13 in the PTG area

1 0

[cinder][ptg] cinder PTG schedule
by Brian Rosmaita 09 Jun '23

09 Jun '23

Hello Argonauts, We're going to have a small presence at the PTG next week, so we've only scheduled 3 sessions: Wednesday 14 June 10:20-10:50 Support for NVMe-OF in os-brick 15:50-16:20 Cinder Operator Half-Hour Thursday 15 June 16:40-17:10 Open Discussion with the Cinder project team All times are Vancouver time (UTC-7) and all will take place at Table #13 in the PTG area. Here's the Cinder PTG etherpad: https://etherpad.opendev.org/p/vancouver-ptg-june-2023 cheers, brian

1 0

[cinder][all] EOL EM branches
by Rajat Dhasmana 09 Jun '23

09 Jun '23

Hi, We had a discussion in the last cinder meeting regarding making EM branches EOL for the cinder project[1]. The discussion started because of the CVE fixes where we backported to active stable branches i.e. Yoga, Zed and 2023.1 but there were no backports to further EM stable branches like Xena, Wallaby ... all the way to Train. Cinder team doesn't see much merit in keeping these EM stable branches alive since there is rarely any activity that requires collaboration and if there is, it is usually by the core cinder team. Following are some of our reasons to EOL these branches: 1) We have less review bandwidth even for active stable branches (Yoga, Zed and 2023.1) 2) No one, apart from the project team, does backport of critical fixes implying that those branches aren't used much for collaboration 3) Will save gate resources for some periodic jobs and the patches proposed 4) Save project team's time to fix gate issues We, as the cinder team, have decided to EOL all the existing EM branches that go from Train to Xena. It was agreed upon by the cinder team and no objections were raised during the upstream cinder meeting. We would like to gather more feedback outside of the cinder team regarding if this affects other projects, deployers, operators, vendors etc. Please reply to this email with your concerns, if you have any, so we can discuss again and reconsider our decision. Else the week after the summit we will be moving forward with our current decision. If you will be at the Vancouver Summit, you can also give us feedback at the cinder Forum session at 11:40 am on Wednesday June 14. [1] https://meetings.opendev.org/irclogs/%23openstack-meeting-alt/%23openstack-… Thanks Rajat Dhasmana

8 14

[kolla] Image building process getting stuck
by Satish Patel 09 Jun '23

09 Jun '23

Folks, I am trying to build images using 2023.1 kolla tag but every time it's getting stuck here and there and I have to ctrl+c and re-run the build. It's very frustrating. How do CI jobs build images without getting stuck? Because of that I have to build images role-by-role instead of all images in a single shot. Example, This is stuck here since 24 hours and not moving at all : https://paste.opendev.org/show/bf1rRhg9V3BCy4KmHPRg/

1 0

[cinder] Spec Review Day 09 June
by Rajat Dhasmana 09 Jun '23

09 Jun '23

Hello Argonauts, Inspired from the nova team, we will be having our day of spec review. As decided in today's cinder meeting, we will be having spec review day on 09th June i.e. this Friday. Following are the details: Date: 09 June, 2023 Time: 1400-1500 UTC Connection Information: Meeting link will be shared in the cinder channel before the event Thanks Rajat Dhasmana

1 1

[gate][tripleo] gate blocker
by Ananya Banerjee 09 Jun '23

09 Jun '23

Hello, Jobs on Centos 9 deploying standalone or multinode are failing standalone deploy or overcloud deploy with https://bugs.launchpad.net/tripleo/+bug/2023019 . Fixes are in progress, please hold rechecks for the moment if you hit this. Thanks, Ananya -- Ananya Banerjee, RHCSA, RHCE-OSP Software Engineer Red Hat EMEA <https://www.redhat.com/> anbanerj(a)redhat.com M: +491784949931 IM: frenzy_friday @RedHat <https://twitter.com/redhat> Red Hat <https://www.linkedin.com/company/red-hat> Red Hat <https://www.facebook.com/RedHatInc> <https://www.redhat.com/>

2 1

Octavia does not work properly.
by GOPAL RAJORA 09 Jun '23

09 Jun '23

Hi everyone. Hope you are well. This is Gopal. I am contacting you as I need your help. So, recently I installed the Octavia service on the Openstack server. After installation of the Octavia, several services such as Nova, Neutron and Keystone started not to work and I can not access the horizon page either. So, I have checked the logs, for the moment, keystone service does not work after the Octavia installation. *Unable to establish connection to http://keystone-api.openstack.svc.cluster.local:5000/v3/auth/tokens <http://keystone-api.openstack.svc.cluster.local:5000/v3/auth/tokens>: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response'))* So, I tried to install the Octavia service several times, so if I disable the health manager, it seems everything works properly, but as you know, Octavia can not work properly if the heath manger is not installed. So, can you please help me regarding this problem? Thanks.

3 6

[neutron] Neutron drivers meeting cancelled
by Rodolfo Alonso Hernandez 09 Jun '23

09 Jun '23

Hello Neutrinos: Due to the lack of agenda [1], today's meeting is cancelled. Please remember that all meetings will be cancelled next week too because of the Vancouver PTG. Have a nice weekend! [1]https://wiki.openstack.org/wiki/Meetings/NeutronDrivers

1 0

Strange Cinder rpc timeouts after Xena upgrade
by Colby Walsworth 09 Jun '23

09 Jun '23

Hey Everyone, We just upgraded from Wallaby to Xena. We use Ceph as our volume/image backend. All instances from before the upgrade seem to be unable to be shelved/unshelved or live migrated (have not tried offline migration yet). Any new instances that are created work fine and all those tasks work fine on those. The problem seems to be with cinder: cinder.api.v3.attachments [req-2af34fab-a4b5-43f3-bd9a-94f360201533 e28435e0a66740968c523e6376c57f68 179f701c810c425ab004548cc1f76bc9 - default default] Unable to create attachment for volume.: oslo_messaging.exceptions.MessagingTimeout: Timed out waiting for a reply to message ID 8eea6a00568a477c89ced8db17f1179d the migrations and shelve/unshelve processes start on the hypervisor but eventually error out with the above message. Any new instances I create do not have this issue at all. I have done all the db upgrades so I don't believe this is a db record update issue. Any ideas of what might be causing this? Thanks, Colby

2 1

[ironic][barbican][qa][tripleo][nova][opendev] Next steps for Fedora jobs in OpenStack
by Tony Breeds 08 Jun '23

08 Jun '23

Hello all, Following on from "Future of Fedora and CentOS Stream Test Images"[1] discussion on service-discuss the opendev infra team have removed the unused Fedora content from the AFS mirrors. Now it's time to look at removing the Fedora-36 content from the mirrors. I'd like to, again, point out the Fedora 36 isn't the latest release and is infact EOL[4]. Removal of the Fedora 36 content will start with something like "[configure-mirrors] Allow per distribution disabling of mirrors"[2]. Once merged, and activated, this means that any/all Fedora based jobs will pull OS content from the Fedora project mirrors directly. There isn't an ETA but "soon" is a fair estimate. Any Fedora jobs will potentially run slower and will be more subject to network failures, this is also the situation with existing rocky linux jobs and there hasn't been any major problems[3]. Projects using Fedora are encouraged to switch to CentOS Stream or Rocky Linux. As at some stage the Fedora nodepool images may also need to go away. OpenStack users of Fedora (master) appear to be: * name: bifrost-integration-tinyipa-fedora-latest where: https://opendev.org/openstack/bifrost/src/branch/master/zuul.d/bifrost-jobs… recent builds: https://zuul.openstack.org/builds?job_name=bifrost-integration-tinyipa-fedo… * name: bifrost-integration-redfish-uefi-fedora-latest where: https://opendev.org/openstack/bifrost/src/branch/master/zuul.d/bifrost-jobs… recent builds: https://zuul.openstack.org/builds?job_name=bifrost-integration-redfish-uefi… * name: barbican-dogtag-tox-functional where: https://opendev.org/openstack/barbican/src/branch/master/.zuul.yaml#L16 recent builds: https://zuul.openstack.org/builds?job_name=barbican-dogtag-tox-functional&b… * name: devstack-plugin-ceph-tempest-fedora-latest where: https://opendev.org/openstack/devstack-plugin-ceph/src/branch/master/.zuul.… recent builds: https://zuul.openstack.org/builds?job_name=devstack-plugin-ceph-tempest-fed… * name: devstack-platform-fedora-latest where: https://opendev.org/openstack/devstack/src/branch/master/.zuul.yaml#L861 recent builds: https://zuul.openstack.org/builds?job_name=devstack-platform-fedora-latest&… * name: devstack-platform-fedora-latest-virt-preview where: https://opendev.org/openstack/devstack/src/branch/master/.zuul.yaml#L868 recent builds: https://zuul.openstack.org/builds?job_name=devstack-platform-fedora-latest-… Notes: This COPR has CentOS Stream packages * name: validations-libs-podified-podman where: https://opendev.org/openstack/validations-libs/src/branch/master/.zuul.yaml… recent builds: https://zuul.openstack.org/builds?job_name=validations-libs-podified-podman… * name: novajoin-functional where: https://opendev.org/x/novajoin/src/branch/master/.zuul.yaml#L13 recent builds: https://zuul.openstack.org/builds?job_name=novajoin-functional&branch=maste… * name: bindep-fedora-latest where: https://opendev.org/opendev/bindep/src/branch/master/.zuul.yaml#L24 recent builds: https://zuul.openstack.org/builds?job_name=bindep-fedora-latest&branch=mast… Looking at these jobs they're all non-voting or disabled apart from: * validations-libs-podified-podman, which is part of which is part of tripleo and as such the future is hazy * bindep-fedora-latest, This job would seem to be a loss, however from a funcational test POV Fedora and Centos Stream are compatible [1] https://lists.opendev.org/archives/list/service-discuss@lists.opendev.org/t… [2] https://review.opendev.org/c/zuul/zuul-jobs/+/884935?tab=change-view-tab-he… [3] This may be in part due to the scale/number of those jobs [4] https://docs.fedoraproject.org/en-US/releases/eol/ Yours Tony.

2 1

[cinder] Active-Active cluster support for allocated_capacity_gb
by Ilya Popov 08 Jun '23

08 Jun '23

Hello, All ! There is one issue with Active/Actvie cinder cluster. Each cinder-volume instance in cluster holds it's own local allocated_capacity_gb. When cinder-volume service starts it counts all volumes created on particular pool and calculates allocated_capacity_gb accordingly. If one instance of cinder-volume create volume - it increase its local allocated_capacity_gb. If other instance delete volume - it decrease its local allocated_capacity_gb. And each instance of cinder-volume in cluster reports its own local allocated_capacity_gb. It cause incorrect allocated_capacity_gb presented to cinder get-pools --detail. And it is able to see even negative value of allocated_capacity_gb for pool. There is reported issue about it: https://bugs.launchpad.net/cinder/+bug/1927186 There is document about different approaches of Active-Active cinder support, but there is nothing about incorrect allocated_capacity_gb report on it: https://docs.openstack.org/cinder/latest/contributor/high_availability.html Looks like without fixing allocated_capacity_gb we have to get all valumes and calculate this value by portal (it isnt quite effective and resource consuming by the way). Are there any plans to complete Active/Active support for cinder ? For example as the coordinator is demand for Active/Active support (“My recommendation is to do this right: configure the cluster option, remove the backend_host, and configure the coordinator.”, https://lists.openstack.org/pipermail/openstack-discuss/2020-November/01885…) - it is possible to move allocated_capacity_gb for each pool to redis or to listen notification queue and change local allocated_capacity_gb for each instance of cinder-volume accordingly Bug #1927186 “the value of allocated_capacity_gb is Incorrect wh...” : Bugs : Cinder<https://bugs.launchpad.net/cinder/+bug/1927186> the value of allocated_capacity_gb is incorrect when the number of replaca of cinder-volume is more than one and all of them configurated same backend, We set up more than one cinder-volume service ,and all of them have the same config file with the same storage backend. When all cinder-volume services complete initialization, the value of 'allocated_capacity_gb' that command of 'cinder get pools -detail' returned is correct.But once any creating or deleting volumes has been done, the value... bugs.launchpad.net 

1 0

[kolla-ansible][Yoga] Manila share creation stuck in creating status cephfs backend
by wodel youchi 08 Jun '23

08 Jun '23

Hi, We are facing a strange problem, when creating manila shares, we use cephfs as backend, the creation is stuck in creation state. If we try to delete the share, we get and error "you are not authorized to delete share ...." We have to use force-delete in cli to be able to delete it. We don't have any indication in manila's log files, there no error or exception. It seems like an access right problem, but we don't know where to look. Regards. <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Virus-free.www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

1 1

[security-sig] PTG schedule
by Jeremy Stanley 07 Jun '23

07 Jun '23

I've booked a PTG table for the two "slots" immediately prior to Thursday's lunch break (11:00-12:50 Vancouver time). See https://ptg.opendev.org/etherpads.html for a link to the notepad for it; I've added some ideas for things we could do or discuss but add anything you'd like to cover and I'm happy to pivot based on attendee interest. Given the timing, we can also turn it into an early lunch outing or whatever. -- Jeremy Stanley

1 0

[manila] Cancelling June 8th and June 15th weekly meetings
by Carlos Silva 07 Jun '23

07 Jun '23

Hello, Since June 8th is a holiday in some countries and that will impact the weekly meeting's attendance numbers, we are cancelling this meeting. The weekly meeting of June 15th is also being cancelled, as some members will be attending the OpenInfra Summit. The next upstream weekly meeting will be on June 22nd. Regards, carloss

1 0

[manila][ptg] Vancouver PTG
by Carlos Silva 07 Jun '23

07 Jun '23

Hello, zorillas and interested stackers. In the previous weekly meeting I mentioned the tentative time slot for next week's PTG and I got confirmation. We will host a hybrid session for our PTG on Thursday 9:40AM to 12:10 PM PDT. More details about the location, topics and connecting to the meeting bridge will be available in the PTG etherpad [1]. You can still add your topics until Friday (June 9th) to the etherpad. [1] https://etherpad.opendev.org/p/manila-openinfra-2023 Regards, carloss

1 0

[all][ops][rbac] RBAC feedback sessions in Vancouver Summit
by Ghanshyam Mann 07 Jun '23

07 Jun '23

Hello Everyone, If you are planning to attend Vancouver Summit, we will have a forum discussion on Tuesday to provide the RBAC updates and collect operators' feedback. "OpenStack RBAC: updates & operators feedback" - Tue, June 13, 1:45pm - 2:15pm | Vancouver Convention Centre - Room 9 I have created the etherpad to collect the feedback, feel free to write your feedback if you cannot attend this session. - https://etherpad.opendev.org/p/rbac-operator-feedback-vancouver2023 -gmann

1 0

[cinder] Vancouver PTG scheduling
by Brian Rosmaita 07 Jun '23

07 Jun '23

Hello Vancouver-bound Argonauts, In trying to put together a doodle pool, I found it was way easier to just use an etherpad. So please navigate on over to it and block out your unavailability before the Cinder Spec Review meeting at 1400 UTC on Friday 9 June. https://etherpad.opendev.org/p/vancouver2023-cinder-ptg-scheduling thanks, brian

1 0

Question About BGP Dynamic Routing, Floating IP, and SNAT
by Alex Z 07 Jun '23

07 Jun '23

Hi Everyone, Hope you are all doing well. I’m a beginner to Openstack and Neutron and now run into an issue about SNAT and shared floating IP. I’ve already deployed a neutron network which uses BGP to announce floating IP to PE (Provider Edge router), and everything works as expected when I assign the public floating IP (e.g., 123.0.0.10/24) to VMs. But when I tried to use floating IP port-forwarding function with floating IP 123.0.0.20/24 and rule (internal_ip 10.10.10.10, internal_port 5555, external_port 64000), and assign a private IP (10.10.10.10/24) to a VM. The floating IP 123.0.0.20 won’t be advertised through BGP. May I have some suggestions about how I could get this fixed, or the neutron just won’t work this way? FYI, 1. Per my understanding, the port_forwardings rule will make the port act like a SNAT role and forward any packets that reach it with destination 123.0.0.20:64000 to the private IP 10.10.10.10/24. 2. The IP address could be reached in the neutron network. 3. PE IP address, CE IP address, and floating IP gateway are using the same subnet A and subnet pool (192.168.123.0/24), while floating IP belongs to subnet B and subnet pool (123.0.0.0/24), both subnets belong to the provider network. 4. Only floating IP that assigned to the specific VM will be advertised to PE through BGP 5. Floating IP that is assigned to the port of a router in the neutron network won’t be advertised, even if the IP is activated and is reachable internally. Sincerely, Alex

1 0

[i18n] upstream investment: translations infrastructure engineer
by Brian Rosmaita 07 Jun '23

07 Jun '23

I've proposed an OpenStack "upstream investment opportunity" for an engineer to handle the Zanata -> Weblate re-plumbing for gerrit/zuul: https://review.opendev.org/c/openstack/governance/+/885379 Please leave comments if you have any. cheers, brian

1 0

Cinder Bug Report 2023-06-07
by Sofia Enriquez 07 Jun '23

07 Jun '23

Hello Argonauts, Cinder Bug Meeting Etherpad <https://etherpad.opendev.org/p/cinder-bug-squad-meeting> *Medium* - Volume creation fails if an old signature is found when using the LVM driver. <https://bugs.launchpad.net/cinder/+bug/2023073> - *Status*: Unassigned. - LIO target doesn't support discard on thin volumes. <https://bugs.launchpad.net/cinder/+bug/2023168> - *Status*: Fix proposed to master. <https://review.opendev.org/c/openstack/cinder/+/885451> *Low* - Cinder PowerMax driver volume attach/detach hang issues. <https://bugs.launchpad.net/cinder/+bug/2021999> - *Status*: Fix proposed to master <https://review.opendev.org/c/openstack/cinder/+/884957>. - Huawei Oceanstor volume driver is not up to date with official Huawei's driver <https://bugs.launchpad.net/cinder/+bug/2022152>. - *Status*: Please propose the topic to the cinder meeting <https://wiki.openstack.org/wiki/CinderMeetings>. *Incomplete* - [huawei] wrong hostname passed to os_brick. <https://bugs.launchpad.net/cinder/+bug/2017575> - *Status*: Waiting on <hillpd> keep the conversation on the Launchpad bug or propose a WIP patch to discuss the changes on the patch. -- Sofía Enriquez she/her Software Engineer Red Hat PnT <https://www.redhat.com> IRC: @enriquetaso @RedHat <https://twitter.com/redhat> Red Hat <https://www.linkedin.com/company/red-hat> Red Hat <https://www.facebook.com/RedHatInc> <https://www.redhat.com>

1 0

[nova][ptg][ops] Please collect your thoughs and wishlists for the Forum and the PTG !
by Sylvain Bauza 07 Jun '23

07 Jun '23

Hey folks and especially operators, As a reminder, we will have multiple opportunities during the next week for discussing about some topics : - we will have on Tuesday a general 30-min contributors Meet&Greet Forum session where operators and developers will be. If you want to attend this session and you have some questions or if you want to explain about your problems, you can provide those in the meet&greet etherpad : https://etherpad.opendev.org/p/nova-vancouver2023-meet-and-greet - we will also have a 2-day PTG on Wednesday and Thursday where operators and contributors on a table (#24) can discuss about everything that's in the physical PTG agenda that we will have in the below etherpad : https://etherpad.opendev.org/p/vancouver-june2023-nova The more we are able to collect insights, the better the Summit will be. Thanks folks and hope to see the most of you in Vancouver face-to-face ! -Sylvain

1 0

[kolla] IRC meeting cancelled today
by Bartosz Bezak 07 Jun '23

07 Jun '23

Hello, Unfortunately I have conflicting meetings and I am unable to run the IRC meeting today, let’s cancel it today. Best regards, Bartosz Bezak

1 0

[openstack-ansible] Tuesday June 13 meeting is CANCELLED
by Dmitriy Rabotyagov 06 Jun '23

06 Jun '23

Hi folks, Since some members will be attending OpenInfra Summit and as we are having a PTG session on Wednesday, weekly meeting on Tuesday, June 13 is cancelled.

1 0

[ptg][openstack-ansible] Upcoming hybrid PTG and operator hours
by Dmitriy Rabotyagov 06 Jun '23

06 Jun '23

Hi everyone, I'm glad to announce that OpenStack-Ansible team is going to have a hybrid PTG during the OpenInfra Summit in Vancouver. PTG will happen on Wednesday, June 14, 09:40 - 11:30 local time or 16:45 - 18:30 UTC For those who will be on-site: we have table number 23 booked in the PTG room (Ballroom A?) For those who can not make it to the summit, we have a Zoom room prepared [1] Moreover, we're planning to have an in-person Operator Hours session on Thursday, June 15, at 11:40 - 12:50, in an hour after the Project on-boarding session. So if you have more questions or wanna continue discussion or just can't make it to the Project on-boarding due to some conflict - you're warmly welcome to the operator hours slot. Etherpad with dates and topics that are to be discussed is here [2] [1] https://us06web.zoom.us/j/89099630568?pwd=WnBHYkEzdXJxQ2tLclQ1QXRvNjg5UT09 [2] https://etherpad.opendev.org/p/vancouver-june2023-os-ansible

1 0

Forum Etherpad Collection
by Kendall Nelson 06 Jun '23

06 Jun '23

Hello All! I started a wiki to collect etherpads into as we get them ready for next week. Feel free to add them as you create them! Can't wait to see everyone :) https://wiki.openstack.org/wiki/Forum/Vanvouver2023 <https://wiki.openstack.org/wiki/Forum/Vanvouver2023> -Kendall Nelson

1 0

[nova] Tuesday June 13 meeting is CANCELLED
by Sylvain Bauza 06 Jun '23

06 Jun '23

Some folks (including me) will be traveling for the OpenInfra Summit, so we deferred the nova meeting to the week after. -Sylvain

1 0

[neutron] Neutron meetings next week, Vancouver PTG
by Rodolfo Alonso Hernandez 06 Jun '23

06 Jun '23

Hello Neutrinos: As commented today during the Neutron meeting, next week we are cancelling all Neutron meetings (team, CI and drivers) due to the Vancouver PTG. See you there!

1 0

[qa] No office hour June 13th
by Martin Kopec 06 Jun '23

06 Jun '23

Hello everyone, we're cancelling our office hour on June 13th due to the OpenInfra Summit happening that week. If there is anything you would like to discuss in person in Vancouver, feel free to add it to the agenda [1]. The next office hour will be held on June 20th, 15:00 UTC as usual [2]. [1] https://etherpad.opendev.org/p/vancouver-june2023-qa [2] https://wiki.openstack.org/wiki/Meetings/QATeamMeeting Thanks, -- Martin Kopec Principal Software Quality Engineer Red Hat EMEA IM: kopecmartin

1 0

[ptg][qa] Planning for the upcoming June 2023 PTG
by Martin Kopec 06 Jun '23

06 Jun '23

Hello everyone, me and Ghanshyam will be present at the OpenInfra summit next week. If you have any topic you would like to discuss, feel free to add it to the etherpad [1]. Based on the number of topics we'll reserve a table and time accordingly. [1] https://etherpad.opendev.org/p/vancouver-june2023-qa Thanks, -- Martin Kopec Principal Software Quality Engineer Red Hat EMEA IM: kopecmartin <https://red.ht/sig>

1 0

OpenStack informations
by Imene Hessas 06 Jun '23

06 Jun '23

Greetings , As a curious person and a cloud enthusiast , I started recently documenting myself about OpenStack, learned about its components , methods of deployments .. etc And now am in front of an essential question : is there a lightweight version of Openstack ? Since I noticed that it requires significant hardware resources, including compute, storage, and networking infrastructure, to run efficiently. I'll be waiting patiently for your response ! Thank you.

2 1

[nova] Nova Spec review day next Tuesday 6 June
by Sylvain Bauza 06 Jun '23

06 Jun '23

Hey Nova community, As a reminder, you can find the Nova agenda for the 2023.2 Bobcat release here https://releases.openstack.org/bobcat/schedule.html As you can see, we plan to do a round of reviews for all the open specifications in the openstack/nova-specs repository by next Tuesday June 6th. If you're a developer wanting to propose a new feature in Nova and you have been said to provide a spec, or if you know that you need to create a spec, or if you already have an open spec, please make sure to upload/update your file before next Tuesday so we'll look at it. Also, if you can look again on your spec during the day, it would be nice as we could try to discuss your spec during this day. Thanks, -Sylvain

2 1

Nested template
by Antony P 06 Jun '23

06 Jun '23

Dear team, I have 2 template test1.yaml test2.yaml how to run this 2 templates as single template. what is steps i have to follow *--Warm Regards* *Antony P* *Jr. DevOps Engineer* antony(a)edgebricks.com Mob No: +919498079898 www.edgebricks.com

5 4

[devstack] Recent change breaks cloning with GIT_DEPTH setting
by Nell Jerram 06 Jun '23

06 Jun '23

FYI, devstack commit b0bd5b92 doesn't work with a GIT_DEPTH=1 setting. That commit basically changed from git clone ... --branch <BRANCH> to git clone ... git checkout <BRANCH> So it's easy for the desired <BRANCH> to be unavailable if GIT_DEPTH is limited. Best wishes - Nell

2 2

[neutron][ovn] The implementation status of DVR for port forwarding in OpenStack.
by 韩光宇 06 Jun '23

06 Jun '23

Hello I previously learned that distributed SNAT has not been implemented in ML2/OVS yet, and traffic for floating IP port forwarding still goes through the network node. Therefore, I tried using ML2/OVN. However, I found that the traffic for floating IP port forwarding still goes through the network node. Does anyone know if this is normal or if OVN has implemented DVR for port forwarding? Or is it because there is an issue with my configuration? I deploy a master ubuntu env by kolla, and I had set dvr of ovn. ``` # in /etc/kolla/globals.yml neutron_plugin_agent: "ovn" neutron_ovn_distributed_fip: "yes" ``` I would like to know if OVN currently implements DVR for port forwarding. If not, what can I do to distribute the traffic load for port forwarding of OpenStack? In my use case, I need to create a large number of port forwarding rules, which puts a lot of pressure on the network node. I will appreciate any help or advice. Best regards, Han Guangyu

2 1

[puppet] puppet module improvements
by Benedikt Trefzer 05 Jun '23

05 Jun '23

Hi all I use the openstack puppet modules to deploy openstack. I'd like to suggest some improvements to the modules and like to know what the community thinks about: 1.) use proper types for parameters Parameter validation is done with 'validate_legacy...' instead of defining the class/resource parameter with a proper type all over the code. I cannot imaging of any advantage not using proper type definitions. Instead using typed parameters would be more efficient an code readability would increase. 2.) params.pp This is the legacy way to define parameter defaults for different OS's. In the modern puppet world a module specific hiera structure is used, which eliminates the need of params.pp class (with inheritance and include). The usage of hiera improves readability and flexibility (every parameter can be overwritten on request, eg. change of packages names etc.) This also eliminate the restriction that the modules can only be used by certain OS'es (osfamily 'RedHat' or 'Debian'). 3.) Eliminate "if OS=='bla' {" statements in code These statements make the code very inflexible. It cannot be overruled if necessary (eg. if I use custom packages to install and do not need the code provided in the if statement). Instead a parameter should be used with a default provided in hiera. Since there is lot of code to change I do not expect this to be done in a single commit (per module) but in steps probably in more than one release cycle. But defining this as best practice for openstack puppet modules and start using above in new commits would bring the code forward. Finally: These are suggestions open for discussion. In no way I like to critic the current state of the puppet modules (which is quite good, but a bit legacy) or the people working on the modules. This is just a feedback/suggestion from an operator using the modules on a daily basis. Regards Benedikt Trefzer

4 4

[tc] Technical Committee next weekly meeting on June 6, 2023
by Nikolla, Kristi 05 Jun '23

05 Jun '23

Hi all, This is a reminder that the next weekly Technical Committee meeting is to be held on Tuesday, Jun 6, 2023 at 1800 UTC on Zoom. Meeting link and agenda can be found at https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting Please find below the current agenda for the meeting. * Roll call * Follow up on past action items ** knikolla Book timeslots for PTG in Vancouver ** knikolla Prepare PTG agenda for Vancouver ** knikolla To fix link redirect to release from docs ** knikolla Finish TC Tracker 2023.2 * Open Infra Summit and PTG in Vancouver, next week * Gate health check * Broken docs due to inconsistent release naming * Open Discussion and Reviews ** https://review.opendev.org/q/projects:openstack/governance+is:open Thank you, Kristi Nikolla

1 0

[ceph-users] Quuncy release - radosGW integration with Keystone
by fsbiz＠yahoo.com 05 Jun '23

05 Jun '23

Hi folks, My ceph cluster with Quincy and Rocky9 is up and running.But I'm having issues with radosGW authenticating with keystone. Was wondering if I'm missed anything in the configuration. From the debug logs below, it appears that radosgw is still trying to authenticate withSwift instead of Keystone.Any pointers will be appreciated. thanks, Fred Here is my configuration. # ceph config dump | grep rgw client advanced debug_rgw 20/20 client advanced rgw_keystone_accepted_roles admin,user * client advanced rgw_keystone_admin_domain Default * client advanced rgw_keystone_admin_password <secret> * client advanced rgw_keystone_admin_project service * client advanced rgw_keystone_admin_user ceph-ks-svc * client advanced rgw_keystone_api_version 3 client advanced rgw_keystone_implicit_tenants false * client advanced rgw_keystone_token_cache_size 0 client basic rgw_keystone_url <Identity URL> * client advanced rgw_s3_auth_use_keystone true client advanced rgw_swift_account_in_url true client basic rgw_thread_pool_size 512 client.rgw.s_rgw.dev-ipp1-u1-control01.ojmddc basic rgw_frontends beast port=7480 * client.rgw.s_rgw.dev-ipp1-u1-control02.adnjrx basic rgw_frontends beast port=7480 Here's the debug log. If I interpret it correctly, it is trying to do a swift authentication and failing.Am I missing any configuration for Keystone based authentication ? Jun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: beast: 0x7fddeb8e7710:10.117.53.10 - - [03/Jun/2023:18:47:03.060 +0000] "GET/swift/v1/AUTH_c668ed224e434c88a9e0fce125056112?format=json HTTP/1.1" 401 119 -"openstacksdk/0.52.0 keystoneauth1/4.0.0 python-requests/2.22.0 CPython/3.8.10"- latency=0.000000000s Jun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: HTTP_ACCEPT=*/*Jun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: HTTP_ACCEPT_ENCODING=gzip,deflateJun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: HTTP_CONNECTION=closeJun 03 11:47:03 dev-ipp1-u1-control02.radosgw[2802861]:HTTP_HOST=dev-ipp1-u1-object-storeJun 03 11:47:03 dev-ipp1-u1-control02radosgw[2802861]: HTTP_USER_AGENT=openstacksdk/0.52.0keystoneauth1/4.0.0 python-requests/2.22.0 CPython/3.8.10Jun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: HTTP_VERSION=1.1 Jun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]:HTTP_X_AUTH_TOKEN=gAAAAABke4qn779UQ_XMz0EDL3P3TgjBQsGG6p-MNhviJxLZTuMTnTDmpT5Yfi9UpgO_T3LOOsPjQAw6zoMUIaC22wPeryp5x-UumB3XwXOWp-qSXLbuN3b9oj_Qg5kCZWA0waWNRHzQ1mwtlEmmpTgvTXbU5V1ym6hEBOn6Q3RWhn34Hj3cF9oJun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: HTTP_X_FORWARDED_FOR=10.117.148.3Jun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: QUERY_STRING=format=jsonJun 03 11:47:03 dev-ipp1-u1-control02.radosgw[2802861]: REMOTE_ADDR=10.117.53.10 Jun 03 11:47:03 dev-ipp1-u1-control02.radosgw[2802861]: REQUEST_METHOD=GETJun 03 11:47:03 dev-ipp1-u1-control02.radosgw[2802861]:REQUEST_URI=/swift/v1/AUTH_c668ed224e434c88a9e0fce125056112?format=jsonJun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]:SCRIPT_URI=/swift/v1/AUTH_c668ed224e434c88a9e0fce125056112 Jun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: SERVER_PORT=7480Jun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: ====== starting new requestreq=0x7fddeb8e7710 ===== Jun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: req 41483251800463850450.000000000s initializing for trans_id = tx000003991cfc5c1791f95-00647b8aa7-30c56-default Jun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: req 41483251800463850450.000000000s rgw api priority: s3=8 s3website=7Jun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: req 41483251800463850450.000000000s host=dev-ipp1-u1-object-store Jun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: req 41483251800463850450.000000000s subdomain= domain= in_hosted_domain=0 in_hosted_domain_s3website=0 Jun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: req 41483251800463850450.000000000s final domain/bucket subdomain= domain= in_hosted_domain=0in_hosted_domain_s3website=0 s->info.domain=s->info.request_uri=/swift/v1/AUTH_c668ed224e434c88a9e0fce125056112 Jun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: req 41483251800463850450.000000000s name: format val: jsonJun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: req 41483251800463850450.000000000s ver=v1 first= req= Jun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: req 41483251800463850450.000000000s handler=29RGWHandler_REST_Service_SWIFT Jun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: req 41483251800463850450.000000000s getting op 0 Jun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: req 41483251800463850450.000000000s get_system_obj_state: rctx=0x7fddeb8e6790obj=default.rgw.log:script.prerequest. state=0x55f743b97720 s->prefetch_data=0 Jun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: req 41483251800463850450.000000000s cache get: name=default.rgw.log++script.prerequest. : hit (negative entry) Jun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: req 41483251800463850450.000000000s swift:list_buckets scheduling with throttler client=3 cost=1Jun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: req 41483251800463850450.000000000s swift:list_buckets op=29RGWListBuckets_ObjStore_SWIFTJun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: req 41483251800463850450.000000000s swift:list_buckets verifying requester Jun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: req 41483251800463850450.000000000s swift:list_buckets rgw::auth::swift::DefaultStrategy: tryingrgw::auth::swift::TempURLEngine Jun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: req 41483251800463850450.000000000s swift:list_buckets rgw::auth::swift::TempURLEngine denied with reason=-13 Jun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: req 41483251800463850450.000000000s swift:list_buckets rgw::auth::swift::DefaultStrategy: tryingrgw::auth::swift::SignedTokenEngine Jun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: req 41483251800463850450.000000000s swift:list_buckets rgw::auth::swift::SignedTokenEngine denied with reason=-1 Jun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: req 41483251800463850450.000000000s swift:list_buckets rgw::auth::swift::DefaultStrategy: tryingrgw::auth::swift::SwiftAnonymousEngine Jun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: req 41483251800463850450.000000000s swift:list_buckets rgw::auth::swift::SwiftAnonymousEngine denied withreason=-1 Jun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: req 41483251800463850450.000000000s swift:list_buckets Failed the auth strategy, reason=-1 Jun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: failed to authorize requestJun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: req 41483251800463850450.000000000s op->ERRORHANDLER: err_no=-1 new_err_no=-1Jun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: req 41483251800463850450.000000000s get_system_obj_state: rctx=0x7fddeb8e6790obj=default.rgw.log:script.postrequest. state=0x55f743b97960 s->prefetch_data=0 Jun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: req 41483251800463850450.000000000s cache get: name=default.rgw.log++script.postrequest. : hit (negative entry) Jun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: req 41483251800463850450.000000000s swift:list_buckets op status=0 Jun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: req 41483251800463850450.000000000s swift:list_buckets http status=401

1 0

[publiccloud-sig] Reminder - next meeting June 7th - 0700 UTC
by Felix Kronlage-Dammers 05 Jun '23

05 Jun '23

Hi everyone, on Wednesday the next meeting of the public cloud sig is going to happen. We meet on IRC in #openstack-operators at 0700 UTC. A preliminary agenda can be found in the pad: https://etherpad.opendev.org/p/publiccloud-sig-meeting See also here for all other details: https://wiki.openstack.org/wiki/PublicCloudSIG read you on 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

swift container retention
by Geert Geurts 05 Jun '23

05 Jun '23

Hallo, I've gotten the assignment to implement a backup solution using openstack swift containers. What we want is that the files of customers are kept in the customers own container and for those files to retain their versions on updates of the file. So far so good, this is all possible, and extensively documented online. Now, the second part is more complicated it appears where I thougth this would be a quite common usage example of object storage. I cannot find how I can automagically delete versions of files that are older then X days. There is the X-delete-after header, but this header needs to be added for each transaction. What I want is for all objects in a container to get deleted after X days without having to add a header once the object is uploaded. Does anyone have suggestions on how I could implement this requirement? Please find below a grafical repesentation of what I want Versioning disabled Automated add headers delete-after Versioning enabled Usage on the account of LF Usage on the account of client │ │ │ │ │ │ ▼ ▼ ┌────────────────────────┐ ┌────────────────────────┐ │ │ │ │ │ Versions-container │ │ Current-container │ │ │ │ │ ├────────────────────────┤ ├────────────────────────┤ │ │ │ │ │File1 v123456 │ │ File1 │ │File1 v567899 │ │ File2 │ │ │ │ File3 │ │File3 v234567 │ │ ... │ │ │ │ FileN │ └────────────────────────┘ └─────────────┬──────────┘ ▲ │ │ │ └────────────────────────────────────────┘ Modifications cause current to be moved to Versioned-container Best regards, Geert

2 1

Kubernetes Conformance 1.24 + 1.25
by Kendall Nelson 05 Jun '23

05 Jun '23

Hello All! First of all, I want to say a huge thanks to Guilherme Steinmuller for all his help ensuring that OpenStack Magnum remains Kubernetes Certified [1]! We are certified for v1.24! However, in digging into the set of conformance tests this round, it appears that we will not be able to get 1.25 certified with the current Magnum. This means that in May when we have to re-cert (every 3 months they reach an EOL because that's k8s release cadence) we will not be able to maintain this which is the other part of why I wanted to write this email - to raise awareness and ask for help digging into what needs to happen to make sure we can retain this. Tangentially related, Guilherme has posted a patch with documentation for how to run the conformance tests for yourself and it could use some reviews [2]. And one last thing, I have begun conversation with the opendev folks about what it might take to setup jobs to run the conformance tests periodically so that we don't have to manually run them when it's time to recert. I am planning on submitting a forum topic for this for those interested :) Long live LOKI! - Kendall Nelson [1] https://github.com/cncf/k8s-conformance/pull/2446 [2] https://review.opendev.org/c/openstack/magnum/+/849156

5 10

[neutron] Bug Deputy May 29 - June 4
by Miro Tomaska 05 Jun '23

05 Jun '23

Hello All! Here is bug report from May 29nd to June 4th, Undecided bugs needs further triage: *Critical:-* *High:-* - https://bugs.launchpad.net/neutron/+bug/2021457 The firewall group without any port in active status Assigned to ZhouHeng - https://bugs.launchpad.net/neutron/+bug/2022059 Trunk can be deleted when the parent port is bound to a VM Assigned to Rodolfo Alonso *Medium:-* - https://bugs.launchpad.net/neutron/+bug/2021968 [OVN-BGP-AGENT] Expose subnet CIDR information on NB DB Assigned to Lucas Alvares Gomez - https://bugs.launchpad.net/neutron/+bug/2022070 "neutron-ovn-rally-task" timing out randomly Assigned to Rodolfo Alonso *Low:-* *- *https://bugs.launchpad.net/neutron/+bug/2022043 APIs for resources which don't have project_id still requires it in the API definition Assigned Slawek Kaplonski *Wishlist:-* *Undecided:-* https://bugs.launchpad.net/neutron/+bug/2022058 - l3ha and distributed router extra attributes do not reflect OVN state https://bugs.launchpad.net/neutron/+bug/2022360 - SecurityGroup deletion causes bulk_pull of SG rules by all the agents - requested more info Thank you Miro Tomaska

1 0

[ironic] No Meeting June 12th
by Jay Faulkner 05 Jun '23

05 Jun '23

Hi all, Due to proximity to OpenInfra Summit/Forum/PTG events, the Ironic meeting for June 12th will be cancelled. The next Ironic meeting will be Monday, June 19th. See many of you in Vancouver! Thanks, Jay Faulkner Ironic PTL

1 0

[forum] [k8s] Kubernetes on OpenStack
by Michał Dulko 05 Jun '23

05 Jun '23

Hi folks, With Matt we're holding a Forum session to discuss Kubernetes on OpenStack in Vancouver. We'd like the users, admins and developers of the projects to connect and talk about challenges, pain points and best practices. The agenda is being gathered in the etherpad [1], please do not hesitate to add any topics that you would like to discuss during the meeting. See you in Vancouver! Thanks, Michał [1] https://etherpad.opendev.org/p/openinfra-2023-kubernetes-on-openstack

1 0

Openstack Ansible
by Gk Gk 05 Jun '23

05 Jun '23

Hi All, We have an OSA setup. When I check the usage of filesystem of any container using "df" command, it shows the lvm partitions of the underlying host as well as shown below: -- Filesystem Size Used Avail Use% Mounted on /dev/mapper/lxc1-lv_root 86G 60G 22G 74% / none 492K 4.0K 488K 1% /dev /dev/mapper/lxc-openstack 493G 136G 334G 29% /var/log tmpfs 252G 0 252G 0% /dev/shm tmpfs 51G 88K 51G 1% /run tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs 252G 0 252G 0% /sys/fs/cgroup example:gfs-repo 86G 67G 16G 82% /var/www/repo --- How to exclude the host partitions such that df only reports the container usage only ? Thanks Kumar

2 3

[heat] Plan for upcoming June 2023 PTG
by Takashi Kajinami 04 Jun '23

04 Jun '23

Hello, I'm attending the upcoming OpenInfra Summit @ Vancouver, so would like to moderate some Heat sessions in PTG. Unfortunately we have limited number of core reviewers attending this time. We discussed most of the important items during the previous vPTG. So I'm planning to have open discussion slots mainly to hear feedback from users/operators/etc. If you are interested, please add your name and topics to the etherpad . https://etherpad.opendev.org/p/vancouver-june2023-heat I've reserved slots from 11:00 to 12:50 on Wednesday, but we can be flexible. Please let me know if anyone is interested but that slot does not work. Thank you, Takashi Kajinami

1 0

[horizon] Cancelling next weekly meeting on 7th June
by vishal manchanda 04 Jun '23

04 Jun '23

Hello Team, As agreed, during the last weekly meeting, we are canceling our next weekly meeting on 7th June. I am on vacation for next complete week with limited or no access to internet. Please reach out to horizon core team if need any help. Thanks & regards, Vishal Manchanda

1 0

[charms] OpenStack Charms 2023.1 (Antelope) release is now available
by Peter Matulis 02 Jun '23

02 Jun '23

The 2023.1 (Antelope) release of the OpenStack Charms is now available. Please see the release notes for full details: https://docs.openstack.org/charm-guide/latest/release-notes/2023.1-antelope… == Highlights == * OpenStack Antelope OpenStack Antelope is now supported on Ubuntu 22.04 LTS (via UCA) and Ubuntu 23.04 natively. * New charm: ironic-dashboard This new charm integrates the Ironic Dashboard into the OpenStack Dashboard. * Service user password rotation The keystone, mysql-innodb-cluster, and rabbitmq-server charms have gained actions to assist with rotating the passwords of OpenStack service users. Two actions are provided for each of these charms (to list usernames and rotate their passwords). * New features for the ironic-conductor charm The ironic-conductor charm has acquired a few new abilities. It can now enable hardware specific options in the Ironic Conductor service. It also now supports custom timeouts for when requests are made to download install images. * Documentation updates Regular improvements and bug fixes. A new page on Network spaces was landed. == OpenStack Charms team == The OpenStack Charms team can be contacted via real time chat: https://chat.charmhub.io/charmhub/channels/openstack-charms The Juju user forum is also popular for diagnosing technical issues: https://discourse.charmhub.io/c/juju/ == Thank you == Lots of thanks to the 24 contributors below who squashed bugs, enabled new features, and improved the documentation! Alex Kavanagh Arif Ali Bas de Bruijne Billy Olsen Chris MacNaughton Corey Bryant Dmitrii Shcherbakov Edward Hope-Morley Felipe Reyes Frode Nordahl Gabriel Cocenza Guillaume Boutry Hemanth Nakkina James Page Jorge Merlino Liam Young Marcus Boden Martin Kalcok Neil Campbell Olivier Dufour-Cuvillier Peter Matulis Simon Dodsley Tiago Pasqualini Trent Lloyd -- OpenStack Charms Team

1 0

[nova] hw:numa_nodes question
by hai wu 02 Jun '23

02 Jun '23

Is there any concern to enable 'hw:numa_nodes=1' on all flavors, as long as that flavor can fit into one numa node?

4 18

RDO Ice Cream Social at OpenInfra Summit
by Amy Marrich 02 Jun '23

02 Jun '23

Join members of the community for ice cream after the Marketplace Mixer on Wednesday at Soft Peaks in Gastown! Soft Peaks is known for using organic milk and their unique topics! For those with dairy related dietary needs who register we will have an alternative for you so don't feel left out! https://eventyay.com/events/231a963f

1 1

[neutron] Neutron drivers meeting
by Rodolfo Alonso Hernandez 02 Jun '23

02 Jun '23

Hello Neutrinos: Please remember we have the Neutron drivers meeting today at 14:00 UTC. The agenda [1] has one topic: * https://bugs.launchpad.net/neutron/+bug/2020823: [RFE] Add flavor/service provider support to routers in the L3 OVN plugin See you later. [1]https://wiki.openstack.org/wiki/Meetings/NeutronDrivers

1 0

[Nova] How to (live-) migrate instances in a server-group with affinity to another host?
by Christian Rohmann 01 Jun '23

01 Jun '23

Hello OpenStack-Discuss, I was wondering how I as an admin can (live-)migrate instances for which the user applied a server-group with affinity. Looking at the API ([1]), there is no (obvious) way to migrate multiple instances or a server-group "en bloc". But migrating a single instance out of a group does result in: > [...] > 2023-06-01 12:20:00.489 6910 INFO nova.scheduler.host_manager > [req-01d9 83eb5 9c8353142098 - default default] Host filter ignoring > hosts: > 2023-06-01 12:20:00.490 6910 INFO nova.filters [req-01d9 83eb5 > 9c8353142098 - default default] Filter ServerGroupAffinityFilter > returned 0 hosts > 2023-06-01 12:20:00.491 6910 INFO nova.filters [req-01d9 83eb5 > 9c8353142098 - default default] Filtering removed all hosts for the > request with instance ID '2476cfdd-9315-4bff-ba3e-d3be5874593f'. > Filter results: ['AvailabilityZoneFilter: (start: 10, end: 10)', > 'ComputeFilter: (start: 10, end: 10)', 'ComputeCapabilitiesFilter: > (start: 10, end: 9)', 'ImagePropertiesFilter: (start: 9, end: 9)', > 'ServerGroupAntiAffinityFilter: (start: 9, end: 9)', > 'ServerGroupAffinityFilter: (start: 9, end: 0)'] > [...] Am I missing something here? Or am I just holding this wrong? Regards Christian [1] https://docs.openstack.org/api-ref/compute/?expanded=force-migration-comple…

4 4

openstack/devstack issue
by syed 01 Jun '23

01 Jun '23

Hi, I was building a system i.e. an orchestrator that includes resources like an ubuntu virtual machine, firecracker micro virtual machine, unikraft unikernel and a storage. It seems that openstack/devstack is capable of orchestration of such a heterogeneous system and could be customized according to the specific needs. I, however, am experiencing a lot of issues when including the resources e.g. when i try to create an ubuntu image and launch it, it results in errors that are quite complex to resolve and so i intend to reach out to the experts so as to resolve these issues at hand. Regards

2 1

[ironic][stable] Proposing EOL of ironic project branches older than Wallaby
by Jay Faulkner 01 Jun '23

01 Jun '23

Hi all, Ironic has a large amount of stable branches still in EM. We need to take action to ensure those branches are either retired or have CI repaired to the point of being usable. Specifically, I'm looking at these branches across all Ironic projects: - stable/queens - stable/rocky - stable/stein - stable/train - stable/ussuri - stable/victoria In lieu of any volunteers to maintain the CI, my recommendation for all the branches listed above is that they be marked EOL. If someone wants to volunteer to maintain CI for those branches, they can propose one of the below paths be taken instead: 1 - Someone volunteers to maintain these branches, and also report the status of CI of these older branches periodically on the Ironic whiteboard and in Ironic meetings. If you feel strongly that one of these branches needs to continue to be in service; volunteering in this way is how to save them. 2 - We seriously reduce CI. Basically removing all tempest tests to ensure that CI remains reliable and able to merge emergency or security fixes when needed. In some cases; this still requires CI fixes as some older inspector branches are failing *installing packages* in unit tests. I would still like, in this case, that someone volunteers to ensure the minimalist CI remains happy. My intention is to let this message serve as notice and a waiting period; and if I've not heard any response here or in Monday's Ironic meeting (in 6 days), I will begin taking action on retiring these branches. This is simply a start; other branches (including bugfix branches) are also in bad shape in CI, but getting these retired will significantly reduce the surface area of projects and branches to evaluate. I know it's painful to drop support for these branches; but we've provided good EM support for these branches for a long time and by pruning them away, we'll be able to save time to dedicate to other items. Thanks, Jay Faulkner

3 5

Add netapp storage in edge site | Wallaby | DCN
by Swogat Pradhan 01 Jun '23

01 Jun '23

Hi, I have a DCN setup and there is a requirement to use a netapp storage device in one of the edge sites. Can someone please confirm if it is possible? And if so then should i add the parameters in the edge deployment script or the central deployment script. Any suggestions? With regards, Swogat Pradhan

2 10

[blazar] Meeting cancelled today
by Pierre Riteau 01 Jun '23

01 Jun '23

Hello, I am unable to run the IRC meeting today, let's cancel. Best wishes, Pierre Riteau (priteau)

1 0

problem with zun not available console in horizon
by МАКАРОВ МАКС 01 Jun '23

01 Jun '23

1 0

CRITICAL! RabbitMQ PackageCloud repos will be not more available from today - affected Openstack-ansible
by Maroš Varchola 01 Jun '23

01 Jun '23

From today, the PackageCloud repos will be not more available from today. Official information: https://github.com/rabbitmq/rabbitmq-server/discussions/8386 BUG on launchpad: https://bugs.launchpad.net/openstack-ansible/+bug/2021410 -- S pozdravom/Yours Sincerely, Maroš Varchola +421 950 401 060 Astrová 6116/2, 071 01 Michalovce, Slovakia marosvarchola(a)sunray.sk ---- Táto správa bola digitálne podpísaná PGP certifikátom/ This message was digitally signed by PGP certificate

5 7

[neutron] New Yoga, Zed and 2023.1 releases
by Rodolfo Alonso Hernandez 01 Jun '23

01 Jun '23

Hello Neutrinos: Please check the new releases proposals for Yoga, Zed and 2023.1: * https://review.opendev.org/c/openstack/releases/+/885030 * https://review.opendev.org/c/openstack/releases/+/885031 * https://review.opendev.org/c/openstack/releases/+/885033 If you find something wrong please comment on the patch. Regards.

1 0

[horizon][stable] [release] Proposal to make stable/stein as EOL
by vishal manchanda 01 Jun '23

01 Jun '23

Hi all, As discussed in yesterday's Horizon weekly meeting[1] on 2023-05-31, I want to announce that the Horizon team decided to move the stable/stein branch as EOL. Consider this mail as an official announcement of that. The gate for horizon stable/stein is failing for the last few months [2]. I would like to know if anyone still wants to keep this branch to be open otherwise, I will propose an EOL patch for this branch. Thanks & Regards, Vishal Manchanda [1] https://meetings.opendev.org/irclogs/%23openstack-horizon/%23openstack-hori… [2] https://review.opendev.org/q/project:openstack%252Fhorizon+branch:stable%25…

1 0

Question About BGP Dynamic Routing, Floating IP, and SNAT
by Alex 31 May '23

31 May '23

Hi Everyone, Hope you are all doing well. I'm a beginner to Openstack and Neutron and now run into an issue about SNAT and shared floating IP. I've already deployed a neutron network which use BGP to announce floating IP to PE (Provider Edge router), and everything works as expected when I assigned the public floating IP (e.g., 123.0.0.10/24) to VMs. But when I tried to use floating IP port-forwarding function with floating IP 123.0.0.20/24 and rule (internal_ip 10.10.10.10, internal_port 5555, external_port 64000), and assign a private IP (10.10.10.10/24) to a VM. The floating IP 123.0.0.20 won't be advertised through BGP. May I have some suggestions about how could I get this fixed, or the neutron just won't work this way? FYI, 1. Per my understanding, the port_forwardings rule will make the port acts like a SNAT role and forward any packets that reached to it with destination 123.0.0.20:64000 to the private IP 10.10.10.10/24. 2. The IP address could be reached in the neutron network. 3. PE IP address, CE IP address, and floating IP gateway are using the same subnet A and subnet pool (192.168.123.0/24), while floating IP belongs to subnet B and subnet pool (123.0.0.0/24), both subnets belong to provider network. 4. Only floating IP that assigned to the specific VM will be advertised to PE through BGP 5. Floating IP that assigned to port of a router in the neutron network won't be advertised, even the IP is activated and is reachable internally. Sincerely, Alex

1 0