- openstack-discuss - lists.openstack.org

[TripleO] Major Release Upgrade Issue
by Anirudh Gupta 07 Mar '22

07 Mar '22

Hi Team I have deployed Openstack USSURI using TripleO. It was successfully done, after which I started Upgrading the setup to Victoria. The Undercloud was successfully upgraded and there was no issue, but when I tried upgrading the Overcloud Nodes (starting with the Controller), some issues were encountered while executing the below command openstack overcloud upgrade run --limit Controller --playbook upgrade_steps_playbook.yaml Issue: TASK | Ensure DNF modules have the right stream *2022-03-04 14:29:57.723661 | 525400cb-2e90-4086-e760-00000000009b | FATAL | Ensure DNF modules have the right stream | overcloud-novacompute-0 |* item={'module': 'container-tools', 'stream': '3.0'} |* *...* *...* *Installing module from Fail-Safe repository is not* *allowed\"))\ndnf.exceptions.Error: Installing module from Fail-Safe repository is not allowed\n", "module_stdout": "", "msg": "MODULE FAILURE\nSee stdout/stderr for the exact error", "rc": 1}** *Can someone please help in resolving this.* Thanks in Advance Regards Anirudh Gupta

1 0

[nova][neutron] os-vif params
by Arnaud Morin 07 Mar '22

07 Mar '22

Hey all, When I take a look at [1], I can see some parameters, such as network_device_mtu, isolate_vif, etc. As far as I can tell, nova is using these params when plugging the port in OVS (if using OVS as ml2 plugin of course). But I cannot find the config params in the documentation: [2] Am I missing something? Cheers, Arnaud. [1] https://github.com/openstack/os-vif/blob/master/vif_plug_ovs/ovs.py [2] https://docs.openstack.org/nova/latest/configuration/config.html

4 6

[ironic][tripleo][kayobe][tenks][vbmc] Do you also experience random issues with vbmc?
by Radosław Piliszek 07 Mar '22

07 Mar '22

Dear fellow upstream OpenStackers, I tagged the main projects that use vbmc intensively because I have a question regarding the stability of vbmc. I have been working on adding baremetal testing in Kolla Ansible using Tenks and thus also VirtualBMC. I am encountering random failures that I am at the moment unable to debug. It seems vbmc likes to reject the "chassis bootdev pxe" ipmitool command from time to time (the command is issued when trying to deploy a host). This seems permanent per case as ironic retries this call several times only to fail. The error message is "Error setting Chassis Boot Parameter 5". I can't see any trace in vbmc logs (with DEBUG enabled). Other ipmitool commands seem to work fine (like periodic power status). I was wondering if any of you also experienced this issue. I am providing a link to an excerpt from the logs. [1] It also shows a raw ipmitool command succeeding only to let the next one fail. [1] https://paste.ubuntu.com/p/MgHHpDvVGf/ -yoctozepto

2 2

[Triple0] Upgrade Error
by Lokendra Rathour 06 Mar '22

06 Mar '22

Hi Team, we are trying to upgrade Triple0 Train to Ussuri. Undercloud upgrade prepare is done successfully and when we are going for overcloud upgrade getting below error: * len(inspect.getargspec(type_).args) > 1)2022-02-23 16:49:50.959 187217 INFO tripleoclient.utils.utils [-] Running Ansible playbook: /usr/share/ansible/tripleo-playbooks/cli-update-params.yaml, Working directory: /tmp/tripleoj7rvp51m, Playbook directory: /usr/share/ansible/tripleo-playbooksPLAY [Update Parameters] *******************************************************2022-02-23 16:49:51.858966 | 5254007d-0040-f631-88e7-000000000008 | TASK | Check for required inputs2022-02-23 16:49:51.895961 | 5254007d-0040-f631-88e7-000000000008 | SKIPPED | Check for required inputs | localhost2022-02-23 16:49:51.897803 | 5254007d-0040-f631-88e7-000000000008 | TIMING | Check for required inputs | localhost | 0:00:00.096595 | 0.04s2022-02-23 16:49:51.901827 | 5254007d-0040-f631-88e7-000000000009 | TASK | Set parameters fact2022-02-23 16:49:51.949091 | 5254007d-0040-f631-88e7-000000000009 | OK | Set parameters fact | localhost2022-02-23 16:49:51.951583 | 5254007d-0040-f631-88e7-000000000009 | TIMING | Set parameters fact | localhost | 0:00:00.150375 | 0.05s2022-02-23 16:49:51.956146 | 5254007d-0040-f631-88e7-00000000000b | TASK | Update parameters2022-02-23 16:50:12.542028 | 5254007d-0040-f631-88e7-00000000000b | FATAL | Update parameters | localhost | error={"changed": false, "error": "Error validating environment for plan overcloud: ERROR: Property error: resources.InternalApiVirtualIP.properties: Unknown Property DnsName\n File \"/usr/lib/python3.6/site-packages/heat/common/wsgi.py\", line 891, in __call__\n request, **action_args)\n File \"/usr/lib/python3.6/site-packages/heat/common/wsgi.py\", line 964, in dispatch\n return method(*args, **kwargs)\n File \"/usr/lib/python3.6/site-packages/heat/api/openstack/v1/util.py\", line 56, in handle_stack_method\n return handler(controller, req, **kwargs)\n File \"/usr/lib/python3.6/site-packages/heat/api/openstack/v1/stacks.py\", line 633, in validate_template\n raise exc.HTTPBadRequest(result['Error'])\n", "msg": "Error updating parameters for plan overcloud: Error validating environment for plan overcloud: ERROR: Property error: resources.InternalApiVirtualIP.properties: Unknown Property DnsName\n File \"/usr/lib/python3.6/site-packages/heat/common/wsgi.py\", line 891, in __call__\n request, **action_args)\n File \"/usr/lib/python3.6/site-packages/heat/common/wsgi.py\", line 964, in dispatch\n return method(*args, **kwargs)\n File \"/usr/lib/python3.6/site-packages/heat/api/openstack/v1/util.py\", line 56, in handle_stack_method\n return handler(controller, req, **kwargs)\n File \"/usr/lib/python3.6/site-packages/heat/api/openstack/v1/stacks.py\", line 633, in validate_template\n raise exc.HTTPBadRequest(result['Error'])\n", "success": false}2022-02-23 16:50:12.544560 | 5254007d-0040-f631-88e7-00000000000b | TIMING | Update parameters | localhost | 0:00:20.743350 | 20.59s* Command used to run the overcloud upgrade prepare: *(undercloud) [stack@undercloud ~]$ cat upgrade_overcloud_prepare.shopenstack overcloud upgrade prepare --templates \ -r /home/stack/templates/roles_data.yaml \ -n /home/stack/templates/network_data.yaml \ -e /home/stack/templates/environment.yaml \ -e /home/stack/templates/environments/network-isolation.yaml \ -e /home/stack/templates/environments/network-environment.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/services/ironic-conductor.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/services/ironic-inspector.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/services/ironic-overcloud.yaml \ -e /home/stack/templates/ironic-config.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/docker-ha.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/podman.yaml \ -e /home/stack/templates/init-repo.yaml \ -e /home/stack/containers-prepare-parameter.yaml(undercloud) [stack@undercloud ~]$* *Document referred:*Upgrading to a Next Major Release — TripleO 3.0.0 documentation (openstack.org) <https://docs.openstack.org/project-deploy-guide/tripleo-docs/wallaby/post_d…> Any support here, please. -- ~ Lokendra skype: lokendrarathour

