- openstack-discuss - lists.openstack.org

Fwd: [Forum] Meet the Projects Session!
by Kendall Nelson 03 Jun '22

03 Jun '22

Hello :) I wanted to take a moment to invite project maintainers, core contributors, PTLs, governance officials, etc to a meet the projects (projects being the OIF top level ones- Kata, Zuul, OpenStack, StarlingX, and Airship) session during the Forum at the upcoming Summit in Berlin. It will take place Tue, June 7, 11:20am - 12:30pm local in A - A06. The idea is to gather in a single place so that newer members of the community or people unfamiliar with the project can come and meet some of the active participants and ask questions. It's all really informal so there is no need to prepare anything ahead of time. I realize it is pretty late in everyone's planning their schedules for the summit, but if you have a few minutes to spare to come hang out and meet some people and network, please do! We would love to see you there. -Kendall

5 4

[sdk] openstacksdk 0.99.0 breaks swift object header setting
by Clark Boylan 03 Jun '22

03 Jun '22

Hello, Last week the OpenDev team upgraded Zuul which deployed zuul-executors with openstacksdk==0.99.0 installed. After this, test job logs uploaded to the rackspace swift location were no longer viewable in the Zuul dashboard. The reason for this is these objects did not have properly configured CORS headers any longer. The objects uploaded to OVH appear to have been fine (potentially because the headers are not required for OVH). Today we downgraded the version of openstacksdk on the zuul-executors to 0.61.0 and the rackspace uploaded job log objects have functional CORS headers again. For this reason we're fairly confident that something about the 0.99.0 release is impacting the setting of these headers. The code that does these uploads with openstacksdk can be found here [0]. I suspect that the problem is going to be related to this header set on line 227 [1]. In particular that appears to be rackspace specific and this issue is rackspace specific under 0.99.0. However, I wasn't able to find anything in openstacksdk that would have a problem with this. Does anyone else have ideas? I'm somewhat concerned that this represents a class of data loss (metadata is going missing) for swift object uploads. Additionally, we rely on setting the x-delete-after header to timeout, expire, and prune our logs in swift [2]. If there is a general problem with 0.99.0 setting headers on objects it is possible that all of the objects we created using 0.99.0 do not have this metadata set and will leak in their swift containers. [0] https://opendev.org/zuul/zuul-jobs/src/commit/e69d879caecb454c529a7d757b80a… [1] https://opendev.org/zuul/zuul-jobs/src/commit/e69d879caecb454c529a7d757b80a… [2] https://opendev.org/zuul/zuul-jobs/src/commit/e69d879caecb454c529a7d757b80a…

3 7

[ironic] No weekly meeting next week (June 6)
by Iury Gregory 02 Jun '22

02 Jun '22

Hello ironicers, As you probably already know, next week is the Open Infrastructure Summit in Berlin and some of us will be at the event. We will resume our weekly meeting on June 13. Thanks! -- *Att[]'sIury 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

[release] Release countdown for week R-17, Jun 06 - 10
by Előd Illés 02 Jun '22

02 Jun '22

Development Focus ----------------- The Zed-2 milestone will happen in next month, on July 14th, 2022. Zed-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/ <https://releases.openstack.org/zed/schedule.html>zed <https://releases.openstack.org/zed/schedule.html>/schedule.html <https://releases.openstack.org/zed/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/ <https://opendev.org/openstack/releases/src/branch/master/deliverables/zed>zed <https://opendev.org/openstack/releases/src/branch/master/deliverables/zed> 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/ <https://releases.openstack.org/zed/schedule.html#z-mf>zed <https://releases.openstack.org/zed/schedule.html#z-mf>/schedule.html# <https://releases.openstack.org/zed/schedule.html#z-mf>z <https://releases.openstack.org/zed/schedule.html#z-mf>-mf <https://releases.openstack.org/zed/schedule.html#z-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 -------------------------- Zed-2 Milestone: July 14th, 2022 OpenInfra Summit: June 7-9, 2022 (Berlin) Előd Illés irc: elodilles

1 0

[dev][docs][security-sig] Retiring security-analysis process and repo
by Jeremy Stanley 02 Jun '22

02 Jun '22

In 2016, what was then the Security Project Team embarked on an effort to centrally collect security analyses of OpenStack components. It accumulated a total of two, one for Barbican as of the Newton release, and another for KeystoneMiddleware as of Pike. The latter was finalized in 2017 and took nearly a year to merge due to already waning enthusiasm and reviewer availability: https://docs.openstack.org/security-analysis Given this effort was effectively abandoned years ago, the Security SIG members agree that the repository should be retired in order to reduce confusion. The vulnerability management oversight requirements were amended in February to remove any reference to this process, and we reached a consensus that this sort of documentation is better off inside the projects which are writing it rather than collected centrally with a disconnected (or in this case absent) group of reviewers and maintainers. This message serves as notice to the community that we will be pushing changes to follow the usual OpenStack repository retirement process for openstack/security-analysis in the coming days. As usual, the final state of the documents will be found in the parent commit of the one which wipes all the old files, but for posterity I'll link it here as well: https://opendev.org/openstack/security-analysis/src/commit/ac43025 Many thanks to those who attempted to provide and review these analyses in years past. The idea of maintaining information on the security risks and considerations for the systems we design is still a good one, and something I hope our contributor community might find more time to focus on in the years to come; but the place to document those things is right alongside the rest of the software's documentation, there's nothing inherently special or different about it. -- Jeremy Stanley

1 0

[all][tc] Technical Committee next weekly meeting on June 2, 2022 at 1500 UTC
by Ghanshyam Mann 02 Jun '22

02 Jun '22

Hello Everyone, The technical Committee's next weekly meeting is scheduled for June 2, 2022, at 1500 UTC. If you would like to add topics for discussion, please add them to the below wiki page by Wednesday, June 1, at 2100 UTC. https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting -gmann

1 1

Resources to learn IT Infrastructure
by Raghav Gururajan 02 Jun '22

02 Jun '22

Hello All, I am stepping into infrastructure side of the IT world and was wondering if any of you could recommend best books, materials or videos for learning? Regards, Raghav "RG" Gururajan.

1 0

Re: Re: [vdi][daas][ops] What are your solutions to VDI/DaaS on OpenStack?
by Ümit Seren 02 Jun '22

02 Jun '22

