March 2022 - openstack-discuss - lists.openstack.org

[neutron] We want you for the PTG !
by Lajos Katona 30 Mar '22

30 Mar '22

Retweet..... (original http://lists.openstack.org/pipermail/openstack-discuss/2022-March/027889.ht… ) Hi folks As a reminder, PTG will start next week and we'll have Neutron meetings on Monday up to Friday everyday between 1pm UTC and 4pm UTC. I'm asking here loudly folks to provide their topics they want to discuss for the PTG *before Thursday this week* so I can start to plan the agenda for next week. All of the PTG logistics and topics are on https://etherpad.opendev.org/p/neutron-zed-ptg Add the topics you want ! Don't be afraid to join the hopefully last virtual PTG and see our community :-) Last note, remember you need to register for free for the PTG https://openinfra-ptg.eventbrite.com/ See you next week, Lajos Katona (lajoskatona)

1 0

rabbitmq config changes not applied in newer format
by Eugen Block 30 Mar '22

30 Mar '22

Hi *, this might not be the right place to ask but I'm curious how others configure their rabbitmq. RabbitMQ version: 3.8.3 OpenStack version: Ussuri/Victoria (two different clusters) We have a highly available cloud controlled by pacemaker. The deployment is based on our own Salt states. We noticed that our config is not applied (e. g. after power outage), we need to import those manually with 'rabbitmqctl import /path/to/definitions.json'. Comparing it to an older cloud version (Rocky, Rabbit version 3.6.16) I noticed that the config format is different between those versions, the older version uses a json format (?): ---snip--- # old format cat /etc/rabbitmq/rabbitmq.config [ {mnesia, [ {dump_log_write_threshold, 300}, {dump_log_time_threshold, 180000} ] }, {rabbit, [ {collect_statistics_interval, 5000}, {tcp_listen_options, [ {backlog, 128},{nodelay, true},{keepalive, false} ] }, {tcp_listeners, [ {"x.x.x.x", 5672} ]}, {cluster_partition_handling, pause_minority}, {queue_master_locator, <<"min-masters">>}, {disk_free_limit, 50000000} ]}, {rabbitmq_management, [ {listener, [{ip, "x.x.x.x"}, {port, 15673}]}, {load_definitions, "/etc/rabbitmq/definitions.json"} ] } ]. # new format [...] listeners.tcp.default = 5672 listeners.tcp.other_port = 5673 listeners.tcp.other_ip = x.x.x.x:5672 [...] ---snip--- If I switch to the old format and restart rabbitmq on that node, the changes are applied successfully. Is this a known issue? Should I just stick to the old format? Any comments are appreciated! Regards, Eugen

1 2

[magnum][murano][release][sahara][tc][trove][zaqar] Emergency bypass reviewer/PTL/liaison approval for Yoga release fixes
by Jeremy Stanley 29 Mar '22

29 Mar '22

A number of teams seem not to have noticed that their tests (and possibly the services themselves) were broken by the removal[*] of the "tenant" argument from RequestContext objects in oslo.context 4.0.0 released on February 3, 2022. As we're at a little over a day left before we need to finalize the Yoga release, I'm seeking permission from the TC on behalf of the OpenStack Release Managers to bypass normal core reviewer, PTL and release liaison approval processes in order to approve any remaining changes for official OpenStack projects necessary for this transition, and to produce new release candidates with those fixes included as necessary. [*] https://review.opendev.org/815938 -- Jeremy Stanley

8 16

[ironic] No weekly meeting in April 4th
by Iury Gregory 29 Mar '22

29 Mar '22

Hello Ironicers, Since next week is the PTG we won't have our weekly meeting, we will resume our weekly meeting on April 11. Thank you! -- *Att[]'sIury Gregory Melo Ferreira * *MSc in Computer Science at UFCG* *Part of the ironic-core and puppet-manager-core team in OpenStack* *Software Engineer at Red Hat Czech* *Social*: https://www.linkedin.com/in/iurygregory *E-mail: iurygregory(a)gmail.com <iurygregory(a)gmail.com>*

1 0

[qa] Cancelling office hour on April 5th
by Martin Kopec 29 Mar '22

29 Mar '22

Hi everyone, we are cancelling the QA office hour on April 5th due to PTG. We are looking forward to seeing you on PTG. Just as a reminder, QA time slots: - Monday (April 4th) 13-14 UTC (1 hour) @ Liberty room - Tuesday (April 5th) 15-17 UTC (2 hours) @ Liberty room - Thursday (April 7th) 13-14 UTC (1 hour) @ Liberty room The topics we are going to cover are gathered in this etherpad [1]. If you have anything you would like to discuss with us, please, feel free to write it to [1]. [1] https://etherpad.opendev.org/p/qa-zed-ptg Thank you, -- Martin Kopec Senior Software Quality Engineer Red Hat EMEA IM: kopecmartin

1 0

Juju bootstrap issues on ubuntu 20.04 LTS
by Wada Akor 29 Mar '22

29 Mar '22

Good Day every one, Please i need a respond from these who have deployed openstack charms on ubuntu . i ran the command below # juju bootstrap --bootstrap-series=focal --constraints tags=juju mymaas maas-controller here is my out put below # Creating Juju controller "maas-controller" on mymaas/default Looking for packaged Juju agent version 2.9.27 for amd64 Located Juju agent version 2.9.27-ubuntu-amd64 at https://streams.canonical.com/juju/tools/agent/2.9.27/juju-2.9.27-ubuntu-am… Launching controller instance(s) on mymaas/default... - a3r8rm (arch=amd64 mem=3.5G cores=2) Installing Juju agent on bootstrap instance Fetching Juju Dashboard 0.8.1 Waiting for address Attempting to connect to 10.0.0.2:22 Connected to 10.0.0.2 Running machine configuration script... I was unable to bootstrap the juju-controller on the maa-controller I need support thanks Wada Akoh Kenneth Jos,Plateau State , Nigeria

1 0

[nova][placement] We want you for the PTG !
by Sylvain Bauza 29 Mar '22

29 Mar '22

Hi folks, As a reminder, PTG will start next week and we'll have Nova meetings on Tues up to Friday everyday between 2pm UTC and 5pm UTC. I'm asking here loudly folks to provide their topics they want to discuss for the PTG *before Thursday this week* so I can start to plan the agenda for next week. All of the PTG logistics and topics are within https://etherpad.opendev.org/p/nova-zed-ptg Add the topics you want ! Don't be afraid to join the hopefully last virtual PTG and see our community :-) Last note, remember you need to register for free for the PTG https://openinfra-ptg.eventbrite.com/ See you next week, -Sylvain

1 0

[TripleO] Propositing Jiri Podivin as TripleO (Validation Framework) core
by Mathieu Bultel 29 Mar '22

29 Mar '22

Hi folks, I would like to propose Jiri Podivin as TripleO Validation Framework core. Jirka has been part of the TripleO organization for some significant time now and his contribution has grown a lot during the last few months. He is submitting highly valuable reviews and has now a strong knowledge around the TripleO Validations Framework areas, the Python framework but also in the CI (TripleO and upstream generic) and more general projects. I think getting him as a core reviewer for the Validations repositories will be very good for us. Feel free to send your feedback, if there is no objection until next week, I propose to add him to the list with limited core votes to the VF repo [1]. Thank you, KR, Mathieu (matbu) [1] openstack/validations-libs openstack/validations-common openstack/tripleo-validations and eventually the Validation related code in openstack/python-tripleoclient.

6 5

Cinder - easy to hit RecursionError with complex config formulas
by bartosz.rabiega＠ovhcloud.com 29 Mar '22

29 Mar '22

Hello, I wanted to share something I've recently discovered - there is a strange issue with cinder evaluating complex configuration formulas. For example when using complex goodness_function it's quite easy to hit: ERROR cinder.scheduler.weights.goodness maximum recursion depth exceeded: RecursionError: maximum recursion depth exceeded I did some tests to find the root cause. It seems that pyparsing module does deep recursive parsing quite a lot (default recursion limit is 1000). Not sure how to solve it but it would be nice to at least have a warning in the docs. Results and methodology below. Tests were done using following code snippet ------------------------------------------- from cinder.scheduler.evaluator.evaluator import evaluate import sys formulas = [ "1", "1 + 1", "max(1, 2, 3)", "max(1 + (10 / 20), 2, 3)", "(1 + max(1 + (10 / 20), 2, 3)) / 100", "((1 + max(1 + (10 / 20), 2, 3)) / 100) + stats.total_capacity_gb", "(((1 + max(1 + (10 / 20), 2, 3)) / 100) + stats.total_capacity_gb) / 100", ] stats = { 'allocated_capacity_gb': 50000, 'total_capacity_gb': 60000, 'free_capacity_gb': 10000, } for f in formulas: for i in range(10, 2000, 10): sys.setrecursionlimit(i) try: res = evaluate(f, stats=stats) print(f"{i}: {f}") break except RecursionError: pass Test results -------------------------------- Cinder 14.3.1, pyparsing<3.0 210: 1 210: 1 + 1 450: max(1, 2, 3) 600: max(1 + (10 / 20), 2, 3) 790: (1 + max(1 + (10 / 20), 2, 3)) / 100 980: ((1 + max(1 + (10 / 20), 2, 3)) / 100) + stats.total_capacity_gb 1160: (((1 + max(1 + (10 / 20), 2, 3)) / 100) + stats.total_capacity_gb) / 100 Cinder 16.4.2, pyparsing<3.0 220: 1 220: 1 + 1 450: max(1, 2, 3) 610: max(1 + (10 / 20), 2, 3) 790: (1 + max(1 + (10 / 20), 2, 3)) / 100 980: ((1 + max(1 + (10 / 20), 2, 3)) / 100) + stats.total_capacity_gb 1170: (((1 + max(1 + (10 / 20), 2, 3)) / 100) + stats.total_capacity_gb) / 100 Cinder 19.1.0, pyparsing<3.0 220: 1 220: 1 + 1 450: max(1, 2, 3) 610: max(1 + (10 / 20), 2, 3) 790: (1 + max(1 + (10 / 20), 2, 3)) / 100 980: ((1 + max(1 + (10 / 20), 2, 3)) / 100) + stats.total_capacity_gb 1170: (((1 + max(1 + (10 / 20), 2, 3)) / 100) + stats.total_capacity_gb) / 100 BR

2 1

[tacker] Zed PTG schedule
by Yasufumi Ogawa 28 Mar '22

28 Mar '22

Hi everyone, The next vPTG will be held on 4-8 April and I've reserved rooms 6-8 UTC from 5th to 8th Apr. If you have any suggestion, add your topic on the etherpad[1]. Please don't forget to register youself before joining[2]. [1] https://etherpad.opendev.org/p/tacker-zed-ptg [2] https://openinfra-ptg.eventbrite.com/ Cheers, Yasufumi

1 0

[keystone] get project info with username and password only?
by Tony Liu 28 Mar '22

28 Mar '22

Hi, Is there any way to know which project(s) a non-admin user is assigned to by username and password only? Or it can only be found out by admin user? The intention is to get the project-scoped token by username and password. Another thing interesting, when tried unscoped auth with Train and Xena, no project info or catalog returned. This is expected. But when tried the same unscoped auth with Ussuri, project info and catalog are returned. This is not expected. Any clues how this could happen? Or how I can look into it? Thanks! Tony

1 0

question on plain text config parameters encryption feature
by Alexander Yeremko 28 Mar '22

28 Mar '22

Dear OpenStack community, we are developing plain text config secrets encryption feature according to the next specification: https://specs.openstack.org/openstack/openstack-ansible-specs/specs/xena/pr… We started from Glance OS service and submitted two patchsets already: https://review.opendev.org/c/openstack/openstack-ansible-os_glance/+/814865 Now we have two questions that we need to clarify to proceed our work on that feature and finish our development: 1. Is it correct that we need to develop more patchsets to rework some logic of encryption mechanism according to comment to 'files/encypt_secrets.py' script that arised at the second patchset (PatchSet 2) dated Nov/30/2021 ? Comment is by Dmitry Rabotyagov: "We _really_ should make it as an ansible plugin and re-work logic" 2. We wish to have such feature in previous releases also, not just in upcoming Yoga or Zed. Stein, Train and Victoria - it would be excellent to have plain text secrets encryption with these releases also. So question is how is it possible to use our feature in those releases also? Can we push some backports to those releases openstack-ansible repo? Best regards and wishes, Alex Yeremko This E-Mail (including any attachments) may contain privileged or confidential information. It is intended only for the addressee(s) indicated above. The sender does not waive any of its rights, privileges or other protections respecting this information. Any distribution, copying or other use of this E-Mail or the information it contains, by other than an intended recipient, is not sanctioned and is prohibited. If you received this E-Mail in error, please delete it and advise the sender (by return E-Mail or otherwise) immediately. Any calls held by you with Connectria may be recorded by an automated note taking system to ensure prompt follow up and for information collection purposes, and your attendance on any calls with Connectria confirms your consent to this. Any E-mail received by or sent from Connectria is subject to review by Connectria supervisory personnel.

2 1

[neutron] deputy report late
by Bence Romsics 28 Mar '22

28 Mar '22

Hi Team, I miscalculated a bit about how much time I have early this week and did not have time to compile the deputy report. Sorry for that. Later this week I'll catch up with the bugs still belonging to my week and make sure to send out the report so it can be discussed on next week's meeting. Cheers, Bence

1 0

[cinder] reminder: this week's meeting in video+IRC
by Brian Rosmaita 28 Mar '22

28 Mar '22

Quick reminder that this week's Cinder team meeting on Wednesday 30 March, being the final meeting of the month, will be held in both videoconference and IRC at the regularly scheduled time of 1400 UTC. Given that this is the final meeting of the Yoga development cycle, we're going to do a retrospective during the meeting. It would be helpful to get things rolling if you filled out one (or both) of the following 3 question forms: Cinder Wallaby-Xena-Yoga Retrospective - https://rosmaita.wufoo.com/forms/m1gc1dfo1s42947/ Cinder W-X-Y Retrospective Survey for Drivers - https://rosmaita.wufoo.com/forms/zab0fdr1dg4nwo/ As a reminder, these are the video meeting rules we've agreed to: * Everyone will keep IRC open during the meeting. * We'll take notes in IRC to leave a record similar to what we have for our regular IRC meetings. * Some people are more comfortable communicating in written English. So at any point, any attendee may request that the discussion of the current topic be conducted entirely in IRC. * The meeting will be recorded. connection info: https://bluejeans.com/3228528973 meeting agenda: https://etherpad.opendev.org/p/cinder-yoga-meetings cheers, brian

1 0

[sdk] Fixing role assignment for groups on a domain different than default
by Pedro Alvarez 28 Mar '22

28 Mar '22

Hi all, Some time ago I discovered that I wasn't able to add groups as members of a project (when not in the default domain) using "openstack.cloud.role_assignment". I spent some time debugging and figured what was the issue, and that a solution was already in place for "users", and not "groups". I also noticed that the master branch had all this part of the codebase rewritten, and probably the bug doesn't exist in there, but I believe that version of the sdk won't work with Xena. Additionally just noticed that the stable/yoga branch also has the issue. So, I'm sending a patch to fix this issue, hoping the next tag/release of openstacksdk could have the fix. You can find them here: https://review.opendev.org/q/topic:pedro%252Ffix-group-assignment-on-domain My guess is that the only relevant one would be the one for 'stable/yoga' and I can drop the other. Also I'm assuming that Zuul is taking its time to run CI, and I'll need to update some unit tests before it can be merged. Just wanted to know your thoughts before I finish with the tests. Thanks, Pedro. PS: An example of the current issue: The full traceback is: File "/tmp/ansible_openstack.cloud.role_assignment_payload_hcrpn6hu/ansible_openstack.cloud.role_assignment_payload.zip/ansible_collections/openstack/cloud/plugins/module_utils/openstack.py", line 407, in __call__ results = self.run() File "/tmp/ansible_openstack.cloud.role_assignment_payload_hcrpn6hu/ansible_openstack.cloud.role_assignment_payload.zip/ansible_collections/openstack/cloud/plugins/modules/role_assignment.py", line 178, in run File "/home/ollivander/.local/lib/python3.9/site-packages/openstack/cloud/_identity.py", line 1379, in grant_role raise exc.OpenStackCloudException( failed: [localhost] (item={'name': 'sa', 'groups': ['openstack-sa', 'openstack-pe', 'openstack-technology']}) => { "ansible_facts": { "discovered_interpreter_python": "/usr/bin/python3" }, "ansible_loop_var": "item", "changed": false, "extra_data": { "data": null, "details": "None", "response": "None" }, "invocation": { "module_args": { "api_timeout": null, "auth": null, "auth_type": null, "availability_zone": null, "ca_cert": null, "client_cert": null, "client_key": null, "domain": "LDAP", "group": "openstack-pe", "interface": "public", "project": "sa", "region_name": null, "role": "member", "state": "present", "timeout": 180, "user": null, "validate_certs": null, "wait": true } }, "item": { "groups": [ "openstack-sa", "openstack-pe", "openstack-technology" ], "name": "sa" }, "msg": "Must specify either a user or a group" }

1 0

[neutron] CI meetings next 2 weeks
by Slawek Kaplonski 28 Mar '22

28 Mar '22

Hi, I can't chair CI meeting this week (29.03) because of some personal appointment in the same time. Next week (5.04) there is PTG so lets cancel CI meeting this and next week. See You on the CI meeting after the PTG week, on Tuesday 12.04 -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0

[neutron] Week 13 meetings (starting from 28 March)
by Lajos Katona 28 Mar '22

28 Mar '22

Hi Neutrinos, Let's cancel this week's Team and Drivers meeting as we have PTG next week anyway. See you next week during the PTG Cheers Lajos Katona (lajoskatona)

1 0

[kolla-ansible] OVS br-ex configuration for OVN SNAT gateway along with HAProxy
by Tony Liu 26 Mar '22

26 Mar '22

Hi, My goal is to have OVN SNAT gateway (with OVS bridge) and HAProxy co-exist. Here is the networking configuration (partial) before deployment. eth1, no address, neutron_external_interface eth1.40, external address, kolla_external_vip_interface After deployment, I'd like to see this. br-ex eth1 eth1.40 tag 40 eth1.40 with external address But actually, only eth1 is put on br-ex by Kolla Ansible. Need eth1.40 on br-ex, because the external network is also one of the provider networks. Need eth1 on br-ex, to support other provider networks (different VLANs). It works fine when deploy with TripleO with os-net-config. Is it supported by Kolla Ansible? It seems Kolla Ansible only puts one interface (neutron_external_interface) on br-ex? I know a few workarounds in case that's not supported, just want to confirm. Thanks! Tony

2 2

[neutron] Feedback on slides (driver's meeting topic)
by Rodolfo Alonso Hernandez 26 Mar '22

26 Mar '22

Hello Neutrinos (and Lajos on this topic): I would also add: - OVN BW scheduling aware (in progress during the last two cycles but almost ready). - OVN QoS GW IP (actually the patch was merged, so for sure we'll have this feature that closes the gap between OVN and OVS). Regards.

3 2

[all][tc] What's happening in Technical Committee: summary Mar 25th, 21: Reading: 10 min
by Ghanshyam Mann 25 Mar '22

25 Mar '22

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * We had this week's meeting on Mar 24th. Most of the meeting discussions are summarized below (Completed or in-progress activities section). Meeting full logs are available @https://meetings.opendev.org/meetings/tc/2022/tc.2022-03-24-15.00.log.html * Due to OpenInfra episode and PTG, we have cancelled the next two meetings[1] and will be meeting on April 14th Thursday 15:00 UTC, feel free to add the topic on the agenda[2] by April 13th. 2. What we completed this week: ========================= * None for this week. 3. Activities In progress: ================== TC Tracker for Yoga cycle ------------------------------ * This etherpad includes the Yoga cycle targets/working items for TC[3]. 4 out of 9 items are completed and many are in progress. Open Reviews ----------------- * Five open reviews for ongoing activities[4]. Consistent and Secure Default RBAC -------------------------------------------- I sent the updates for Yoga timeline target on ML[5] and created the etherpad to track this goal for all the milestone[6]. The quick summary is, along with keystone, Nova has completed the work and neutron is in progress. Community-wide goals readiness checklist -------------------------------------------------- As we received the feedback in Yoga PTG TC+PTL interaction session, I have proposed the checklist which can help us to check if the goal is ready to start or not[7], please review and let us know if more items need to be added. Zed cycle Leaderless projects ---------------------------------- No updates on this. I am still waiting for Zaqar PTL +1 on the PTL appointment patch[8] and we will discuss Adjutant in PTG, hoping Braden will be ready with their company side permission[9]. PTG Preparation -------------------- Nothing much to share on this but please continue adding the topics in etherpad[10]. Dropping tags framework ------------------------------ Along with deprecation tag removal[11], we are removing the complete framework now[12]. Fixing Zuul config error ---------------------------- Requesting projects with zuul config error to look into those and fix them which should not take much time[13]. Project updates ------------------- * None for this week. 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[14]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15 UTC [15] 3. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. [1] http://lists.openstack.org/pipermail/openstack-discuss/2022-March/027828.ht… [2] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting [3] https://etherpad.opendev.org/p/tc-yoga-tracker [4] https://review.opendev.org/q/projects:openstack/governance+status:open [5] http://lists.openstack.org/pipermail/openstack-discuss/2022-March/027837.ht… [6] https://etherpad.opendev.org/p/rbac-goal-tracking [7] https://review.opendev.org/c/openstack/governance/+/835102 [8] https://review.opendev.org/c/openstack/governance/+/831123 [9] http://lists.openstack.org/pipermail/openstack-discuss/2022-March/027626.ht… [10] https://etherpad.opendev.org/p/tc-zed-ptg [11] https://review.opendev.org/c/openstack/governance/+/834327 [12] https://review.opendev.org/c/openstack/governance/+/834798/3 [13] https://etherpad.opendev.org/p/zuul-config-error-openstack [14] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [15] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0

[magnum] kube_cluster_deploy timing out
by Chris DiLorenzo 25 Mar '22

25 Mar '22

Hello, I'm trying to deploy a kubernetes cluster using CoreOS 33. I have also tried with CoreOS 35/. 1 master, 1 worker. Ths VMs are deploying without issue. However, the stack is timing out on kube_cluster_deploy. It appears the kubernetes API isn't running: [root@tes-001-pkjawhk66slm-master-0 log]# podman ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES a08cbea59a57 docker.io/openstackmagnum/heat-container-agent:wallaby-stable-1 /usr/bin/start-he... 21 minutes ago Up 21 minutes ago heat-container-agent [root@tes-001-pkjawhk66slm-master-0 log]# ss -ln | grep 8080 -> nothing [root@tes-001-pkjawhk66slm-master-0 heat-config-script]# tail -f 8d8fa128-bca4-485e-946f-90732ebb4cf0-tes-001-pkjawhk66slm-kube_cluster_config-bwkfqwjxzk36.log + sleep 5 ++ kubectl get --raw=/healthz The connection to the server localhost:8080 was refused - did you specify the right host or port? + '[' ok = '' ']' + sleep 5 ++ kubectl get --raw=/healthz The connection to the server localhost:8080 was refused - did you specify the right host or port? + '[' ok = '' ']' + sleep 5 ++ kubectl get --raw=/healthz Not sure where else to look. Thanks Chris

1 0

[kolla] [rabbitmq] Another RMQ config question
by Albert Braden 25 Mar '22

25 Mar '22

We’re running kolla-ansible Train and implementing durable queues. I was able to make it work by adding these lines to etc/kolla/config/global.conf: [oslo_messaging_rabbit] amqp_durable_queues = True But we want to do it one cluster at a time, so I tried commenting that out and adding line: amqp_durable_queues: "True" to group_vars/<region>/vars.yml but that seems to have no effect. Where can I put this value to enable durable queues per-cluster?

2 1

[tripleo] CI jobs broken due to #1966382
by Chandan Kumar 25 Mar '22

25 Mar '22

Hello, The tripleo-ci jobs are broken due to the following bug. https://bugs.launchpad.net/tripleo/+bug/1966382 - Multiple tripleo jobs are failing because of "error: Multiple top-level packages discovered in a flat-layout" The latest release of setuptools 61.0 caused it and more info is added here: https://github.com/pypa/setuptools/issues/3197 The team is working on fixing it https://review.opendev.org/q/topic:lp%252F1966382. Till then please hold the rechecks and avoid workflowing patches. Thanks, Chandan Kumar

2 1

[all][tc][goals] : Consistent and Secure Default RBAC: Yoga Timeline updates
by Ghanshyam Mann 25 Mar '22

25 Mar '22

Hello Everyone, As you know, "Consistent and Secure Default RBAC" is one of the currently selected community-wide goals and we have divided it into multiple milestones (cycle)[1]. Our first milestone was Yoga release[2] and in this email, I am going to summarize the progress of Yoga timeline targets. With Lance's role change in his company and we finalized the direction in between of Yoga cycle, there is less progress than what we targeted. Gerrit Topic: https://review.opendev.org/q/topic:%2522secure-rbac%2522+(status:open+OR+st… Tracking: https://etherpad.opendev.org/p/rbac-goal-tracking Completed: ========= * Keystone is already implemented the RBAC as per the new direction. * Nova completed the RBAC as per the new direction[3]. In-progress: ========= * Neutron has started the policy update as per the new direction[4]. Yoga Targets and their progress: ======================== 1. Keystone implements a new default role called manager: Spec merged[5], implementation yet to start. 2. Keystone implements a new default role called service: Spec under discussion[6] 3. Keystone enforces scope by default: Not yet done. We can do it at the start of the Zed cycle. 4. Services start implementing Phase 1: Done. The target was to do at least in one of the services and Nova completed it. 5. OpenStack-wide Personas Documentation: Not yet done. [1] https://governance.openstack.org/tc/goals/selected/consistent-and-secure-rb… [2] https://governance.openstack.org/tc/goals/selected/consistent-and-secure-rb… [3] https://blueprints.launchpad.net/nova/+spec/policy-defaults-refresh-2 [4] https://review.opendev.org/c/openstack/neutron/+/821208 [5] https://review.opendev.org/c/openstack/keystone-specs/+/818603 [6] https://review.opendev.org/c/openstack/keystone-specs/+/818616 -gmann

1 0

[release] Release countdown for week R-0, Mar 28-30
by Előd Illés 25 Mar '22

25 Mar '22

Development Focus ----------------- We will be releasing the coordinated OpenStack Yoga release Wednesday next week, on March 30th. Thanks to everyone involved in the Yoga cycle! We are now in pre-release freeze, so no new deliverable will be created until final release, unless a release-critical regression is spotted. Otherwise, teams attending the (virtual) PTG should start to plan what they will be discussing there, by creating and filling team etherpads. You can access the list of PTG etherpads at: http://ptg.opendev.org/etherpads.html General Information ------------------- On release day, the release team will produce final versions of deliverables following the cycle-with-rc release model, by re-tagging the commit used for the last RC. A patch doing just that will be proposed. PTLs and release liaisons should watch for that final release patch from the release team. While not required, we would appreciate having an ack from each team before we approve it on the 30th, so that their approval is included in the metadata that goes onto the signed tag. Upcoming Deadlines & Dates -------------------------- Final Yoga release: March 30th, 2022 PTG: April 4 - 8, 2022 (virtual) OpenInfra Summit: June 7-9, 2022 (Berlin) ElődIllés irc: elodilles

1 0