2 5

[tc][ptl] TC + Community Leaders interaction in Zed Virtual PTG
by Ghanshyam Mann 04 Mar '22

04 Mar '22

Hello Everyone, We had successful TC+Community leaders interaction sessions in the last PTG, and we will continue the same for Zed cycle PTG also. I have created the below etherpad with the draft agenda, If you as PTL or project representatives or SIG Chair and would like to attend this session, please add your name: - https://etherpad.opendev.org/p/tc-ptl-interaction-zed Also, I have created the doodle poll to select the best suitable time. It will be for two hours (single or two sessions) either on Monday or Tuesday. Please add your preference in the below doodle poll (including TC members): - https://doodle.com/poll/dcer6i3wk2b8eim3 -gmann

1 1

[release] Release countdown for week R-3, Mar 07 - 11
by Előd Illés 04 Mar '22

04 Mar '22

Development Focus ----------------- The Release Candidate (RC) deadline is next Thursday, March 10th, 2022. Work should be focused on fixing any release-critical bugs. General Information ------------------- All deliverables released under a cycle-with-rc model should have a first release candidate by the end of the week, from which a stable/yoga branch will be cut. This branch will track the Yoga release. Once stable/yoga has been created, the master branch will be ready to switch to Zed development. While the master branch will no longer be feature-frozen, please prioritize any work necessary for completing Yoga plans. Release-critical bugfixes will need to be merged in the master branch first, then backported to the stable/yoga branch before a new release candidate can be proposed. Actions ------- Early in the week, the release team will be proposing RC1 patches for all cycle-with-rc projects, using the latest commit from the master branch. If your team is ready to go for cutting RC1, please let us know by leaving a +1 on these patches. If there are still a few more patches needed before RC1, you can -1 the patch and update it later in the week with the new commit hash you would like to use. Remember, stable/yoga branches will be created with this, so you will want to make sure you have what you need included to avoid needing to backport changes from the master branch (which will technically then be Zed) to this stable branch for any additional RCs before the final release. The release team will also be proposing releases for any deliverable following a cycle-with-intermediary model that has not produced any Yoga release so far. Finally, now is a good time to finalize release highlights if you have not already done so. Release highlights help shape the messaging around the release and make sure that your work is properly represented. Upcoming Deadlines & Dates -------------------------- RC1 deadline: March 10th, 2022 (R-3 week) Final RC deadline: March 24th, 2022 (R-1 week) Final Yoga release: March 30th, 2022 Next PTG: April 4 - 8, 2022 (virtual) Előd Illés irc: elodilles

1 0

[requirements][release][rfe] sushy 4.1.1 for Yoga
by Iury Gregory 04 Mar '22

04 Mar '22

Hello Stackers, I would like to request a new release for sushy before creating the yoga branch, It contains some important fixes (e.g it will fix a problem when build sushy in Debian). The sushy lib is only used by ironic, so it shouldn't cause any problems updating the version in requirements. Thanks! -- *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>*

3 3

[Ironic] No suitable device was found for deployment
by 韩光宇 04 Mar '22

04 Mar '22

Dear all, I have a OpenStack Victoria environment, and tried to use ironic manage bare metal. But I got "- root device hints were not provided and all found block devices are smaller than 4294967296B." in deploy stage. 2022-02-09 17:57:56.492 3908982 ERROR ironic.drivers.modules.agent_base [-] Agent returned error for deploy step {'step': 'write_image', 'priority': 80, 'argsinfo': None, 'interface': 'deploy'} on node cc68c450-ce54-4e1c-be04-8b0a6169ef92 : No suitable device was found for deployment - root device hints were not provided and all found block devices are smaller than 4294967296B.. I used "openstack server create --flavor my-baremetal-flavor --nic net-id=$net_id --image $image testing" to deploy bare metal node. I download deploy images(ipa-centos8-master.kernel and ipa-centos8-master.initramfs) in https://tarballs.opendev.org/openstack/ironic-python-agent/dib/files/. The baremetal node info and flavor info as following: https://paste.opendev.org/show/bV7lgO6RkNQY6ZGPbT2e/ Ironic configure file as following: https://paste.opendev.org/show/bTgY9Kpn7KWqwQl73aEa/ Ironic-conductor log: https://paste.opendev.org/show/bFKZYlXmccxNxU8lEogk/ The log of ironic-python-agent in bare metal node: https://paste.opendev.org/show/btAuaMuV2IutV2Pa7YIa/ I see some old discussion about this, such as: https://bugzilla.redhat.com/show_bug.cgi?id=1312187. But those discussions took place a long time ago, not version V, and no solution was seen. Does anyone know how to solve this problem? I would appreciate any kind of guidance or help. Thank you, Han Guangyu

3 14

[nova][placement] Zed PTG preparation
by Sylvain Bauza 04 Mar '22

04 Mar '22

Hey folks, We have until Mar 11th [1]to communicate about our needs for the Zed PTG (I've already signed up our presence by the survey) .As you can see in [2], there are already projects that booked some timeslots. This time, I won't ask you to tell me over Doodle which times you can be around, but I'd rather propose you 3 options : Option A "The short one" : we ask for 3 days from Wednesday to Friday with 4 hours each (13UTC-17UTC) Option B "The week used": we ask for 4 days from Tuesday to Friday with 3 hours each (14UTC-17UTC) Option C "The largest one" : we ask for 4 days from Tuesday to Friday with 4 hours each (13UTC-17UTC) Option D "The Asian-nice one" : we ask for Wed to Friday with 3 hours each (14UTC-17UTC) but we also ask for Thursday with 2 hours (6UTC-8UTC) Please start to think about those options as we'll discuss this on next Tuesday meeting [3] and eventually we will vote on it. I also created a new etherpad for our PTG : https://etherpad.opendev.org/p/nova-zed-ptg If you want, you can start to collect some topics but also if you aren't able to attend next Nova meeting, you can also start to vote on the option above in there. Voila, that's it. Thanks and let's discuss it again on next meeting, -Sylvain [1] http://lists.openstack.org/pipermail/openstack-discuss/2022-February/027051… [2] https://ethercalc.openstack.org/7yxdas7suqnd [3] https://meetings.opendev.org/#Nova_Team_Meeting

1 0

[neutron] Drivers meeting agenda - 04.03.2022.
by Lajos Katona 03 Mar '22

03 Mar '22

Hi Neutron Drivers, The agenda for tomorrow's drivers meeting is at [1]. * Gratuitous ARPs are not sent during master transition: ( https://bugs.launchpad.net/neutron/+bug/1952907) ** For this one there are a few wip patches: ** https://review.opendev.org/c/openstack/neutron/+/821434 ** https://review.opendev.org/c/openstack/neutron/+/821433 ** https://review.opendev.org/c/openstack/neutron/+/712474 * On Demand agenda: (ralonsoh): https://bugs.launchpad.net/neutron/+bug/1962465. I want to discuss the scope of this bug and the possible fix. [1] https://wiki.openstack.org/wiki/Meetings/NeutronDrivers#Agenda See you at the meeting tomorrow. Lajos Katona (lajoskatona)

1 0

Openstack HPC storage suggestion
by Satish Patel 03 Mar '22

03 Mar '22

Folks, I built a 30 node HPC environment on openstack using mellanox infiniband nic for high speed MPI messaging. So far everything works. Now I am looking for a HPC PFS (parallel file system) similar to Luster which I can mount on all HPC vms to run MPI jobs. I was reading on google and saw some CERN videos and they are using Ceph (cephfs) for PFS. Also i was reading CephFS + Manila is a good choice for HPC on openstack design. Does anyone have any experience with HPC storage for Openstack? Please advice or share your experience :) Thanks in advance. ~S