We are using xpra (https://xpra.org/) together with VirtualGL (https://www.virtualgl.org/) on our virtualized OpenStack based SLURM cluster to support OpenGL accelerated applications such as MorphoGraphX (https://morphographx.org/) for our users. This works pretty well. There was a bit of work involved because it requires an X11 server to run on the compute nodes but once this was done it worked fairly well. Best Ümit On 02.06.22, 01:10, "Andy Botting" <andy(a)andybotting.com> wrote: Hi Radosław, > I am wondering if and how OpenStackers are approaching the subject of > VDI (Virtual Desktop Infrastructure), also nowadays commonly called > DaaS (Desktop as a Service) offering. > To be more specific, I am looking forward to a solution covering both > Linux and Windows desktops, pre-OS screen access optional, > well-integrated (i.e., having automation) with OpenStack Nova, > preferably also with Cinder and Glance, optionally with Keystone > (apart from self-auth of course!) and Heat, 3D acceleration optional > (most of the desktops here don't need it), nice to have read-only > sharing of screen. We just launched a service like this on the Nectar Research Cloud. Like you, I looked around but couldn't find any Open Source projects that would be suitable. In the end, we based ours on a project from the University of Melbourne that did initially support Windows, but we removed some of that support to simplify our codebase as we didn't need it. We called it Bumblebee, and the code is here: https://github.com/NeCTAR-RC/bumblebee It's a Django web app with a Redis-based task scheduler that launches Nova instances, booted from a Cinder volume, cloned from a base OS image. The Django app directly modifies Guacamole's database to create the connections once the OpenStack resources have been provisioned and provides the user with a link that takes them to their desktop. We used Keycloak with OIDC for authentication on the web app and Guacamole and it's fairly seamless transitioning between the two. We did initially look at using Heat, but we wanted to support a workflow of being able to destroy the VM and archive the OS image to Swift (and restore again later if needed) so it was easier to just manage the resources directly. There's no 3D acceleration in our solution yet, but we're planning on looking at things like virtual GPUs later on. Sadly, I'm not going to make it to Berlin either, but I was thinking it might make for a good talk at the next summit. I'm in the process of properly documenting it now, so I don't have much to share at this point, but I'm happy to go into more detail about anything. cheers, Andy

1 0

[all][tc] Lets talk about Flake8 E501
by Miro Tomaska 01 Jun '22

01 Jun '22

Hello All, This is probably going to be a hot topic but I was wondering if the community ever considered raising the default 79 characters line limit. I have seen some places where even a very innocent line of code needs to be split into two lines. I have also seen some code where I feel like variable names were abbreviated on purpose to squeeze everything into one line. How does the community feel about raising the E501 limit to 119 characters? The 119 character limit is the second most popular limit besides the default one. It's long enough to give a developer enough room for descriptive variables without being forced to break lines too much. And it is short enough for a diff between two files to look OK. The only downside I can see right now is that it's not easy to convert an existing code. So we will end up with files where the new code is 79+ characters and the "old" code is <=79. I can also see an argument where someone might have trouble reviewing a patch on a laptop screen (assuming standard 14" screen) ? Here is an example of one extreme, a diff of two files maxing out at 119 characters https://review.opendev.org/c/opendev/sandbox/+/843697/1..2 Thank you for your time and I am looking forward to this conversation :) -- Miro Tomaska irc: mtomaska Red Hat

9 11

[keystone] how to use v3tokenlessauth
by hai wu 01 Jun '22

01 Jun '22

I could not find any example/usage of v3tokenlessauth, using environment variables. There are no documents to be found. I assume we could need to have this one at least: export OS_AUTH_TYPE="v3tokenlessauth" What other environment variables are required if using this auth type? Would like to use HTTPs x509 auth. This is the only relevant doc found: https://docs.openstack.org/keystone/train/admin/configure_tokenless_x509.ht… [keystone_authtoken] memcached_servers = localhost:11211 cafile = /etc/keystone/ca.pem project_domain_name = Default project_name = service auth_url = https://192.168.0.10/identity/v3 auth_type = v3tokenlessauth certfile = /etc/glance/certs/glance.pem keyfile = /etc/glance/private/glance_private_key.pem But there are no environment variables mentioned in the above doc.

1 0

Novice question
by tim+openstack.org＠coote.org 01 Jun '22

01 Jun '22

Hullo Naïve question follows. Sorry. I’m trying a minimal OS install on a Virtualbox VM on a mac. I’d like to get to the point where I can launch a compute node. I’ve failed with `packstack` and I’m trying `devstack`. Should this work out of the box: ie Spin up a vm with vagrant: I’m using Centos Stream 9 to ensure that I get a current(ish) version of Python. It has 9GB RAM Ensure that SELinux and firewalls are turned off Clone devstack, cd to the directory and run `stack.sh` as user `vagrant` (this fails 1/3 of the time as some repo or other resets a connection. `stack.sh` doesn’t seem to be idempotent as reinvoking it may or may not install and run the OS environment Upload a ssh keypair through the web interface Use the web interface to launch the m1.nano flavor with Cirros image (I think that this flavor is quite new as some of the documentation refers to creating such a flavor with 64MB, whereas this one has 128MB. I did try the 64MB route [with `packstack`] and concluded that at least 96MB was needed and the documentation was wrong. I couldn’t log into launchpad.net <http://launchpad.net/> to report this ☹ At this point the launch process fails with the error message: “Build of instance 157bfa1d-7f8c-4a6c-ba3a-b02fb4f4b6a9 aborted: Failed to allocate the network(s), not rescheduling.” In the web ui Afaict, the vm has enough memory (just: it’s using a bit of swap, but more cache, so it could reclaim that). I’d expected the instance to launch, and I can well believe that I’ve missed something, but the documentation seems to point all over the place for various logs. Should this approach work? Is there an alternative that’s better (e.g. use Ubuntu: I’m not keen on apt/dpkg/.deb based distros as I’ve been tripped up in the past over the dependency handling and systemd integration, so I’ve avoided this, but I can see that Canonical is spending money on OS. But so is IBM/Redhat)? Where can I find info on how to trouble shoot the failing process? tia Tim

3 5

[neutron][networking-ovn] Propose to EOL stable/queens, stable/rocky and stable/stein branches of networking-ovn
by Lajos Katona 01 Jun '22

01 Jun '22

Hi, The Queens, Rocky and Stein branches of networking-ovn see little activity and maintaining them and keeping their jobs running is a big effort. We discussed this topic during the team meeting (see [1]), and agreed to propose stable/queens, stable/rocky and stable/stein branches of networking-ovn End Of Life. I will wait until the end of next week for anyone who would like to step up as maintainer of those branches and who would at least try to fix CI of them. If there will be no volunteers for that, I will EOL those branches in networking-ovn. [1]: https://meetings.opendev.org/meetings/networking/2022/networking.2022-05-31… Lajos Katona (lajoskatona)

1 0

[neutron][tap-as-a-service] Propose to EOL stable/queens, stable/rocky and stable/stein branches of tap-as-a-service
by Lajos Katona 01 Jun '22

01 Jun '22

Hi, The Queens, Rocky and Stein branches of tap-as-a-service see little activity and maintaining them and keeping their jobs running is a big effort. We discussed this topic during the team meeting (see [1]), and agreed to propose stable/queens, stable/rocky and stable/stein branches of tap-as-a-service End Of Life. I will wait until the end of next week for anyone who would like to step up as maintainer of those branches and who would at least try to fix CI of them. If there will be no volunteers for that, I will EOL those branches in tap-as-a-service. [1]: https://meetings.opendev.org/meetings/networking/2022/networking.2022-05-31… Lajos Katona (lajoskatona)

1 0

[neutron][neutron-fwaas] Propose to EOL stable/queens, stable/rocky and stable/stein branches of neutron-fwaas
by Lajos Katona 01 Jun '22

01 Jun '22

Hi, The Queens, Rocky and Stein branches of neutron-fwaas see little activity and maintaining them and keeping their jobs running is a big effort. We discussed this topic during the team meeting (see [1]), and agreed to propose stable/queens, stable/rocky and stable/stein branches of neutron-fwaas End Of Life. I will wait until the end of next week for anyone who would like to step up as maintainer of those branches and who would at least try to fix CI of them. If there will be no volunteers for that, I will EOL those branches in neutron-fwaas. [1]: https://meetings.opendev.org/meetings/networking/2022/networking.2022-05-31… Lajos Katona (lajoskatona)

1 0

[neutron][networking-sfc] Propose to EOL stable/queens, stable/rocky and stable/stein branches of networking-sfc
by Lajos Katona 01 Jun '22

01 Jun '22

Hi, The Queens, Rocky and Stein branches of networking-sfc see little activity and maintaining them and keeping their jobs running is a big effort. We discussed this topic during the team meeting (see [1]), and agreed to propose stable/queens, stable/rocky and stable/stein branches of networking-sfc End Of Life. I will wait until the end of next week for anyone who would like to step up as maintainer of those branches and who would at least try to fix CI of them. If there will be no volunteers for that, I will EOL those branches in networking-sfc. [1]: https://meetings.opendev.org/meetings/networking/2022/networking.2022-05-31… Lajos Katona (lajoskatona)

1 0

[neutron][networking-bagpipe][networking-bgpvpn] Propose to EOL stable/rocky and stable/stein branches of networking-odl
by Lajos Katona 01 Jun '22

01 Jun '22

Hi, The Rocky and Stein branches of networking-bagpipe and networking-bgpvpn see little activity and maintaining them and keeping their jobs running is a big effort. We discussed this topic during the team meeting (see [1]), and agreed to propose stable/rocky and stable/stein branches of networking-bagpipe and networking-bgpvpn End Of Life. I will wait until the end of next week for anyone who would like to step up as maintainer of those branches and who would at least try to fix CI of them. If there will be no volunteers for that, I will EOL those branches in networking-bagpipe and networking-bgpvpn. [1]: https://meetings.opendev.org/meetings/networking/2022/networking.2022-05-31… Lajos Katona (lajoskatona)

1 2

[neutron][networking-odl] Propose to EOL stable/queens, stable/rocky and stable/stein branches of networking-odl
by Lajos Katona 01 Jun '22

01 Jun '22

Hi, The Queens, Rocky and Stein branches of networking-odl see little activity and maintaining them and keeping their jobs running is a big effort. We discussed this topic during the team meeting (see [1]), and agreed to propose stable/queens, stable/rocky and stable/stein branches of networking-odl End Of Life. I will wait until the end of next week for anyone who would like to step up as maintainer of those branches and who would at least try to fix CI of them. If there will be no volunteers for that, I will EOL those branches in networking-odl. [1]: https://meetings.opendev.org/meetings/networking/2022/networking.2022-05-31… Lajos Katona (lajoskatona)

1 0

[cinder] Bug deputy report for week of 06-01-2022
by Sofia Enriquez 01 Jun '22

01 Jun '22

This is a bug report from 05-25-2022 to 06-01-2022. Agenda: https://etherpad.opendev.org/p/cinder-bug-squad-meeting ----------------------------------------------------------------------------------------- Low - https://bugs.launchpad.net/cinder/+bug/1976400 "[Storwize] Fix multiple SVC CLI calls for rc-relationship operations." Fix proposed to master. Wishlist - https://bugs.launchpad.net/cinder/+bug/1975794 "How to configure Cinder to use as much as possible, (post-provision)." Unassigned. - https://bugs.launchpad.net/cinder/+bug/1976331 "Check attachment_specs may lead to poor performance." Unassigned. Cheers, Sofi -- 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

[qa] Cancelling office hour on June 7th
by Martin Kopec 01 Jun '22

01 Jun '22

Hello everyone, QA team is cancelling the next office hour Tuesday June 7th, I'm gonna attend the OpenStack Summit. https://wiki.openstack.org/wiki/Meetings/QATeamMeeting#Agenda_for_next_Offi… Thanks, -- Martin Kopec Senior Software Quality Engineer Red Hat EMEA IM: kopecmartin

1 0

error creating image from volume
by Russell Stather 01 Jun '22

01 Jun '22

Hi Trying to create an image from a volume. Getting this very unhelpful error message. igadmin@ig-umh-maas:~$ openstack image create --volume 57bc3efa-6cdc-4e2d-a0e2-262340cc6180 commvaultimage upload_to_image() got an unexpected keyword argument 'visibility' Anyone seen this before? Thanks Russell

3 2

[neutron] team meeting 7. 06. 2022 cancelled
by Lajos Katona 01 Jun '22

01 Jun '22

Hi, Next week I will attend the Openinfra summit in Berlin, so I can't drive the team meeting. See you online on the week after the summit, or I hope we can meet in Berlin. Lajos Katona (lajoskatona)

1 0

[neutron] Drivers meeting - Friday 2.6.2022 & 9. 6. 2022. - cancelled
by Lajos Katona 01 Jun '22

01 Jun '22

Hi Neutron Drivers! This Friday I will be at a conference and next Friday I will be travelling back from Berlin, so I can't drive these drivers' meetings, let's cancel them. I hope I can meet a few of you in Berlin, and see you online the week after the summit. Lajos Katona (lajoskatona)

1 0

[neutron] CI meeting 7.06.2022 cancelled
by Slawek Kaplonski 01 Jun '22

01 Jun '22

Hi, Next week there is OpenInfra summit in Berlin and some of us will be busy there, so we decided yesterday to cancel next week's Neutron CI meeting. Please ping me on IRC or email if there would be anything urgent related to our CI. See You all on the CI meeting on 14.06.2022 (and in Berlin if You will be there :)) -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0

[kolla][Yoga][ubuntu][kolla-toolbox] kolla-toolbox build image Failed with status: error
by Vishwanath 31 May '22

31 May '22

Hello, I am trying to upgrade Xena to Yoga, as a per-requisite i have upgraded kolla to 14.0.0 and started kolla-build for 14.0.0. *kolla: 14.0.0* *Distributor ID: UbuntuDescription: Ubuntu 20.04.3 LTSRelease: 20.04Codename: focal* *upgrading to : Yoga* *upgrading from: xena* *kolla-build -t source kolla-toolbox -b ubuntu* following is the error message during the image build, issue occurs only on ubuntu whereas centos has no issues, In my environment we use ubuntu. How can this issue be resolved? INFO:kolla.common.utils.kolla-toolbox:ca-certificates is already the newest version (20210119~20.04.2). INFO:kolla.common.utils.kolla-toolbox:Some packages could not be installed. This may mean that you have INFO:kolla.common.utils.kolla-toolbox:requested an impossible situation or if you are using the unstable INFO:kolla.common.utils.kolla-toolbox:distribution that some required packages have not yet been created INFO:kolla.common.utils.kolla-toolbox:or been moved out of Incoming. INFO:kolla.common.utils.kolla-toolbox:The following information may help to resolve the situation: INFO:kolla.common.utils.kolla-toolbox:The following packages have unmet dependencies: INFO:kolla.common.utils.kolla-toolbox: rabbitmq-server : Depends: erlang-base (< 1:25.0) but 1:25.0-1rmq1ppa1~ubuntu20.04.1 is to be installed or INFO:kolla.common.utils.kolla-toolbox: erlang-base-hipe (< 1:25.0) but it is not going to be installed or INFO:kolla.common.utils.kolla-toolbox: esl-erlang (< 1:25.0) but it is not installable INFO:kolla.common.utils.kolla-toolbox: Depends: erlang-crypto (< 1:25.0) but 1:25.0-1rmq1ppa1~ubuntu20.04.1 is to be installed or INFO:kolla.common.utils.kolla-toolbox: esl-erlang (< 1:25.0) but it is not installable INFO:kolla.common.utils.kolla-toolbox: Depends: erlang-eldap (< 1:25.0) but 1:25.0-1rmq1ppa1~ubuntu20.04.1 is to be installed or INFO:kolla.common.utils.kolla-toolbox: esl-erlang (< 1:25.0) but it is not installable INFO:kolla.common.utils.kolla-toolbox: Depends: erlang-inets (< 1:25.0) but 1:25.0-1rmq1ppa1~ubuntu20.04.1 is to be installed or INFO:kolla.common.utils.kolla-toolbox: esl-erlang (< 1:25.0) but it is not installable INFO:kolla.common.utils.kolla-toolbox: Depends: erlang-mnesia (< 1:25.0) but 1:25.0-1rmq1ppa1~ubuntu20.04.1 is to be installed or INFO:kolla.common.utils.kolla-toolbox: esl-erlang (< 1:25.0) but it is not installable INFO:kolla.common.utils.kolla-toolbox: Depends: erlang-os-mon (< 1:25.0) but 1:25.0-1rmq1ppa1~ubuntu20.04.1 is to be installed or INFO:kolla.common.utils.kolla-toolbox: esl-erlang (< 1:25.0) but it is not installable INFO:kolla.common.utils.kolla-toolbox: Depends: erlang-parsetools (< 1:25.0) but 1:25.0-1rmq1ppa1~ubuntu20.04.1 is to be installed or INFO:kolla.common.utils.kolla-toolbox: esl-erlang (< 1:25.0) but it is not installable INFO:kolla.common.utils.kolla-toolbox: Depends: erlang-public-key (< 1:25.0) but 1:25.0-1rmq1ppa1~ubuntu20.04.1 is to be installed or INFO:kolla.common.utils.kolla-toolbox: esl-erlang (< 1:25.0) but it is not installable INFO:kolla.common.utils.kolla-toolbox: Depends: erlang-runtime-tools (< 1:25.0) but 1:25.0-1rmq1ppa1~ubuntu20.04.1 is to be installed or INFO:kolla.common.utils.kolla-toolbox: esl-erlang (< 1:25.0) but it is not installable INFO:kolla.common.utils.kolla-toolbox: Depends: erlang-ssl (< 1:25.0) but 1:25.0-1rmq1ppa1~ubuntu20.04.1 is to be installed or INFO:kolla.common.utils.kolla-toolbox: esl-erlang (< 1:25.0) but it is not installable INFO:kolla.common.utils.kolla-toolbox: Depends: erlang-syntax-tools (< 1:25.0) but 1:25.0-1rmq1ppa1~ubuntu20.04.1 is to be installed or INFO:kolla.common.utils.kolla-toolbox: esl-erlang (< 1:25.0) but it is not installable INFO:kolla.common.utils.kolla-toolbox: Depends: erlang-tools (< 1:25.0) but 1:25.0-1rmq1ppa1~ubuntu20.04.1 is to be installed or INFO:kolla.common.utils.kolla-toolbox: esl-erlang (< 1:25.0) but it is not installable INFO:kolla.common.utils.kolla-toolbox: Depends: erlang-xmerl (< 1:25.0) but 1:25.0-1rmq1ppa1~ubuntu20.04.1 is to be installed or INFO:kolla.common.utils.kolla-toolbox: esl-erlang (< 1:25.0) but it is not installable INFO:kolla.common.utils.kolla-toolbox:E: Unable to correct problems, you have held broken packages. INFO:kolla.common.utils.kolla-toolbox: INFO:kolla.common.utils.kolla-toolbox:Removing intermediate container 7ea161d0dbbd ERROR:kolla.common.utils.kolla-toolbox:Error'd with the following message ERROR:kolla.common.utils.kolla-toolbox:The command '/bin/sh -c apt-get update && apt-get -y install --no-install-recommends build-essential ca-certificates crudini gdisk git jq libffi-dev libssl-dev libxslt1-dev openvswitch-switch python3-dev rabbitmq-server && apt-get clean && rm -rf /var/lib/apt/lists/*' returned a non-zero code: 100 INFO:kolla.common.utils:========================= INFO:kolla.common.utils:Successfully built images INFO:kolla.common.utils:========================= INFO:kolla.common.utils:base INFO:kolla.common.utils:=========================== INFO:kolla.common.utils:Images that failed to build INFO:kolla.common.utils:=========================== ERROR:kolla.common.utils:kolla-toolbox Failed with status: error INFO:kolla.common.utils:========================================= Thanks Vish

2 2

[blazar] IRC meeting of June 2 is cancelled
by Pierre Riteau 31 May '22

31 May '22

Hello, Due to unavailability of the usual participants, the Blazar IRC meeting of June 2 is cancelled. The next meeting will be on June 16. Thanks, Pierre Riteau (priteau)

1 0

[nova][placement] June 7th Meeting is CANCELLED
by Sylvain Bauza 31 May '22

31 May '22

Some of us will be traveling at the OIF Summit so we won't have a quorum for next week. The nova meeting will be back on June 15th. Thanks, -Sylvain

1 0

[qa][stable][gate] Gate fix for stable/ussuri and Tempest pin for stable/victoria
by Ghanshyam Mann 31 May '22

31 May '22

Hello Everyone, You might know the stable/ussuri gate is broken because we dropped the py36 support in zed cycle and Tempest master is used to test it which uses master constraints. To fix this, I am pinning Tempest 26.1.0 in stable/ussuri and tested it with compatible stable/ussuri constraints and tempest plugins. - https://review.opendev.org/q/topic:ussuri-pin-tempest at the same time, I am also pinning tempest in stable/victoria too as it is also in EM state - https://review.opendev.org/q/topic:victoria-pin-tempest Both stable branches pining is working fine and ready to merge now. I have proposed the fixes for a few tempest plugins and stable branches, and request them to merge because we are going to merge the tempest and devstack changes. Below is the complete set of changes we need: QA patches need to go first: - Tempest - https://review.opendev.org/c/openstack/tempest/+/843045 - https://review.opendev.org/c/openstack/tempest/+/843293/2 - Devstack: - https://review.opendev.org/c/openstack/devstack/+/838051 - https://review.opendev.org/c/openstack/devstack/+/843295 - Devstack-plugin-ceph - https://review.opendev.org/c/openstack/devstack-plugin-ceph/+/843354 - https://review.opendev.org/c/openstack/devstack-plugin-ceph/+/843355 (it is +A and waiting for depends-on devstack patch to merge) - Devstack-gate - https://review.opendev.org/c/openstack/devstack-gate/+/843689 Cinder: - https://review.opendev.org/c/openstack/cinder/+/843305 - https://review.opendev.org/c/openstack/cinder/+/843092 (it is +A and waiting for depends-on devstack patch to merge) - https://review.opendev.org/c/openstack/cinder-tempest-plugin/+/843319 (merged) Cyborg: no action is needed - https://review.opendev.org/c/openstack/cyborg-tempest-plugin/+/843329 (it is +A and waiting for depends-on devstack patch to merge) Neutron: need review - https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/838053 Designate: need review - https://review.opendev.org/c/openstack/designate/+/843709 - https://review.opendev.org/c/openstack/designate/+/843710 -gmann

1 1

[cinder] Zed R-18 virtual mid cycle on 1st June
by Rajat Dhasmana 31 May '22

31 May '22

Hello Argonauts, The first Zed mid cycle R-18 will be held on 1st June with the following details: Date: 01st June 2022 Time: 1400-1600 UTC Meeting link: https://bluejeans.com/556681290 Etherpad: https://etherpad.opendev.org/p/cinder-zed-midcycles Please add topics to the etherpad and also mark the date and time on your calendar. Thanks and regards Rajat Dhasmana

1 0

SSL verify failed | Overcloud deploy step 4 | Wallaby | tripleo
by Swogat Pradhan 30 May '22

30 May '22

Hi, I am facing the below issue in step4 ' TASK | Clean up legacy Cinder keystone catalog entries': FATAL | Clean up legacy Cinder keystone catalog entries | undercloud | item={'service_name': 'cinderv2', 'service_type': 'volumev2'} | error={"ansible_index_var": "cinder_api_service", "ansible_loop_var": "item", "changed": false, "cinder_api_service": 0, "item": {"service_name": "cinderv2", "service_type": "volumev2"}, "module_stderr": "Failed to discover available identity versions when contacting https://overcloud.bdxworld.com:13000. Attempting to parse version from URL.\nTraceback (most recent call last):\n File \"/usr/lib/python3.6/site-packages/urllib3/connectionpool.py\", line 677, in urlopen\n chunked=chunked,\n File \"/usr/lib/python3.6/site-packages/urllib3/connectionpool.py\", line 381, in _make_request\n self._validate_conn(conn)\n File \"/usr/lib/python3.6/site-packages/urllib3/connectionpool.py\", line 978, in _validate_conn\n conn.connect()\n File \"/usr/lib/python3.6/site-packages/urllib3/connection.py\", line 371, in connect\n ssl_context=context,\n File \"/usr/lib/python3.6/site-packages/urllib3/util/ssl_.py\", line 384, in ssl_wrap_socket\n return context.wrap_socket(sock, server_hostname=server_hostname)\n File \"/usr/lib64/python3.6/ssl.py\", line 365, in wrap_socket\n _context=self, _session=session)\n File \"/usr/lib64/python3.6/ssl.py\", line 776, in __init__\n self.do_handshake()\n File \"/usr/lib64/python3.6/ssl.py\", line 1036, in do_handshake\n self._sslobj.do_handshake()\n File \"/usr/lib64/python3.6/ssl.py\", line 648, in do_handshake\n self._sslobj.do_handshake()\nssl.SSLError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:897) Can you please suggest a workaround? With regards, Swogat pradhan

2 2

Ansible OpenStack Collection 2.0.0 and OpenStack SDK 1.0.0/0.99.0
by Jakob Meng 30 May '22

30 May '22

Hello contributors and users of the Ansible OpenStack collection [1]! This week a release candidate of the upcoming first major release of OpenStack SDK has been released [2],[3]. It streamlined and improved large parts of its codebase. For example, its Connection interface now consistently uses the Resource interfaces under the hood. This required breaking changes from older SDK releases though. The Ansible OpenStack collection is heavily based on OpenStack SDK. With OpenStack SDK becoming backward incompatible (for the better), so does our Ansible OpenStack collection. We simply lack the devpower to maintain a backward compatible interface in Ansible OpenStack collection across several SDK releases. We already split our codebase into two separate git branches: master and stable/1.0.0. The former will track the upcoming 2.x.x releases of Ansible OpenStack collection which will be compatible with OpenStack SDK 1.x.x (and its rcs 0.99.x) *only*. Our stable/1.0.0 branch will track the current 1.x.x releases of Ansible OpenStack collection which is compatible with OpenStack SDK prior to 0.99.0 *only*. Both branches will be developed in parallel for the time being. Our 2.0.0 release is currently under development and we still have a long way to go. "We" mainly are a couple of Red Hat employees working part-time on the collection. If you use modules of Ansible OpenStack collection and want to help us with porting them to the new SDK, please contact us! If you want to help, please reach out to us (e.g. [7],[8]) and we can give you a quick introduction into everything. We have extensive documentation on why, what and how we are adopting and reviewing the new modules [4], how to set up a working DevStack environment for hacking on the collection [5] and, most importantly, a list of modules where we are coordinating our porting efforts [6]. We are also hanging around on irc.oftc.net/#openstack-ansible-sig and #oooq 😎 [1] https://opendev.org/openstack/ansible-collections-openstack [2] https://github.com/openstack/openstacksdk/releases/tag/0.99.0 [3] https://pypi.org/project/openstacksdk/0.99.0/ [4] https://hackmd.io/szgyWa5qSUOWw3JJBXLmOQ?view [5] https://hackmd.io/PI10x-iCTBuO09duvpeWgQ?view [6] https://hackmd.io/7NtovjRkRn-tKraBXfz9jw?view [7] Rafael Castillo <rcastill(a)redhat.com> (rcastillo) [8] Jakob Meng <mail(a)jakobmeng.de>, <jmeng(a)redhat.com> (jm1) Best, Jakob

2 2

[dev][nova] How to add a column in table of Nova Database
by 韩光宇 30 May '22

30 May '22

Hi, I'm a beginner in OpenStack development. I would like to try modifying by adding a property to the 'Instances' database table. But I didn't find description in the documentation of the data model mechanism and how to extend the database. https://docs.openstack.org/nova/latest/ Now, I know that it involves versined object model and alembic. My question is: What is the process of adding a column to a table in the database? Could someone show me the process of modifying a database table or recommend me the relevant documentation Best wishes, Han

2 2

OpenStack logs on Opensearch - storage problem
by Daniel Pawlik 30 May '22

30 May '22

Hello, In the last few days there is increase amount of CI jobs that are running on Zuul CI gates, where later logs are pushed into the Opensearch cluster [1]. The current cluster storage is almost full, which causes one of the actions to be performed: temporarily changing log retention (currently it is set to 14 days) or removing temporary non-essential logs [2]. I recommend removing not important logs, so if projects leaders could check whether entries related to the project are needed, it would be really helpful. Otherwise, we will temporarily change log retention to 12 days. Dan [1] https://opensearch.logs.openstack.org/_dashboards/app/discover?security_ten… [2] https://opendev.org/openstack/ci-log-processing/src/branch/master/logscrape…

2 2

[sdk][stable][gate] openstacksdk-functional-devstack is broken in stable/ussuri branch
by Ghanshyam Mann 30 May '22

30 May '22

Hello Everyone, With the recent update in 'coverage' constraints to 6.4[1], openstacksdk-functional-devstack is broken in stable/ussuri branch. openstacksdk-functional-devstack running on stable branches use the master SDK and master constraints and in stable/ussuri this job runs on bionic/py3.6 and now fail for 'coverage' 6.4 version conflict. - https://zuul.opendev.org/t/openstack/build/3d3c21d804ec498e957c1c64470c991b… - https://storyboard.openstack.org/#!/story/2010057 As we know requirements generate constraints for py3.8|9 so if we want this job to run with master constraints then it needs to run on compatible python and distro. This is why I am proposing to run this job on focal - https://review.opendev.org/c/openstack/openstacksdk/+/843968 But clark made a good point in IRC that we should test this job with all python versions supported by the stable branch which we can do by testing this job with stable branch constraints and see if still, master SDK runs on those python versions and stable constraints. This is something we can improve if SDK team agrees or have the bandwidth. Anyways please do not recheck on stable/ussuri until this job is fixed (843968 is merged). [1] https://review.opendev.org/c/openstack/requirements/+/843722/3/upper-constr… -gmann

1 1

[ironic] Group Dinner in Berlin - OIS
by Iury Gregory 30 May '22

30 May '22

Hello Ironicers and fellow stackers! Since some of us will be at the Open Infrastructure Summit in Berlin, I think this would be a great opportunity to have a group dinner in Berlin with our friends (like the one we had during the Ironic Mid-Cycle at CERN). I've created an etherpad to track who would be interested in it [1] and also choose the best day. [1] https://etherpad.opendev.org/p/ironic-dinner-ois2022Berlin -- *Att[]'sIury Gregory Melo Ferreira * *MSc in Computer Science at UFCG* *Part of the ironic-core and puppet-manager-core team in OpenStack* *Senior Software Engineer at Red Hat Brasil* *Social*: https://www.linkedin.com/in/iurygregory *E-mail: iurygregory(a)gmail.com <iurygregory(a)gmail.com>*

1 1

[tripleo] stable/wallaby gate blocker for centos-8 standalone - please hold recheck
by Marios Andreou 30 May '22

30 May '22

Hi folks fyi there is a wallaby gate blocker at https://bugs.launchpad.net/tripleo/+bug/1976247 Seems like ansible-role-python_venv_build is trying to install master upper constraints and that is causing a conflict for oslo-db===11.3.0 (comfing via stackviz installation) we are trying to find a workaround but please hold recheck until we do grateful for any pointers or suggestions here or on the launchpad o/ thanks, marios

1 1

[nova][stable] nova-stable-core team changes
by Sylvain Bauza 30 May '22

30 May '22

Hi, After discussing with all our Nova stable cores, we agreed the below : - Welcome Sean Mooney as a new nova-stable-core team member - Welcome Balazs Gibizer as a new nova-stable-core team member - Welcome Stephen Finucane as a new nova-stable-core team member. I would also like to take the opportunity to thank Matt Riedemann and Lee Yarwood for their important and awesome contributions to the Nova Stable Team. Without them, we saw the impact of their misses, hence the above ^. Lee, Matt, you can anytime return to the nova-stable-core team if you express so, but in the meantime, I'll remove you from the members list. Changes to https://review.opendev.org/admin/groups/540,members will occur literally seconds after I send this email. -Sylvain (on behalf of the Nova Stable team)

1 1

[ops][nova] Problems with AggregateMultiTenancyIsolation/AggregateInstanceExtraSpecsFilter after Train --> Yoga update
by Massimo Sgaravatto 30 May '22

30 May '22

Dear all We have the following use case: - reserve 3 hypervisors for VMs with "big" flavors (whatever the users of these instances are) - partition the rest of the hypervisors according to the project (so projects A1,A2..,An can use only subset S1 of hypervisors, project B1,B2,..,Bm can use only subset S2 of hypervisors) We implemented this: 1- by setting an aggregate_instance_extra_spec 'size' property (with value 'normal' or 'big') for each flavor [*] 2- by creating a BigVMs HostAggregate for size=big [**] 3- by creating an HostAggregate for size=normal for each project, such as this one [***] This used to work. A few days ago we updated our infrastructure from Train to Yoga This was an offline Fast Forward Update: we went through the intermediate releases just to do the dbsyncs. Since this update the instantiation of VMs with flavors with the size=big property doesn't work anymore This is what I see in nova-scheduler log: 2022-05-27 08:38:02.058 5273 INFO nova.filters [req-f92c0e38-262a-4d22-a7fd-8874c4265401 e237e43716fb490db5bda4b777835669 32b5d42c02b0411b8ebf2c33079eeecf - default default] Filtering removed all hosts for the request with instance ID '2412e188-9d5f-4812-ad21-195769a3c220'. Filter results: ['AggregateMultiTenancyIsolation: (start: 59, end: 10)', 'AggregateInstanceExtraSpecsFilter: (start: 10, end: 0)'] Only modifying the property of the BigVMs HA using the filter_tenant_id adding the relevant project: [root@cld-ctrl-01 ~]# openstack aggregate show BigVMs | grep prop | properties | filter_tenant_id='32b5d42c02b0411b8ebf2c33079eeecf', size='big' | the scheduling works Specifying each project and keeping the list up-to-date would be a problem. Moreover if I am not wrong there is a maximum length for the property field. Any hints ? I didn't find anything related to this issue in the nova release notes for Openstack releases > Train These are the filters that we enabled: [filter_scheduler] enabled_filters = AggregateMultiTenancyIsolation,AggregateInstanceExtraSpecsFilter,ComputeFilter,ComputeCapabilitiesFilter,ImagePropertiesFilter,ServerGroupAntiAffinityFilter,ServerGro\ upAffinityFilter,PciPassthroughFilter,NUMATopologyFilter Thanks a lot, Massimo [*] E.g. [root@cld-ctrl-01 ~]# openstack flavor show cldareapd.medium | grep prope | properties | aggregate_instance_extra_specs:size='normal' |[root@cld-ctrl-01 ~]# openstack flavor show cloudvenetocloudveneto.40cores128GB25-bigunipd | grep prop | properties | aggregate_instance_extra_specs:size='big' | [**] [root@cld-ctrl-01 ~]# openstack aggregate show BigVMs +-------------------+---------------------------------------------------------------------------------------+ | Field | Value | +-------------------+---------------------------------------------------------------------------------------+ | availability_zone | nova | | created_at | 2018-06-20T06:54:51.000000 | | deleted_at | None | | hosts | cld-blu-08.cloud.pd.infn.it, cld-blu-09.cloud.pd.infn.it, cld-blu-10.cloud.pd.infn.it | | id | 135 | | is_deleted | False | | name | BigVMs | | properties |size='big' | | updated_at | None | | uuid | 4b593395-1c76-441c-9022-d421f4ea2dfb | +-------------------+---------------------------------------------------------------------------------------+ [***] [root@cld-ctrl-01 ~]# openstack aggregate show Unipd-AdminTesting-Unipd +-------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | Field | Value | +-------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | availability_zone | nova | | created_at | 2018-04-12T07:31:01.000000 | | deleted_at | None | | hosts | cld-blu-01.cloud.pd.infn.it, cld-blu-02.cloud.pd.infn.it, cld-blu-05.cloud.pd.infn.it, cld-blu-06.cloud.pd.infn.it, cld-blu-07.cloud.pd.infn.it, cld-blu-11.cloud.pd.infn.it, cld-blu-12.cloud.pd.infn.it, cld-blu-13.cloud.pd.infn.it, cld-blu-14.cloud.pd.infn.it, cld-blu-15.cloud.pd.infn.it, cld-blu-16.cloud.pd.infn.it | | id | 126 | | is_deleted | False | | name | Unipd-AdminTesting-Unipd | | properties | filter_tenant_id='32b5d42c02b0411b8ebf2c33079eeecf', size='normal' | | updated_at | 2018-06-08T09:06:20.000000 | | uuid | 38f6a0d4-77ab-42e0-abeb-57e06ba13cca | +-------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ [root@cld-ctrl-01 ~]#

3 5

[Image Encryption] No meeting today
by Josephine Seifert 30 May '22

30 May '22

Hi, I have a time conflict, so there will be no meeting today. greetings Josephine (Luzi)

1 0

[neutron] Bug deputy report (week starting on 2022-05-23)
by Bernard Cafarelli 30 May '22

30 May '22

Hey neutrinos, I was the bug deputy last week, here are the reported bugs. All high/critical bugs have patches merged (and backports in progress for some), most of the other bugs have patches up for review or merged Critical * Compute tests are failing with failed to reach ACTIVE status and task state "None" within the required time. - https://bugs.launchpad.net/neutron/+bug/1964940 Revert pushed by ykarel https://review.opendev.org/c/openstack/neutron/+/843426 merged High * Open vSwitch agent - does not report to the segment plugin - https://bugs.launchpad.net/neutron/+bug/1975542 DHCP agent issue with routed provider networks, once an agent is running, new segment mappings are not added for new networks Fix by ralonsoh https://review.opendev.org/c/openstack/neutron/+/843294 merged * [sqlalchemy-20] Missing DB context in L2pop methods - https://bugs.launchpad.net/neutron/+bug/1975797 Fix by ralonsoh https://review.opendev.org/c/openstack/neutron/+/843413 merged * ``ovn_revision_bumbers_db._ensure_revision_row_exist`` is mixing DB contexts - https://bugs.launchpad.net/neutron/+bug/1975837 Also fix by ralonsoh https://review.opendev.org/c/openstack/neutron/+/843478 also merged Medium * Neutron RBAC not sharing subnet - https://bugs.launchpad.net/neutron/+bug/1975603 Reported around last week's meeting time, lajos looking into it? * Neutron agent blocks during VM deletion when a remote security group is involved - https://bugs.launchpad.net/neutron/+bug/1975674 Happening with OVS firewall and large number of VMS, suggested fix for deferred https://review.opendev.org/c/openstack/neutron/+/843253 * OVN migration failed due to unhandled error in neutron_ovn_db_sync_util - https://bugs.launchpad.net/neutron/+bug/1975692 Patch by ralonsoh https://review.opendev.org/c/openstack/neutron/+/843263 merged * difference in execution time between admin/non-admin call - https://bugs.launchpad.net/neutron/+bug/1975828 Follow-up to https://bugs.launchpad.net/neutron/+bug/1973349 (that added an index to ports.network_id) Unassigned * ML2 OVN - Creating an instance with hardware offloaded port is broken - https://bugs.launchpad.net/neutron/+bug/1975743 Suggested fix by fnordahl - https://review.opendev.org/c/openstack/neutron/+/843601 Have a nice week! -- Bernard Cafarelli

1 0

[magnum] [xena] [IPv6] What is needed to make dual-stack IPv4/6 work in Magnum-managed Kubernetes 1.21+?
by Namrata Sitlani 29 May '22

29 May '22

Hello All, We run release Xena, and we have deployed Kubernetes version 1.21.10 on Magnum with Fedora CoreOS version 34 and we are trying to have IPv6 support for that Kubernetes cluster, as Kubernetes 1.21 and later versions have dual-stack(IPv4/IPv6) support enabled by default. To achieve the same, we used a network with both IPv4 and IPv6 subnets and we got a successful creation of the cluster. The compute instances of the cluster get both IPv4 and IPv6 addresses, but the master and minion nodes get IPv4 as external IP, and also the container does not get an IPv6 address. Can someone please help us with the information, what changes are required to be made at the magnum client-side to have an IPv6 supported Kubernetes Cluster? Thanks, Namrata

2 2

[all][tc] What's happening in Technical Committee: summary May 27, 2022: Reading: 5 min
by Ghanshyam Mann 27 May '22

27 May '22

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * We had this week's meeting on May 26. Most of the meeting discussions are summarized in this email. Meeting summary logs are available @https://meetings.opendev.org/meetings/tc/2022/tc.2022-05-26-15.00.log.html * Next TC weekly meeting will be on June 3 Thursday at 15:00 UTC, feel free to add the topic on the agenda[1] by June 2. 2. What we completed this week: ========================= * Update governance documentation to try the DPL model for leaderless projects [2]. After election, TC used to search for PTL for leaderless projects but from now onwards we will try if such projects can be moved to the DPL model. 3. Activities In progress: ================== TC Tracker for Zed cycle ------------------------------ * Zed tracker etherpad includes the TC working items[3], we have started the many items. Open Reviews ----------------- * Seven open reviews for ongoing activities[4]. Change OpenStack release naming policy proposal ----------------------------------------------------------- We had a call on Tuesday and figured out how to use the number/name in our development cycle/tooling. I am adding the agreement in resolution[5] and also the documentation about using the release number and names [6]. New release cadence "SLURP" open items -------------------------------------------------- 1. release notes strategy: Brian proposal for ""SLURP release notes approach is up for review[7]. Improve project governance --------------------------------- Slawek has the proposal the framework up and it is under review[8]. New ELK service dashboard: e-r service ----------------------------------------------- A small summary from dpawlik: "the opensearch cluster space seems to be stable right now (there is enough space). For the elastic search recheck, I'm working on ansible role for deploying the e-r and push it to the ci-log-processing project." TripleO team and dpawlik are working on the e-r repo merge. Consistent and Secure Default RBAC ------------------------------------------- We had call on May 24 and discussed the new defaults approach clarification for designate and octavia[9]. Takashi sent a reminder for the feedback about the 'split stack' approach[10]. We will also plan to bring it to the ops meetup in Berlin (Most of us not travelling there but we will find someone who can discuss it). I will schedule the next call and will update the timing on email and wiki[11] 2021 User Survey TC Question Analysis ----------------------------------------------- No update on this. The survey summary is up for review[12]. Feel free to check and provide feedback. Zed cycle Leaderless projects ---------------------------------- No updates on this. Only Adjutant project is leaderless/maintainer-less. We will check Adjutant's the situation again on ML and hope Braden will be ready with their company side permission[13]. Fixing Zuul config error ---------------------------- Requesting projects with zuul config error to look into those and fix them which should not take much time[14][15]. Project updates ------------------- * Add a repository for the Large Scale SIG[16] 4. How to contact the TC: ==================== If you would like to discuss or give feedback to TC, you can reach out to us in multiple ways: 1. Email: you can send the email with tag [tc] on openstack-discuss ML[17]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15 UTC [18] 3. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. [1] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting [2] https://review.opendev.org/c/openstack/governance/+/840363 [3] https://etherpad.opendev.org/p/tc-zed-tracker [4] https://review.opendev.org/q/projects:openstack/governance+status:open [5] https://review.opendev.org/c/openstack/governance/+/843214 [6] https://review.opendev.org/c/openstack/governance/+/841800/ [7] https://review.opendev.org/c/openstack/project-team-guide/+/843457 [8] https://review.opendev.org/c/openstack/governance/+/839880 [9] https://etherpad.opendev.org/p/rbac-zed-ptg#L97 [10] http://lists.openstack.org/pipermail/openstack-discuss/2022-May/028677.html [11] https://wiki.openstack.org/wiki/Consistent_and_Secure_Default_Policies_Popu… [12] https://review.opendev.org/c/openstack/governance/+/836888 [13] http://lists.openstack.org/pipermail/openstack-discuss/2022-March/027626.ht… [14] https://etherpad.opendev.org/p/zuul-config-error-openstack [15] http://lists.openstack.org/pipermail/openstack-discuss/2022-May/028603.html [16] https://review.opendev.org/c/openstack/project-config/+/843534 [17] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [18] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0

[neutron][neutron-vpnaas] retiring train/ussuri/victoria branches
by Mohammed Naser 27 May '22

27 May '22

Hi everyone, At the moment, the VPNaaS team is a bit low on people and in order to be able to handle the workload, I'd like to opt to only keeping maintained releases active. I propose retiring those branches unless someone steps up to fix and clean them up: https://review.opendev.org/c/openstack/releases/+/843167 Please respond to this email if you are running those releases and you are willing to maintain those older branches. Thanks Mohammed -- Mohammed Naser VEXXHOST, Inc.

2 1

[all][oslo] Generation of sample policy files broken since oslo.policy 3.12.0
by Pierre Riteau 27 May '22

27 May '22

Hello, While updating sample policy files (those with all rules commented out and including comments) in CloudKitty, I discovered that the functionality was broken: oslo.policy generates an actual policy file instead [1]. This issue was first introduced in 3.12.0. I submitted a fix [2] which I assume will ship in the next release. I thought this was worth sharing since any project using output from oslopolicy-sample-generator in their docs or repository could be impacted. A workaround is to stick to oslo.policy 3.11.0 in your genpolicy tox environment. Cheers, Pierre Riteau (priteau) [1] https://bugs.launchpad.net/oslo.policy/+bug/1975682 [2] https://review.opendev.org/c/openstack/oslo.policy/+/843250

1 0

[cinder] festival of XS reviews 27th May 2022
by Rajat Dhasmana 27 May '22

27 May '22

Hello Argonauts, We will be having our monthly festival of XS reviews today i.e. 27th May (Friday) from 1400-1600 UTC. Following are some additional details: Date: 27th May, 2022 Time: 1400-1600 UTC Meeting link: https://meetpad.opendev.org/cinder-festival-of-reviews etherpad: https://etherpad.opendev.org/p/cinder-festival-of-reviews Thanks and regards Rajat Dhasmana

1 0

Openstack-Ansible - Test Cluster on VirtualBox Hosts
by Dave Hall 26 May '22

26 May '22

Hello, Sorry for a beginner question. I am trying to deploy a 3-host minimal test cluster on VirtualBox hosts via OpenStack-Ansible. My purpose is to first build this test cluster and then to deploy a production cluster on physical hardware. The test cluster will be used first to learn, and then to validate changes prior to deploying them on the production cluster. I started with Vagrant-Openstack, but it is still based on Stein and not easily adaptable to Xena. Right now I'm working with Xena and OpenStack-Ansible 24.x on Debian 10 with a deployment host running Debian 11. All 4 systems are native VirtualBox VMs I've managed to deploy a couple of nearly functional clusters this way, but never fully functional and stable. Any guidelines or recommendations for this kind of deployment would be sincerely appreciated. Thanks. -Dave

2 1

[qa][requirements] Tempest Gate blocked for py3.6|7 support
by Ghanshyam Mann 26 May '22

26 May '22

Hello Everyone, As we know, in Zed cycle we have dropped the support of py3.6|7 from OpenStack which is why projects, lib like oslo started dropping it and made new releases. For example, oslo.log 5.0.0 does not support py3.6|7. Tempest being branchless and still supporting stable/victoria onwards stable branches thought of keeping the py36|7 support. But with the oslo dropped py3.6|7 and upper constraint has been updated to the oslo lib latest version made Tempest unit py3.6|7 test jobs failed. - https://bugs.launchpad.net/tempest/+bug/1975036 We have two options here: 1. requirements repo maintain different constraints for py3.6|7 and py3.8|9 which fix the Tempest py3.6| jobs and we can keep the python3.6|7 support in Tempest. Example: oslo.log which fixed the gate[1] but we might need to do the same for Tempest's other deps - https://review.opendev.org/c/openstack/requirements/+/842820 2. Drop the support of py3.6|7 from Tempest If the requirement team is not ok with the above solution then we can think of dropping the py3.6|7 support from Tempest too. This will stop Tempest to run on py3.6|7 but it will not block Tempest to test the OpenStack running on py3.6|7 as that can be done by running the Tempest in virtual env. Opinion? NOTE: Until we figure this out, I have proposed to temporarily stop running py3.6|7 on tempest gate, (especially to get c9s volume detach failure fix to merged otherwise that will block other projects gate too) - https://review.opendev.org/c/openstack/tempest/+/842821 [1] https://review.opendev.org/c/openstack/tempest/+/842819 -gmann

2 3

[neutron] Drivers meeting agenda - 27.05.2022.
by Lajos Katona 26 May '22

26 May '22

Hi Neutron Drivers, The agenda for tomorrow's drivers meeting is at [1]. We have one RFE to discuss tomorrow: * [RFE] Allow setting --dst-port for all port based protocols at once (#link https://bugs.launchpad.net/neutron/+bug/1973487) On Demand agenda: * (lajoskatona): meaning of option "router_auto_schedule" is ambiguous (#link https://bugs.launchpad.net/neutron/+bug/1973656 ) [1] https://wiki.openstack.org/wiki/Meetings/NeutronDrivers#Agenda See you at the meeting tomorrow. Lajos Katona (lajoskatona)

1 0

[neutron][neutron-vpnaas][release] dropping feature/lbaasv2 branch
by Mohammed Naser 26 May '22

26 May '22

Hi there, It looks like we've managed to track along a feature/lbaasv2 branch into neutron-vpnaas all the way from 2014 :) I'd like to request for the release team to delete that branch if possible. :) Thanks, Mohammed -- Mohammed Naser VEXXHOST, Inc.

5 4

openstack queens how increase dashboard threads
by Ignazio Cassano 26 May '22

26 May '22

Hello, I'd like to increase on centos queens the threads for openstack dashboard. At this time my /etc/httpd/conf.d/openstack-dashboard.conf is the following: WSGIDaemonProcess dashboard WSGIProcessGroup dashboard WSGISocketPrefix run/wsgi WSGIApplicationGroup %{GLOBAL} WSGIScriptAlias /dashboard /usr/share/openstack-dashboard/openstack_dashboard/wsgi/django.wsgi Alias /dashboard/static /usr/share/openstack-dashboard/static <Directory /usr/share/openstack-dashboard/openstack_dashboard/wsgi> Options All AllowOverride All Require all granted </Directory> <Directory /usr/share/openstack-dashboard/static> Options All AllowOverride All Require all granted </Directory> I tired to modify the first line like this: WSGIDaemonProcess dashboard user=apache group=apache processes=3 threads=10 I restartded httpd but now I am not able to log on the the dashboard. I am sure keystone is working because I am able do execute all commands with command line. Any help, please ? Regards Ignazio

1 0

horizon security group page bug
by Parsa Aminian 26 May '22

26 May '22

On the horizon user setting section there is an option called 'Items per page' that changes the number of items per page . It seems it does not work on security_groups page and on that page all of the security groups will be loaded and that causes a bad gateway error timeout on the browser .

1 0