4 4

[TripleO] Gate blocker for Centos 9 Wallaby
by Dariusz Smigiel 03 Mar '22

03 Mar '22

Currently TripleO gate is experiencing issues with building images [1] We're aware of the problem, and we're trying to resolve this issue. Please withhold from rechecking RDO Third Party CI. Thank you, Dariusz Smigiel (dasm) [1]: https://bugs.launchpad.net/tripleo/+bug/1962786

1 1

[Devstack][Gnocchi][Ceilometer] Not able to retrieve metrics using ceilometer and gnocchi
by Molka Gharbaoui 03 Mar '22

03 Mar '22

Hi all, I installed devstack and ceilometer by adding the following lines in the local.conf file: enable_plugin ceilometer https://opendev.org/openstack/ceilometer.git CEILOMETER_BACKEND=gnocchi Devstack (yoga) works correctly (I am able to create images, instances, etc.). The problem is that I cannot visualize the metrics. Using "gnocchi metric list" and "gnocchi resource list" commands the result is empty. When I use the "--debug" option, no errors are plotted but the body response is empty. "ceilometer-upgrade" gives the following error: DEBUG ceilometer.cmd.storage Upgrade Gnocchi resource types upgrade /opt/stack/ceilometer/ceilometer/cmd/storage.py:42 "ceilometer-polling" prints "The resource could not be found". I have a running instance. Could you help me in retrieving the metrics from openstack?

3 5

Neutron issue in current Xena Version of openstack
by Adivya Singh 03 Mar '22

03 Mar '22

hi Team, i am facing issue after installing XENA version of Openstack, where in the Same hosted Network node, some routers work, and some not, The real issue is the router which are not working, All floating IP assigned to the router does not work, but other routers hosted on same L3 agent Works I am seeing this king of error " "Could not generate persistent MAC: No data" , but i am not sure this is impacting the issue Regards Adivya Singh

2 1

[hwsig] sushy-oem-idrac for Hardware Vendor SIG
by Jaunteva, Aija 03 Mar '22

03 Mar '22

Hi, I would like to propose moving sushy-oem-idrac [1] that is used in Ironic project to Hardware Vendor SIG. sushy-oem-idrac is iDRAC specific OEM extension of vendor-independent sushy [2] library and both use Redfish to communicate with BMCs. Any feedback welcome. Regards, Aija [1] https://opendev.org/x/sushy-oem-idrac/ [2] https://opendev.org/openstack/sushy Internal Use - Confidential

2 1

[cinder] PTG Planning Etherpad
by Rajat Dhasmana 03 Mar '22

03 Mar '22

Hello Argonauts, As you might be aware that the Zed PTG is approaching so I've created an etherpad for the details of the PTG and adding topics. To summarize, PTG will take place from 4-8 April, 2022 and below are the details for Cinder PTG: Date: 5-8 April, 2022 TIme: 1300-1700 UTC Connection info will be shared prior to the meeting on the etherpad and the cinder channel on IRC. Most probably it will be on BlueJeans (as has been in the past) but suggestions are welcome. Etherpad: https://etherpad.opendev.org/p/zed-ptg-cinder-planning Regarding the timings, as discussed in the cinder meeting twice, the attendees had no concern and it is the preferred time for the PTG since past 3 virtual PTGs. If there are any concerns, do let me know and we can also schedule your topic as convenient for your timezone. Lastly, I would encourage everyone to add topics as soon as they can since it makes the planning/arranging of topics easier and better. Thanks and regards Rajat Dhasmana

1 0

[all][tc] Technical Committee next weekly meeting on Mar 4th at 1500 UTC
by Ghanshyam Mann 03 Mar '22

03 Mar '22

Hello Everyone, Technical Committee's next weekly meeting is scheduled for Mar 4th at 1500 UTC. If you would like to add topics for discussion, please add them to the below wiki page by Wednesday, Mar 3rd, at 2100 UTC. https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting -gmann

1 2

[election][heat][ptl] PTL non-candidacy
by Rico Lin 03 Mar '22

03 Mar '22

Hi all, As the PTL election will soon start, I would like to share my statement on not planning to run another term of Heat PTL. And Instead, I encourage anyone (core reviewer or not) who is interested to put their name on. I will definitely still stay around and help with reviews and patches. cheers, *Rico Lin*

4 3

[QA][OpenStackSDK][release] Cycle With Intermediary without recent deliverables
by Előd Illés 02 Mar '22

02 Mar '22

Hi, Quick reminder that for deliverables following the cycle-with-intermediary model, the release team will use the latest Yoga release available on release week. The following deliverables have done a Yoga release, but it was not refreshed in the last two months: tempest patrole (this was not yet released at all in Yoga) python-openstackclient (I remember that openstacksdk cannot do another release in Yoga due to issues on master branch. Is this also valid for python-openstackclient?) You should consider making a new one very soon, so that we don't use an outdated version for the final release. Előd Illés irc: elodilles

2 1

[ironic] Zed PTG etherpad
by Iury Gregory 02 Mar '22

02 Mar '22

Hello ironicers! I've created an etherpad to collect topics for our Zed PTG [1] Feel free to add any topics on it =) Later tomorrow I will be sharing the ideas for possible PTG slots and in the upstream meeting on Monday (March 7) we will announce. [1] https://etherpad.opendev.org/p/ironic-zed-ptg -- *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

[designate] Zed PTG planning etherpad
by Michael Johnson 02 Mar '22

02 Mar '22

Hi Designate community, In preparation for our PTG sessions in April I have created an etherpad for us to add topics for discussion. https://etherpad.opendev.org/p/zed-ptg-designate Please add your attendance and topics. Michael

1 0

[tripleo] Dynamically generating firewall rules for the haproxy host on behalf of a deployed service
by Brent Eagles 02 Mar '22

02 Mar '22

Hi all, Designate has a requirement that appears to be a first for TripleO. It needs to deploy miniDNS instances on the internal network but each are accessible from the public network so external bind instances can sync with them. This is done by mapping port numbers on the VIP to each miniDNS instances [1] e.g. 10.0.0.5:16000 --> 172.16.2.184:5354 10.0.0.5:16001 --> 172.16.2.185:5354 10.0.0.5:16002 --> 172.16.2.186:5354 . . . <for each controller> The haproxy configuration is relatively straightforward [2]. There would be no problem if it the haproxy puppet managed the firewall rules, but for typical deployments we appear to disable this [3] and rely on the tripleo.firewall ansible module instead. The complicating factors are: a. the ports range depends on the number of miniDNS instances. b. the miniDNS deployment needs to set firewall rules wherever haproxy happens to live as they are not guaranteed to be on the same host. AFAICT, our ansible based firewall rule mechanism doesn't allow for setting firewall rules on hosts in addition to the ones that the service is being deployed on. Possible solutions I've been considering: a. Have haproxy puppet create firewall rules on the public API network and use tripleo.firewall for everything else. I think we generally don't distinguish which networks firewall rules are applicable to so this would be an "interesting", pervasive change. This is in PID 1's wheelhouse and I'd be interested in how they feel about this. b. Somehow create a jinja-ed firewall rule for haproxy that gets processed at deploy time so details could be filled in using cloud information. This seems like it would be kind of fragile, may not even be possible and depends on details of the framework I'm not familiar with. c. Extend tripleo.firewall or tripleo.iptables to process jinja'd rules - but that's problematic because it needs to be set on the haproxy host, and miniDNS is elsewhere. d. Create some ansible that gets run in the haproxy hosts that generates the firewall rules based on cloud info. I feel this is a bit ugly. Does anyone have any suggestions on other solutions or thoughts on the above? Cheers, Brent 1. https://bugzilla.redhat.com/show_bug.cgi?id=1897319 The TripleO HAProxy instance needs to be configured for BIND->miniDNS AXFR 2. https://review.opendev.org/c/openstack/puppet-tripleo/+/828169 Designate: create proxy ports on external VIP to access miniDNS workers. 3. https://bugs.launchpad.net/tripleo/+bug/1961799 haproxy template tasks to apply IPTables rules are no ops. -- Brent Eagles Principal Software Engineer Red Hat Inc.

3 2

[largescale-sig] Next meeting: Mar 2nd, 15utc
by Thierry Carrez 02 Mar '22

02 Mar '22

Hi everyone, The Large Scale SIG will be meeting this Wednesday in #openstack-operators on OFTC IRC, at 15UTC. You can doublecheck how that time translates locally at: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20220302T15 Feel free to add topics to the agenda: https://etherpad.openstack.org/p/large-scale-sig-meeting Regards, -- Thierry Carrez

1 1

[cinder] Bug deputy report for week of 03-02-2022
by Sofia Enriquez 02 Mar '22

02 Mar '22

This is a bug report from 02-23-2022 to 03-02-2022. Agenda: https://etherpad.opendev.org/p/cinder-bug-squad-meeting ----------------------------------------------------------------------------------------- Low - https://bugs.launchpad.net/cinder/+bug/1962221 "[lightos] Compression handling in lightos driver while default compression enabled." Fix proposed to master. Incomplete - https://bugs.launchpad.net/cinder/+bug/1962607 "IndexError when creating Backups." Fix proposed to master. Cheers -- 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

[TripleO] centos9 jobs only for master, centos 8 & 9 for wallaby
by Marios Andreou 02 Mar '22

02 Mar '22

Hello TripleO o/ During the last period the tripleo-ci team has been working on getting tripleo CI jobs to run centos-9. On master branches across all TripleO repos we now run C9 exclusively (since [1]). On Wallaby branches, after the work at [2] (in particular after https://review.opendev.org/c/openstack/tripleo-ci/+/830132 merges) we will run both C8 and C9 jobs. I started an etherpad at [3] thinking this would be a PTG topic, but I think we'll want to have this conversation way before then. There is a tripleo-heat-templates example in the etherpad that shows what we can expect from the job runs (note the exact jobs that run will vary per repo and even between changes depending on the files touched - but generally there will be duplication between 8 and 9 jobs). The current proposal is that we keep a minimal subset on C8 Wallaby, with C9 wallaby having the full set of jobs. Two factors that will affect our decisions are (there may be more?) i) Upgrades requirements - are we supporting upgrading to Wallaby on 8? For example, the coming undercloud-upgrade-ffu job will be train 8 to wallaby 8. In which case we definitely need to keep at least some subset of 8 jobs (and can't entertain the removal of 8 from Wallaby completely). ii) Are we importing from Wallaby 8 or Wallaby 9? Currently it is 8 but this will soon switch. For the wallaby c8 'subset of jobs' e.g. multinode, vanilla standalone (no scenarios? some subset of them?), undercloud-ffu, minor update. This is just to start the conversation so please reply if you have thoughts or comments about any of the above. We are planning to discuss this in the coming tripleo-ci community call this coming Tuesday at 1330 UTC - meeting link at [4] so please join us if you can and would like to participate, regards, marios [1] https://review.opendev.org/q/topic:c8_teardown_master [2] https://review.opendev.org/q/topic:c9_wallaby_gates [3] https://etherpad.opendev.org/p/tripleoci-wallaby-centos-8-9 [4] https://meet.google.com/bqx-xwht-wky

4 7

[horizon][customization]
by Mathilde Hermet 02 Mar '22

02 Mar '22

Hello Openstack team, I'm currently working on customizing the Horizon (xena) dashboard to use the OVHcloud assets: logo.svg and logo-splash.svg. I've been following this documentation https://docs.openstack.org/horizon/latest/configuration/themes.html I added the ovhcloud theme in horizon/openstack_dashboard/local/local_settings.py in AVAILABLE_THEMES, I created the subdir ovhcloud in horizon/openstack_dashboard/themes and I created a ovhcloud/img with logo.svg and logo-splash.svg in it. I put a _variables.scss and a _styles.scss in /themes/ovhcloud/ Then I executed python manage.py collectstatic It put all the files in horizon-sources/horizon.../static/themes/ovhcloud But then when trying to connect with the session cookie theme="ovhcloud", I have a 500 error. i don't think it comes from images because i've been puting it in /horizon-souurces/horizon.../static/dashbaord.img and they were displayed correctly. Do you have any idea about the misconfiguration I've done ? Best regards, Mathilde Hermet

4 3

[release][requirements][oslo][kuryr][keystone] RFE request
by Előd Illés 02 Mar '22

02 Mar '22

Hi, It turned out that kuryr [1] and keystoneauth [2] deliverables were missed at non-client libraries final release period. So we need to release them now and request Requirement Freeze Exception for them. (PTLs / release liaisons of kuryr and keystoneauth: please review the patches [1][2] as soon as possible) Also I want to mention here oslo.context as well, to formally include it to RFE. (It seems versions >=4.0.0 break things, see thread [3] and [4].) [1] https://review.opendev.org/c/openstack/releases/+/831025 [2] https://review.opendev.org/c/openstack/releases/+/831024 [3] http://lists.openstack.org/pipermail/openstack-discuss/2022-February/027455… [4] http://lists.openstack.org/pipermail/openstack-discuss/2022-March/027480.ht… Előd

3 2

Re: [horizon][customization]
by Laurent Dumont 02 Mar '22

02 Mar '22

Hi! That is possible. Which version of the doc we're you looking at? I think those are able to be modified through merge requests. On Tue, Mar 1, 2022 at 9:07 AM Mathilde Hermet <mathilde.hermet(a)ovhcloud.com> wrote: > Hello, > > > I manage to find that the problem in your documentation is that you forgot > to tell that command "$python manage.py compress --force" must be run after > collecting statics. > > I run it and then my custom themes worked. > > This appears to be required in earlier version of horizon that is why > documentation is may be not up to date. > > > Thanks > > > Mathilde > On 3/1/22 00:25, Laurent Dumont wrote: > > Salut! > > A 500 from Horizon is a bit strange. What do the Horizon logs say? > > If you remove your customization and restart Horizon, does it recover? > > On Mon, Feb 28, 2022 at 11:17 AM Mathilde Hermet < > mathilde.hermet(a)ovhcloud.com> wrote: > >> Hello Openstack team, >> >> >> I'm currently working on customizing the Horizon (xena) dashboard to use >> the OVHcloud assets: logo.svg and logo-splash.svg. >> >> I've been following this documentation >> https://docs.openstack.org/horizon/latest/configuration/themes.html >> >> I added the ovhcloud theme in >> horizon/openstack_dashboard/local/local_settings.py in AVAILABLE_THEMES, >> >> I created the subdir ovhcloud in horizon/openstack_dashboard/themes and >> I created a ovhcloud/img with logo.svg and logo-splash.svg in it. >> >> I put a _variables.scss and a _styles.scss in /themes/ovhcloud/ >> >> Then I executed python manage.py collectstatic >> >> It put all the files in horizon-sources/horizon.../static/themes/ovhcloud >> >> >> But then when trying to connect with the session cookie >> theme="ovhcloud", I have a 500 error. >> >> i don't think it comes from images because i've been puting it in >> /horizon-souurces/horizon.../static/dashbaord.img and they were >> displayed correctly. >> >> >> Do you have any idea about the misconfiguration I've done ? >> >> >> Best regards, >> >> >> Mathilde Hermet >> >> >>

1 0

How OpenStack is Used in Academia - OpenInfra Live
by Sunny Cai 01 Mar '22

01 Mar '22

Hi everyone, This week on OpenInfra Live episode, we are featuring topics on how OpenStack is used in Academic space Open source cloud computing has gained a lot of adoption momentum due to advantages including low cost, flexibility, scalability, and more. Since the early days of OpenStack with NASA’s direct involvement, OpenStack has been deployed in various notable academic institutions all over the world for their infrastructure needs. For this episode, we have invited experts from Oregon State University, Monash University, Télécom Paris, and OpenStack Scientific SIG to talk about how they use OpenStack in academia. Episode: How OpenStack is Used in Academia Date and time: Thursday, March 3 at 9am CT (1500 UTC) You can watch us live on YouTube [1], LinkedIn [2] and Facebook[3]. Host: Kendall Nelson, Senior Upstream Developer Advocate at the OpenInfra Foundation Speakers: • Stig Telfer, Scientific SIG Chair and CTO at StackHPC Ltd • Steve Quenette, Deputy Director at Monash eResearch Centre, Monash University • Rémi Sharrock, Researcher and Lecturer at Télécom Paris & Marc Jeanmougin, Research Engineer at Télécom Paris • Lance Albertson, Director at Oregon State University Open Source Lab Have an idea for a future episode? Share it now at ideas.openinfra.live [4]. [1] https://www.youtube.com/watch?v=xqGvMn0B7jc&ab_channel=OpenInfrastructureFo… [2] https://www.linkedin.com/video/event/urn:li:ugcPost:6902672962731016192/ [3] https://www.facebook.com/104139126308032/posts/4883571768364720/ [4] https://openinfrafoundation.formstack.com/forms/openinfralive Thanks, Sunny Cai OpenInfra Foundation Marketing & Community

1 0

[nova][octavia][masakari][designate][oslo][requirements] oslo.context>=4.0.0 seems to need updated tests
by Matthew Thode 01 Mar '22

01 Mar '22

The update to see what's breaking is here https://review.opendev.org/829599 Feel free to make that patch depend on your fix to test (with rechecks) -- Matthew Thode

4 6

[neutron] CI meeting - agenda for 1.03.2022
by Slawek Kaplonski 01 Mar '22

01 Mar '22

Hi, Agenda for today's Neutron CI meeting is at [1]. Please remember that we will meet on the video call today [2]. See You all there at 1500 UTC [1] https://etherpad.opendev.org/p/neutron-ci-meetings [2] https://meetpad.opendev.org/neutron-ci-meetings -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0

[openstack-helm] No Meeting Tomorrow
by Gage Hugo 01 Mar '22

01 Mar '22

Hey team, Since there's nothing on the agenda for tomorrow's meeting, it has been cancelled. We will meet again next week.

1 0

Fluentd error with Kolla ansible deployment
by A Monster 01 Mar '22

01 Mar '22

I'm getting the following error while trying to deploy openstack using kolla-ansible. I've set up a local docker registry and enabled insecure registries in daemon.json file and I even tried to pull fluentd docker image but I still get the following error TASK [common : Ensure fluentd image is present for label check] fatal: [localhost]: FAILED! => {"changed": true, "msg": "'Traceback (most recent call last):\\n File \"/usr/local/lib/python3.6/site-packages/docker/api/client.py\", line 268, in _raise_for_status\\n response.raise_for_status()\\n File \"/usr/lib/python3.6/site-packages/requests/models.py\", line 940, in raise_for_status\\n raise HTTPError(http_error_msg, response=self)\\nrequests.exceptions.HTTPError: 500 Server Error: Internal Server Error for url: http+docker://localhost/v1.41/images/create?tag=xena&fromImage=quay.io%2Fkolla%2Fcentos-source-fluentd\\n\\nDuring handling of the above exception, another exception occurred:\\n\\nTraceback (most recent call last):\\n File \"/tmp/ansible_kolla_docker_payload_xizndx9s/ansible_kolla_docker_payload.zip/ansible/modules/kolla_docker.py\", line 1241, in main\\n File \"/tmp/ansible_kolla_docker_payload_xizndx9s/ansible_kolla_docker_payload.zip/ansible/modules/kolla_docker.py\", line 1116, in ensure_image\\n File \"/tmp/ansible_kolla_docker_payload_xizndx9s/ansible_kolla_docker_payload.zip/ansible/modules/kolla_docker.py\", line 692, in pull_image\\n File \"/usr/local/lib/python3.6/site-packages/docker/api/image.py\", line 430, in pull\\n self._raise_for_status(response)\\n File \"/usr/local/lib/python3.6/site-packages/docker/api/client.py\", line 270, in _raise_for_status\\n raise create_api_error_from_http_exception(e)\\n File \"/usr/local/lib/python3.6/site-packages/docker/errors.py\", line 31, in create_api_error_from_http_exception\\n raise cls(e, response=response, explanation=explanation)\\ndocker.errors.APIError: 500 Server Error for http+docker://localhost/v1.41/images/create?tag=xena&fromImage=quay.io%2Fkolla%2Fcentos-source-fluentd: Internal Server Error (\"unauthorized: access to the requested resource is not authorized\")\\n'"}

2 2

[qa][devstack] Proposing Dan Smith to devstack core
by Martin Kopec 01 Mar '22

01 Mar '22

Hi all, we would like to propose Dan Smith (IRC: dansmith) to devstack core. Dan is an experienced contributor who has been contributing to several openstack projects. We are glad Dan volunteered to help us in the Devstack project as well. You can vote/feedback in this email thread. If no objection by 17th of February, we will add Dan to the core list. Thanks, -- Martin Kopec Senior Software Quality Engineer Red Hat EMEA IM: kopecmartin

3 3

[cinder] Yoga FEATURE FREEZE in effect
by Harsha Ailani 28 Feb '22

28 Feb '22

Hello Argonauts, Having passed Milestone-3 this week (and yes, it was painful), let's evaluate where we are with cinder Yoga features: - https://blueprints.launchpad.net/cinder/yoga Note: You must apply for a Feature Freeze Exception (FFE) by 17:00 UTC on Tuesday 1 March. Features granted an FFE must be in the gate by 20:00 UTC on Monday 7 March. Being granted an FFE is not a guarantee that your feature will be included in Yoga. FFE Details: ------------------ ibm-svf-portset - https://blueprints.launchpad.net/cinder/+spec/ibm-svf-portset - https://review.opendev.org/c/openstack/cinder/+/817351 - no +2s because third-party CI isn't passing - let's face it, no one is going to review this with failing CI even if it gets an FFE - must apply for an FFE The Third-Party CI for this review is IBM Storage CI. As the storage was done last week the CI failed. But today Zuul and IBM Storage CI both passed successfully. The portset has been tested throughly and reviewed by several reviewers in the last 2 months. All the comments are addressed and tested. The review has received a +2 from Rajat and +1 from Eric and Brian. The review is ready to be merged. Thanks and Regards, Harsh Ailani

2 1

[PTLs][release] Yoga Cycle Highligts
by Előd Illés 28 Feb '22

28 Feb '22

Hi, This is a reminder, that *this week* is the week for Cycle highlights [1][2]! They need to be added to deliverable yamls so that they can be included in release marketing preparations. (See the details about how to add them at the project team guide [3].) [1] https://releases.openstack.org/yoga/schedule.html [2] https://releases.openstack.org/yoga/schedule.html#y-cycle-highlights [3] https://docs.openstack.org/project-team-guide/release-management.html#cycle… Thanks, Előd Illés irc: elodilles

2 1

[neutron] Bug deputy report for week of 21. 02. 2022
by Lajos Katona 28 Feb '22

28 Feb '22

Hi Neutron Team I was bug deputy in neutron last week. It was a very quiet week again. Needs More attention ================= * Duplicate IP address on LSPs in the same LS lead to unpredictable flow output (https://bugs.launchpad.net/neutron/+bug/1961046 ) * [ovn-octavia-provider] OVN NB DB timeouts ( https://bugs.launchpad.net/neutron/+bug/1961874 ) ** perhaps not Neutron related, but more a pkg version problem. Critical ====== * Network interface not found in namespace https://bugs.launchpad.net/neutron/+bug/1961740 ** In progress: https://review.opendev.org/c/openstack/neutron/+/830622 High ==== * Transition to SQLAlchemy 2.0 ( https://bugs.launchpad.net/neutron/+bug/1962153) * [Prefix Delegation] router add segment fails with Subnet for router interface must have a gateway IP ( https://bugs.launchpad.net/neutron/+bug/1962306 ) * [ntp] "test_network_attached_with_two_routers" randomly failing ( https://bugs.launchpad.net/neutron/+bug/1962167) ** In progress: https://review.opendev.org/c/openstack/neutron/+/830813 Low ==== * There may be a typo in the neutron document whose the title is 'Manual install & Configuration' (https://bugs.launchpad.net/neutron/+bug/1962324) Invalid ====== * generate_config_file_samples.sh fails with invalid literal for int() with base 10 (https://bugs.launchpad.net/neutron/+bug/1961906) Regards Lajos Katona (lajoskatona)

1 0

[ops][nova] How to update from N to N+3 (and manage nova services that don't start because they find too old compute nodes...)
by Massimo Sgaravatto 28 Feb '22

28 Feb '22

Dear all When we upgraded our Cloud from Rocky to Train we followed the following procedure: 1) Shutdown of all services on the controller and compute nodes 2) Update from Rocky to Stein of controller (just to do the dbsyncs) 3) Update from Stein to Train of controller 4) Update from Rocky to Train of compute nodes We are trying to do the same to update from Train to Xena, but now there is a problem because nova services on the controller node refuse to start since they find too old compute nodes (this is indeed a new feature, properly documented in the release notes). As a workaround we had to manually modify the "version" field of the compute nodes in the nova.services table. Is it ok, or is there a cleaner way to manage the issue ? Thanks, Massimo

5 10

[devstack][openstack-qa] DevStack upgrade betweem major releases
by Eduardo Santos 27 Feb '22

27 Feb '22

Hello folks, What is the procedure for upgrading a DevSack deployment from one major release to another? I didn't find any information on this in the official documentation. [1] My team maintains DevStack deployments used to provision virtual machines to developers. How can we, let's say, upgrade a stable/xena DevStack to stable/yoga, when it's released? Best regards, Eduardo Santos [1] https://docs.openstack.org/devstack/latest/

3 2

[TripleO] Gate blocker - centos-9 standalone and multinode
by Bhagyashri Shewale 27 Feb '22

27 Feb '22

Hi All, We have an issue affecting standalone and multinode centos-9 check/gate jobs due to tempest test failure. Details: https://bugs.launchpad.net/tripleo/+bug/1962298 We are currently deciding on the best course of action for unblocking this issue. We will post an update once the check/gate is clear. Until then, please hold on rechecking. Thanks and Regards Bhagyashri Shewale

2 1

[Manila] Manila Collaborative Review Session - Thursday, March 10th
by Liron Kuchlani 27 Feb '22

27 Feb '22

Hi all, We are planning a Manila collaborative review session on Thursday, March 10th, to walk through the following proposed feature: - Add S-RBAC tests for manila [1] The session will start at 14:30 UTC and continue through the first half of the weekly upstream manila community meeting as needed. We will use an etherpad [2] during the session to capture notes and discussions. Hope you can all join us, [1] https://review.opendev.org/c/openstack/manila-tempest-plugin/+/805938 [2] https://etherpad.opendev.org/p/Manila-S-RBAC-collaborative-review

3 3

[cinder] Yoga FEATURE FREEZE in effect
by Brian Rosmaita 26 Feb '22

26 Feb '22

Hello Argonauts, Having passed Milestone-3 this week (and yes, it was painful), let's evaluate where we are with cinder Yoga features: - https://blueprints.launchpad.net/cinder/yoga Note: You must apply for a Feature Freeze Exception (FFE) by 17:00 UTC on Tuesday 1 March. Features granted an FFE must be in the gate by 20:00 UTC on Monday 7 March. Being granted an FFE is not a guarantee that your feature will be included in Yoga. Note to reviewers: please concentrate on the below over the next week. 1. Complete transition to Alembic - https://blueprints.launchpad.net/cinder/+spec/complete-transition-to-alembic - this is essential technical debt elimination - has a Feature Freeze Exception 2. Reset State Robustification - https://blueprints.launchpad.net/cinder/+spec/reset-state-robustification - Tushar has been working patiently on this forever - not a destabilizing change - has a Feature Freeze Exception - let's prioritize getting the base patch reviewed and merged, and we can see how far we can work up the stack before 7 March. - https://review.opendev.org/c/openstack/cinder/+/773985/ Driver features 3. HPE Nimble driver rename - https://blueprints.launchpad.net/cinder/+spec/nimble-change-location - https://review.opendev.org/c/openstack/cinder/+/786054 - has one +2 - patch has passed third party CI configured with the old name *and* with the rename - has an FFE Hitachi VSP driver The below require this non-feature patch, which addresses followup issues - https://review.opendev.org/c/openstack/cinder/+/827259/ - has one +2 - doesn't need an FFE because it's a bugfix, but let's get it reviewed and merged! 4. Support AIX as host OS type for VSP Driver - https://blueprints.launchpad.net/cinder/+spec/hitachi-vsp-aix-os-type - https://review.opendev.org/c/openstack/cinder/+/828061 - has one +2 - has an FFE 5. Target Port Assignment for VSP Driver - https://blueprints.launchpad.net/cinder/+spec/hitachi-vsp-tgt-port-asgn - https://review.opendev.org/c/openstack/cinder/+/828060 - has one +2 - has an FFE Questionable: 1. The Return of Make Cinder Consistent and Secure RBAC Ready - https://blueprints.launchpad.net/cinder/+spec/s-rbac-ready-y - community goal - I will meet with the cinder Zed PTL to discuss what to do about this one (may give a FFE for just part) 2. Hitachi: Port Scheduler for VSP Driver - https://blueprints.launchpad.net/cinder/+spec/hitachi-vsp-port-scheduler - https://review.opendev.org/c/openstack/cinder/+/828696 - Code and tests look mostly fine, and CI is passing - some really minor issues and needs a release note - needs to be rebased on latest version of 828060 - not giving an auto-FFE because it hasn't had a +2 yet - must apply for an FFE 3. ibm-svf-portset - https://blueprints.launchpad.net/cinder/+spec/ibm-svf-portset - https://review.opendev.org/c/openstack/cinder/+/817351 - no +2s because third-party CI isn't passing - let's face it, no one is going to review this with failing CI even if it gets an FFE - must apply for an FFE

1 0

[Magnum] heat-container-agent not able to talk to keystone
by Satish Patel 26 Feb '22

26 Feb '22

Folks, I am trying to deploy k8s cluster using magnum on openstack and found cluster creation stuck during kube master heat deployment and when i look into logs i found following Feb 25 22:09:26 k8s-foo-jqpxkt2y7e46-master-0 heat-container-agent[2342]: Authorization failed: Unable to establish connection to http://192.168.75.100:5000/v3/auth/tokens Feb 25 22:09:26 k8s-foo-jqpxkt2y7e46-master-0 heat-container-agent[2342]: Source [heat] Unavailable. Feb 25 22:09:26 k8s-foo-jqpxkt2y7e46-master-0 podman[2311]: Authorization failed: Unable to establish connection to http://192.168.75.100:5000/v3/auth/tokens Feb 25 22:09:26 k8s-foo-jqpxkt2y7e46-master-0 podman[2311]: Source [heat] Unavailable. In my deployment it's a private cloud so all control plane components running on private address space and k8s cluster created their own private network which is not routable so the kube master node can't talk to keystone. I can't put my HAProxy on a public address. In that case what are the options I have? I am running OVN for networking deployed by kolla-ansible. ~S

1 0

[manila] Yoga FFE request
by Fernando Ferraz 26 Feb '22

26 Feb '22

Hi Team, I'd like to request a FFE for the following changes we have been working on for the Yoga cycle. They are all part of the effort to partially implement spec *Add spec for multiple subnet share servers* *[1]* in Manila.: 826928: Support multiple subnets per AZ https://review.opendev.org/c/openstack/python-manilaclient/+/826928 826462: Container: Multiple subnets per AZ https://review.opendev.org/c/openstack/manila/+/826462 825155: NetApp ONTAP: Add support to multiple subnets per AZ https://review.opendev.org/c/openstack/manila/+/825155 826928: Support multiple subnets per AZ https://review.opendev.org/c/openstack/python-manilaclient/+/826928 All changes were submitted in time and there has been significant progress in reviews until this point. [1] https://review.opendev.org/c/openstack/manila-specs/+/619925 Regards, Fernando

2 2

[manila] RC1 bugsquash next week, no weekly IRC meetings until 17th March 2022
by Goutham Pacha Ravi 26 Feb '22

26 Feb '22

Hello there zorillas, It's time again to gather and squash some bugs together! We're hosting a bugsquash week between 3rd March 2022 and 10th March 2022. We've a preliminary list of bugs scoped out [1]. We'd love for you to participate by claiming a bug or two to fix during the week and reviewing bug fixes. Some of these bug fixes are in-progress, and we'll be conducting collaborative reviews to merge them during the week. If you'd like to work on something, please add it to the list [1] We'll use meetpad [2] to hang out opportunistically during the week at different times to review code or brainstorm, please watch the chatter on OFTC's #openstack-manila. However, a few scheduled events: * We'll have a kick-off at 1500 UTC on 3rd March 2022 * A "almost there" check in on 8th March 2022 at 1600 UTC on 8th March 2022 * A collab-review for S-RBAC tempest tests [3] at 1430 UTC on 10th March 2022 * A wrap up for the bugsquash week at 1530 UTC on 10th March 2022 All these will occur in the meetpad room; and these times overlap with our weekly IRC meetings - so we'll skip those. If you have any topics to discuss, please call our attention on this mailing list or on OFTC's #openstack-manila. Thanks, and hope to see you there! Goutham [1] https://ethercalc.openstack.org/t727llczm00f [2] https://meetpad.opendev.org/ManilaYogaRC1Bugsquash [3] http://lists.openstack.org/pipermail/openstack-discuss/2022-February/027329…

1 0

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

25 Feb '22

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * We had this week's meeting on 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-02-24-15.00.log.html * Next week's meeting is on 4th March Thursday 15:00 UTC, feel free to add the topic on the agenda[1] by 3rd March. 2. What we completed this week: ========================= * Zed cycle technical election[2] * Switch Keystone back to PTL model[3] 3. Activities In progress: ================== TC Tracker for Yoga cycle ------------------------------ * This etherpad includes the Yoga cycle targets/working items for TC[4]. 2 out of 9 items are completed. Open Reviews ----------------- * Eight open reviews for ongoing activities[5]. Zed cycle Leaderless projects ---------------------------------- As elections are closed, 17 projects are missing the nomination and out of those 11 have the late nomination. 6 projects are still seeking leaders. As the next step, TC will work on the assignment of leaders if we find any other steps on these leaderless projects[6]. Zed cycle testing runtime ------------------------------ I started the Zed cycle testing runtime, please check and give any objection if there is any[7] PTG Preparation -------------------- I have started the etherpad for TC PTG[8] preparation as well as for TC+Community Leaders sessions[9]. Also, doodle poll to select the slots[10] Testing and bumping the lower bounds in requirements.txt --------------------------------------------------------------------- Brian brought this topic while there was discussion on os-bricks bumping the minimum in requirements.rst[11]. As we do not test the lower bounds, we are not sure if existing lower bounds work or not. Telling anyone to reply on those is no guarantee that they will work or not. As TC, we agreed to give more clear direction on lower bounds and that is why we will discuss this topic in Zed PTG. Meanwhile, os-brick bumping the minimum is fine. Release identification and release name ----------------------------------------------- The proposal is under review and updates [12] Dropping tags framework ------------------------------ part1 of this is merged[13], part-2 of updating release script and other tags migration is under-progress. TC position on release cadence ------------------------------------- The proposal is under review and updates [14]. Fixing Zuul config error ---------------------------- Requesting projects with zuul config error to look into those and fix them which should not take much time[15]. Project updates ------------------- * Retire js-openstack-lib (waiting on Adjutant to have new PTL/maintainer) [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] http://lists.openstack.org/pipermail/openstack-discuss/2022-February/027412… http://lists.openstack.org/pipermail/openstack-discuss/2022-February/027411… [3] https://review.opendev.org/c/openstack/governance/+/829037 [4] https://etherpad.opendev.org/p/tc-yoga-tracker [5] https://review.opendev.org/q/projects:openstack/governance+status:open [6] https://etherpad.opendev.org/p/zed-leaderless [7] https://review.opendev.org/c/openstack/governance/+/830454 [8] https://etherpad.opendev.org/p/tc-zed-ptg [9] https://etherpad.opendev.org/p/tc-ptl-interaction-zed [10] https://doodle.com/poll/gz4dy67vmew5wmn9 https://doodle.com/poll/dcer6i3wk2b8eim3 [11] http://lists.openstack.org/pipermail/openstack-discuss/2022-February/027343… https://review.opendev.org/c/openstack/os-brick/+/828802 [12] https://review.opendev.org/c/openstack/governance/+/829563 [13] https://review.opendev.org/c/openstack/governance/+/822900 [14] https://review.opendev.org/c/openstack/governance/+/828777 [15] https://etherpad.opendev.org/p/zuul-config-error-openstack [16] https://review.opendev.org/c/openstack/governance/+/798540 [17] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [18] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0

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

25 Feb '22

Development Focus ----------------- We just passed feature freeze! Until release branches are cut, you should stop accepting featureful changes to deliverables following the cycle-with-rc release model, or to libraries. Exceptions should be discussed on separate threads on the mailing-list, and feature freeze exceptions approved by the team's PTL. Focus should be on finding and fixing release-critical bugs, so that release candidates and final versions of the Yogadeliverables can be proposed, well ahead of the final Yogarelease date. General Information ------------------- We are still finishing up processing a few release requests, but the Yogarelease requirements are now frozen. If new library releases are needed to fix release-critical bugs in Yoga, you must request a Requirements Freeze Exception (RFE) from the requirements team before we can do a new release to avoid having something released in Yoga that is not actually usable. This is done by posting to the openstack-discuss mailing list with a subject line similar to: [$PROJECT][requirements] RFE requested for $PROJECT_LIB Include justification/reasoning for why a RFE is needed for this lib. If/when the requirements team OKs the post-freeze update, we can then process a new release. A soft String freeze is now in effect, in order to let the I18N team do the translation work in good conditions. In Horizon and the various dashboard plugins, you should stop accepting changes that modify user-visible strings. Exceptions should be discussed on the mailing-list. By March 24th, 2022this will become a hard string freeze, with no changes in user-visible strings allowed. Actions ------- stable/yogabranches should be created soon for all not-already-branched libraries. You should expect 2-3 changes to be proposed for each: a .gitreview update, a reno update (skipped for projects not using reno), and a tox.ini constraints URL update. Please review those in priority so that the branch can be functional ASAP. The Prelude section of reno release notes is rendered as the top level overview for the release. Any important overall messaging for Yoga changes should be added there to make sure the consumers of your release notes see them. Finally, if you haven't proposed Yogacycle-highlights yet, you are already late to the party. Please see our email for details: http://lists.openstack.org/pipermail/openstack-discuss/2022-February/027361… Upcoming Deadlines & Dates -------------------------- RC1 deadline: March 10th, 2022(R-3 week) Final RC deadline: March 24th, 2022(R-1 week) Final Yogarelease: March 30th, 2022 Next PTG: April 4 - 8, 2022 (virtual) ElődIllés irc: elodilles

1 0

[all][elections][tc] Technical Committee Election Results
by Ghanshyam Mann 25 Feb '22

25 Feb '22

For 5 TC open seats, there were 5 candidates so no election was required. Please join me in congratulating the 5 newly elected members of the Technical Committee (TC). Amy Marrich (spotz) Arne Wiebalck (arnewiebalck) Kristi Nikolla (knikolla) Brian Rosmaita (rosmaita) Sławek Kapłoński (slaweq) Full results: no election required. Election process details and results are also available here: https://governance.openstack.org/election/ Thank you to all of the candidates, having a good group of candidates helps engage the community in our democratic process. Thank you for another great round. -gmann, on behalf of the OpenStack Technical Election Officials

3 2

[all][elections][ptl] Project Team Lead Zed Election Conclusion and Results
by Ghanshyam Mann 25 Feb '22

25 Feb '22

Thank you to the all candidates who put their names forward for Project Team Lead (PTL) in this election. A healthy, open process breeds trust in our decision making capability. Thank you to all those who make this process possible. Now for the results of the PTL election process, please join me in extending congratulations to the following PTLs: * Barbican : Douglas Mendizábal * Blazar : Pierre Riteau * Cinder : Rajat Dhasmana * Cloudkitty : Rafael Weingartner * Cyborg : Bailin Zhang * Designate : Michael Johnson * Ec2 Api : Andrey Pavlov * Glance : Abhishek Kekane * Horizon : Vishal Manchanda * Ironic : Iury Gregory Melo Ferreira * Keystone : Douglas Mendizábal * Kolla : Michal Nasiadka * Kuryr : Maysa de Macedo Souza * Manila : Carlos Silva * Neutron : Lajos Katona * Nova : Sylvain Bauza * Octavia : Gregory Thiemonge * OpenStack Helm : Gage Hugo * OpenStackAnsible : Dmitriy Rabotyagov * OpenStackSDK : Artem Goncharov * Puppet OpenStack : Takashi Kajinami * Quality Assurance : Martin Kopec * Rally : Andrey Kurilin * Release Management : Elod Illes * Requirements : Matthew Thode * Sahara : Fossen Qiu * Storlets : Takashi Kajinami * Swift : Tim Burke * Tacker : Yasufumi Ogawa * Telemetry : Matthias Runge * Tripleo : James Slagle * Vitrage : Eyal Bar-Ilan * Winstackers : Lucian Petrut For remaining projects (without PTL candaidates), TC will work on the appointment. Elections: no election required. Election process details and results are also available here: https://governance.openstack.org/election/ Thank you to all involved in the PTL election process -gmann, on behalf of the OpenStack Technical Election Officials

1 0

[neutron] Drivers meeting agenda - 25.02.2022.
by Lajos Katona 24 Feb '22

24 Feb '22

Hi Neutron Drivers, The agenda for tomorrow's drivers meeting is at [1]. * [RFE][L3][OVS] use controller (ovs-agent) send (packet-out) RA to (VMs) ports (https://bugs.launchpad.net/neutron/+bug/1961011 ) * [RFE][OVN] Support DNS subdomains at a network level ( https://bugs.launchpad.net/neutron/+bug/1960850 ) * Gratuitous ARPs are not sent during master transition: ( https://bugs.launchpad.net/neutron/+bug/1952907) ** For this one there are a few wip patches: ** https://review.opendev.org/c/openstack/neutron/+/821434 ** https://review.opendev.org/c/openstack/neutron/+/821433 ** https://review.opendev.org/c/openstack/neutron/+/712474 [1] https://wiki.openstack.org/wiki/Meetings/NeutronDrivers#Agenda See you at the meeting tomorrow. Lajos Katona (lajoskatona)

1 0