August 2022 - openstack-discuss - lists.openstack.org

[all][tc] What's happening in Technical Committee: summary 2022 Aug 19
by Slawek Kaplonski 18 Aug '22

18 Aug '22

Hi, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * We had this week's meeting on Aug 18. Most of the meeting discussions are summarized in this email. Meeting full logs are available at https://meetings.opendev.org/meetings/tc/2022/tc.2022-08-18-15.00.log.html * Next TC weekly meeting will be on 25 Aug Thursday at 15:00 UTC, feel free to add the topic on the agenda[1] by Aug 3. 2. What we completed this week: ========================= 3. Activities In progress: ================== TC Tracker for Zed cycle ------------------------------ * Zed tracker etherpad includes the TC working items[2], Two are completed and others items are in-progress. Open Reviews ----------------- * Four open reviews for ongoing activities[3]. 2021 User Survey TC Question Analysis ----------------------------------------------- No update on this. The survey summary is up for review[4]. Feel free to check and provide feedback. Zed cycle Leaderless projects ---------------------------------- Dale Smith volunteer to be PTL for Adjutant project [5] Fixing Zuul config error ---------------------------- Requesting projects with zuul config error to look into those and fix them which should not take much time[6][7]. Project updates ------------------- * Retire openstack-help-addons [8] 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[9]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15 UTC [10] 3. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. [1] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting [2] https://etherpad.opendev.org/p/tc-zed-tracker [3] https://review.opendev.org/q/projects:openstack/governance+status:open [4] https://review.opendev.org/c/openstack/governance/+/836888 [5] https://review.opendev.org/c/openstack/governance/+/849606 [6] https://etherpad.opendev.org/p/zuul-config-error-openstack [7] http://lists.openstack.org/pipermail/openstack-discuss/2022-May/028603.html [8] https://review.opendev.org/c/openstack/governance/+/851859 [9] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [10] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0

[nova] Is the VMware NSX CI still being maintained?
by melanie witt 18 Aug '22

18 Aug '22

Hi all, I have noticed lately the VMware NSX CI does not seem to be running since March/April of this year based on casual gerrit search [1]. More recently, maybe starting in May, I have seen it post comments on reviews but they say: Build failed - ext-nova-zuul : NOT_REGISTERED Does anyone know whether this job is still being maintained and if it will be fixed? Thanks, -melwitt [1] https://review.opendev.org/q/reviewer:%2522VMware+NSX+CI%2522+project:opens…

1 0

Re: [all][tc] Technical Committee next weekly meeting on 2022 Aug 18 at 1500 UTC
by Ghanshyam Mann 18 Aug '22

18 Aug '22

Hello Everyone, Below is the agenda for Today's TC meeting schedule at 1500 UTC. https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting * Roll call * Follow up on past action items * Gate health check ** Bare 'recheck' state *** https://etherpad.opendev.org/p/recheck-weekly-summary * 2023.1 cycle PTG Planning ** Encourage projects to schedule 'operator hours' as a separate slot in PTG(avoiding conflicts among other projects 'operator hours') * Open Reviews ** https://review.opendev.org/q/projects:openstack/governance+is:open -gmann

1 0

[neutron] Drivers meeting agenda - 19.08.2022.
by Lajos Katona 18 Aug '22

18 Aug '22

Hi Neutron Drivers, The agenda for tomorrow's drivers meeting is at [1]. We have the following RFEs to discuss tomorrow: [RFE] Add possibility to define default security group rules (#link https://bugs.launchpad.net/neutron/+bug/1983053 ) [rfe][fwaas]support standard_attrs for firewall_group (#link https://bugs.launchpad.net/neutron/+bug/1986906 ) [1] https://wiki.openstack.org/wiki/Meetings/NeutronDrivers#Agenda See you at the meeting tomorrow. Lajos Katona (lajoskatona)

1 0

Weird behaviour on a provider net
by Derek O keeffe 18 Aug '22

18 Aug '22

Hi all, We have an Openstack Victoria cluster deployed and a provider network (IPv4) created that worked fine for months. Lately we've noticed that about 30-40% of the VM's that are spun up using this network are inaccessible over ssh, Permission denied (publickey). Also, if you add a customisation script to create a password for the Ubuntu user that fails too. Initially we thought it was confined to one/two compute nodes but further testing this week shows that it can be any of the 6 compute nodes we have and always the original two that we identified as being the problem. If we create the VM's from the cli and send them to specific hosts everything works fine including the original two hosts that had issues. We're finding it hard to nail down the cause of this because it's not consistent behaviour so any tips on where to investigate would be welcome, we have a second provider net (IPv4 & IPv6) that works fine and have went through all the configs to see if there's any difference and all are identical over the hosts. Thanks in advance for any info. Regards,Derek

2 1

Which deployment Method for a production cloud ?
by KK CHN 18 Aug '22

18 Aug '22

List, I want to install Openstack Xena version on a DELL ( R650 2 CPU and 40 cores . 2.4 TB) server machine. Operating System preference is Debian 10. I want to deploy this for production use with Ceph OSDs. There are four methods described in the URL : Confused which to select. https://docs.openstack.org/xena/deploy/ 1. Using Charms deployment 2. Deploy openstack using Ansible in Docker containers 3. Openstack - Ansible Deployment guide. 4. Triple O deployment guide Which method do I have to follow a full fledged production deployment ? why ? Going ahead with Ansible and Docker is a best option or not ? Your kind guidance requested.. Thanks in advance, Krish ps:- Once Completed this installation I have to extend this as a High available(HA) Multi Node cloud. (multi node production cloud with 3 Controllers, 6 compute Nodes and 3 Storage nodes with Ceph OSD pools) . Request to consider this future scalability requirement while answering my query.

2 1

[openstack-ansible][wallaby] lxc-containers-create.yml fails when specifying a container group
by Taltavull Jean-François 18 Aug '22

18 Aug '22

Hello everyone, Whatever the container group, lxc-containers-create playbook fails when specifying the group with -l option. For example : $ sudo openstack-ansible lxc-containers-create.yml -l repo_container Fails with: TASK [lxc_container_create : Gather variables for each operating system] ******************************************************************************************************************************************************************************************************fatal: [p3controller1a_repo_container-b54c9eba]: FAILED! => {"msg": "No file was found when using first_found. Use errors='ignore' to allow this task to be skipped if no files are found"} fatal: [p3controller1b_repo_container-1c7f8c1f]: FAILED! => {"msg": "No file was found when using first_found. Use errors='ignore' to allow this task to be skipped if no files are found"} fatal: [p3controller1c_repo_container-1e73e8a7]: FAILED! => {"msg": "No file was found when using first_found. Use errors='ignore' to allow this task to be skipped if no files are found"} Any similar experience ? Any idea ? Thank you, Jean-Francois

2 2

[Neutron][Octavia][ovn-octavia-provider] proposing Fernando Royo for ovn-octavia-provider core reviewer
by Lajos Katona 17 Aug '22

17 Aug '22

Hi I would like to propose Fernando Royo (froyo) as a core reviewer to the ovn-octavia-provider project. Fernando is very active in the project (see [1] and [2]). As ovn-octavia-provider is a link between Neutron and Octavia I ask both Neutron and Octavia cores to vote by answering to this thread, to have a final decision. Thanks for your consideration. [1]: https://review.opendev.org/q/owner:froyo%2540redhat.com [2]: https://www.stackalytics.io/report/contribution?module=neutron-group&projec… Cheers Lajos

6 6

[cinder] Bug deputy report for week of 08-17-2022
by Sofia Enriquez 17 Aug '22

17 Aug '22

This is a bug report from 08-10-2022 to 08-17-2022. Agenda: https://etherpad.opendev.org/p/cinder-bug-squad-meeting ----------------------------------------------------------------------------------------- Medium - https://bugs.launchpad.net/cinder/+bug/1985962 "Wrong volume_quota exception msg when extending volume_size." Fix proposed to master. Low - https://bugs.launchpad.net/cinder/+bug/1985065 "[Storwize] mkhost command failure". Fix proposed to master. - https://bugs.launchpad.net/cinder/+bug/1986658 "NetApp driver is hitting the QoS policy limit due soft deletion." Fix proposed to master. Cheers, Sofia -- 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

[oslo][stable] Backport of the default value of the config option change
by Slawek Kaplonski 17 Aug '22

17 Aug '22

Hi, Some time ago oslo.messaging changed default value of the "heartbeat_in_pthread" config option to "True" [1]. As was noticed some time ago, this don't works well with nova-compute - see bug [2] for details. Recently we noticed in our downstream Red Hat OpenStack, that it's not only nova-compute which don't works well with it and can hangs. We saw the same issue in various neutron agent processes. And it seems that it can be the same for any non-wsgi service which is using rabbitmq to send heartbeats. So giving all of that, I just proposed change of the default value of that config option to be "False" again [3]. And my question is - would it be possible and acceptable to backport such change up to stable/wallaby (if and when it will be approved for master of course). IMO this could be useful for users as using this option set as "True" be default don't makes any sense for the non-wsgi applications really and may cause more bad then good things really. What are You opinions about it? [1] https://review.opendev.org/c/openstack/oslo.messaging/+/747395 [2] https://bugs.launchpad.net/oslo.messaging/+bug/1934937 [3] https://review.opendev.org/c/openstack/oslo.messaging/+/852251/ -- Slawek Kaplonski Principal Software Engineer Red Hat

13 14

[glance] Antelope PTG Planning
by Abhishek Kekane 16 Aug '22

16 Aug '22

Hi everyone, Virtual PTG for the Antelope cycle will be held between 17th - 21st October [1]. I've also created an etherpad [2] to collect ideas/topics for the PTG sessions. If you have anything to discuss, please don't hesitate to write it there. [1] https://openinfra-ptg.eventbrite.com/ [2] https://etherpad.opendev.org/p/antelope-ptg-glance-planning Thanks, Abhishek Kekane

1 0

[kolla-ansible][octavia] need networking help
by Stuart Whitman 16 Aug '22

16 Aug '22

Hello, I enabled Octavia on a kolla-ansible installed Openstack cluster. When I try to launch a loadbalancer instance, the octavia-worker.log file reports: "WARNING octavia.amphorae.drivers.haproxy.rest_api_driver [-] Could not connect to instance." I researched enough to know that the problem has to do with networking between the controller and the lb-mgmt-net network. I initially overlooked this in the kolla-ansible Octavia documentation: "If using a VLAN provider network, ensure that the traffic is also bridged to Open vSwitch on the controllers." But, I don't know how to do it. Help to create the necessary bridge would be greatly appreciated. Thanks, -Stu _____________________________________ The information contained in this e-mail and any attachments from Group W may contain confidential and/or proprietary information and is intended only for the named recipient to whom it was originally addressed. If you are not the intended recipient, be aware that any disclosure, distribution, or copying of this e-mail or its attachments is strictly prohibited. If you have received this e-mail in error, please notify the sender immediately of that fact by return e-mail and permanently delete the e-mail and any attachments to it.

4 6

[horizon][plugins] Horizon angular based plugins are broken after migrating to angularjs 1.8.2.2
by vishal manchanda 16 Aug '22

16 Aug '22

Hello everyone, Horizon team recently migrated XStatic-Angular 1.5.8.0->1.8.2.2 [1] and after that many horizon angular based plugins start failing [2]. We already fixed these issues in horizon [3]. So I guess we need to fix the similar thing in horizon plugins. Why did we migrated Angular 1.5.8.0->1.8.2.2? The angularjs version is updated 1.5.8.0->1.8.2.2 to include the CVE fixed in the latest version. Also, there is a security bug reported for the same [4]. I have also created an etherpad to track the progress for failed horizon plugins [5]. Action items for the horizon plugins team either fixed their plugins or review/merge the patch pushed by horizon team members on priority basis to fix the gate. The npm jobs are failing in below horizon plugins : • ironic-ui • octavia-dashboard • senlin-dashboard • designate-dashboard • vitrage-dashboard • murano-dashboard • zaqar-ui • zun-ui • magnum-ui In case of any queries, please feel free to reach out to Horizon channel #openstack-horizon. Thanks & Regards, Vishal Manchanda(irc: vishalmanchanda) [1] https://review.opendev.org/c/openstack/requirements/+/844099 [2] https://review.opendev.org/c/openstack/horizon/+/845733 [3] https://review.opendev.org/c/openstack/horizon/+/843346 [4] https://bugs.launchpad.net/horizon/+bug/1955556 [5] https://etherpad.opendev.org/p/Fix_Horizon_Plugins_With_Angularjs_v1.8.2.2

2 2

[neutron] CI meeting - agenda for 16.08.2022
by Slawek Kaplonski 16 Aug '22

16 Aug '22

Hi, Agenda for today's Neutron CI meeting is at [1]. This will be video meeting, which we will have on [2]. [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

Metering, billing software components for Openstack
by KK CHN 16 Aug '22

16 Aug '22

List, We are running our datacenter using the Ussuri version. Planning to upgrade to higher versions soon. 1. What are the metering, billing and metric solutions for ussuri and other latest openstack versions ? 2. The ceilometer and gnocchi is the way forward or ? People are using any latest tools for the best results pls share your thoughts. Any thoughts most welcome. Krish

3 3

[openstack-helm] No meeting tomorrow
by Gage Hugo 15 Aug '22

15 Aug '22

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

1 0

[neutron] Bug deputy report (week starting on Aug-8-2022)
by Bernard Cafarelli 15 Aug '22

15 Aug '22

Hello neutrinos, it is time again to start a new bug deputy rotation: https://wiki.openstack.org/wiki/Network/Meetings#Bug_deputy and my turn for last week's bugs A relatively quiet week (it is the holiday season in quite a few parts of the world!) with fixes already merged for most bugs. Two bugs to highlight though (and in need of some neutron eyes): a manila job failing with IPv6 VMs (1940324) and a live-migration issue (1986003) Critical * neutron-tempest-plugin failing on networking-bagpipe tests - https://bugs.launchpad.net/neutron/+bug/1986534 networking-bagpipe also needed update after neutron-lib constants rehoming, fix merged: https://review.opendev.org/c/openstack/networking-bagpipe/+/852867 High * [CI][Devstack] Failing to SSH to test VMs with IPv6 - https://bugs.launchpad.net/neutron/+bug/1940324 LVM job for manila fails on IPv6 hosts with socket.timeout: timed out, if CI/IPv6 gurus can take a look and help manila team Medium * neutron-dynamic-routing: Continuous warning because of missing context wrapper - https://bugs.launchpad.net/neutron/+bug/1984238 Previous fix missed one context wrapper, fix by tkajinam https://review.opendev.org/c/openstack/neutron-dynamic-routing/+/852775 Low * Replace "click" with "cliff" - https://bugs.launchpad.net/neutron/+bug/1985049 Several patches in progress to update tools using click, see LP for details Original started as bug to add click to requirements - https://bugs.launchpad.net/neutron/+bug/1984109 * [OVN] Remove "FIPAddDeleteEvent" event - https://bugs.launchpad.net/neutron/+bug/1985096 Unassigned cleanup bug, workaround is not needed since OVN v20.03.0 * DeprecationWarning: Using the 'user' argument is deprecated in version '2.18' and will be removed in version '3.0', please use the 'user_id' argument instead - https://bugs.launchpad.net/neutron/+bug/1986418 Fix merged https://review.opendev.org/c/openstack/neutron/+/853050 * DeprecationWarning: invalid escape sequence \u - https://bugs.launchpad.net/neutron/+bug/1986421 Fix merged https://review.opendev.org/c/openstack/neutron/+/853051 * PkgResourcesDeprecationWarning: <MagicMock name='execute().split().__getitem__().__getitem__()' id='140417024565696'> is an invalid version and will not be supported in a future release - https://bugs.launchpad.net/neutron/+bug/1986428 Fix also merged: https://review.opendev.org/c/openstack/neutron/+/853053 Thanks Takashi Natsume for this series of deprecation fixes Untriaged * Exception in concurrent port binding activation - https://bugs.launchpad.net/neutron/+bug/1986003 Live migration issue that I did not have time to dig into - any takers? Have a nice week! -- Bernard Cafarelli

1 0

[Ansible] [Yoga] Infra LXC Cache Failure
by Father Vlasie 15 Aug '22

15 Aug '22

Hello everyone! I am trying to deploy Openstack Ansible with Rocky Linux 8.6. I have 3 infra nodes all running the same software/hardware specifications but the 3rd one keeps giving me the following error. This occurs when running setup-hosts.yml ---------- TASK [lxc_hosts : Ensure that the LXC cache has been prepared] ******************************************************************************* FAILED - RETRYING: [infra3]: Ensure that the LXC cache has been prepared (120 retries left). FAILED - RETRYING: [infra3]: Ensure that the LXC cache has been prepared (119 retries left). fatal: [infra3]: FAILED! => {"ansible_job_id": "205392349782.93369", "attempts": 3, "changed": true, "cmd": "chroot /var/lib/machines/rocky-8-amd64 /opt/cache-prep-commands.sh > /var/log/lxc-cache-prep-commands.log 2>&1", "delta": "0:00:16.353232", "end": "2022-08-15 12:59:42.058169", "finished": 1, "msg": "non-zero return code", "rc": 1, "results_file": "/root/.ansible_async/205392349782.93369", "start": "2022-08-15 12:59:25.704937", "started": 1, "stderr": "", "stderr_lines": [], "stdout": "", "stdout_lines": []} ---------- Thank you very much for any help! Father Vlasie

1 1

[Octavia] Monitor through Listener Prometheus Protocol
by Vu Tuan Dat 15 Aug '22

15 Aug '22

HI, I installed Prometheus on controller nodes. However, My prometheus instance cannot connect to Listener Prometheus endpoint because it's binded to VIP only in network namespace. Anyone can help? Thanks in advanced, Dat

2 1

[Ansible] [Yoga] Set rsyslog not to containerise
by Father Vlasie 15 Aug '22

15 Aug '22

Hello everyone! I am trying to deploy Openstack Ansible with Rocky Linux 8.6. I have a rsyslog host that is somewhat underpowered (RAM and CPU) and I thought it might help to run rsyslog without containerisation. I have searched but I have not been able to find an example of this.My guess is that I need to create a file in /etc/openstack_deploy/env.d What syntax and commands do I need? I have searched but I could not find any examples... Thank you very much! Father Vlasie

2 1

[ironic] Proposing Jacob Anders to sushy-core
by Iury Gregory 14 Aug '22

14 Aug '22

Hello ironic-cores and sushy-cores, I would like to propose Jacob Anders (janders irc) for sushy-core. He made great contributions to improve sushy to cover corner cases from different HW in the last releases, you can find some of his contributions in [1], please vote with +1/-1. [1] https://review.opendev.org/q/owner:janders%2540redhat.com+project:openstack… -- *Att[]'s* *Iury Gregory Melo Ferreira * *MSc in Computer Science at UFCG* *Ironic PTL * *Senior Software Engineer at Red Hat Brazil* *Social*: https://www.linkedin.com/in/iurygregory *E-mail: iurygregory(a)gmail.com <iurygregory(a)gmail.com>*

3 2

[Ansible] [Yoga] Not recognising Rocky Linux as supported
by Father Vlasie 12 Aug '22

12 Aug '22

Hello everyone! I am trying to deploy Openstack Ansible with Rocky Linux 8.6 on my target hosts. The documentation here (https://docs.openstack.org/project-deploy-guide/openstack-ansible/latest/ta…) says " • Centos 8 Stream 64-bit * Derivitives: Rocky Linux” under the list of supported operation systems. Ansible does not seem to check for the existence of RHEL 8 systems. :( But when I run “openstack-ansible setup-hosts.yml” I get the error: TASK [Check for a supported Operating System] ***************************************************************************************** fatal: [infra1]: FAILED! => { "assertion": "(ansible_facts['distribution'] == 'Debian' and ansible_facts['distribution_release'] == 'bullseye') or (ansible_facts['distribution'] == 'Ubuntu' and ansible_facts['distribution_release'] == 'focal') or (ansible_facts['distribution'] == 'Ubuntu' and ansible_facts['distribution_release'] == 'jammy') or (ansible_facts['os_family'] == 'RedHat' and ansible_facts['distribution_major_version'] == '9')", "changed": false, "evaluated_to": false, "msg": "The only supported platforms for this release are Debian 11 (Bullseye), Ubuntu 20.04 LTS (Focal), Ubuntu 22.04 (Jammy) and CentOS 9 Stream.\n” What should I do? Thank you!

3 2

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

12 Aug '22

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * We had this week's meeting on Aug 11. Most of the meeting discussions are summarized in this email. Meeting full logs are available @https://meetings.opendev.org/meetings/tc/2022/tc.2022-08-11-15.00.log.html * Next TC weekly meeting will be on Aug 18 Thursday at 15:00 UTC, feel free to add the topic on the agenda[1] by Aug 17. 2. What we completed this week: ========================= * None in this week. 3. Activities In progress: ================== TC Tracker for Zed cycle ------------------------------ * Zed tracker etherpad includes the TC working items[3], Two are completed and others items are in-progress. Open Reviews ----------------- * Two open reviews for ongoing activities[4]. OpenStack TC + Board member meeting ------------------------------------------------ As you might know, OpenStack TC and Board member had a informal meeting on Aug 10[5][6], I am summarizing the discussion here. The Openstack TC has presented the 'OpenStack Updates' to Board meeting in berlin. One of the key part of the updates were 'OpenStack community Challenges' and we could not finish the discussion or brainstorm on these in berlin meeting. We decided to continue the discussion on those (Slide#21)[7]. In this call, we can only cover the first challenge only 'Less Interaction with Operators & Users'. There is no doubt that we are facing this issue at noticeable level (RBAC is good example where we lacked the operator/user feedback). A lot of things including ML, events are discussed on why it is happening and how to improve it. Having ops meetup as a separate event is something many members raised concern about and it will be good to merge these events into other community events like Summit, PTG etc. To try the first step towards that we can invite or welcome operators in Oct virtual PTG and give them a feeling on merging the events with developers event can be beneficial to both the group. On that, Dan suggested the idea of scheduling the 'Operatos Hours' per project in PTG and there we will keep the discussion on operator-centric and the format they want. We continued the discussion on this in TC weekly meeting where we had mixed suggestions on the 'Operator Hours' schedule, either to ask each project to schedule it in their room and operator join or other way around. Before deciding any format, we will be asking operators about their preference. We will continue the discussion on 'OpenStack community Challenges' in the next call which is schedule on 20:00 UTC on Wednesday, November 16[8]. If anyone is interested, feel free to join it. 2023.1 cycle Technical Election (TC + PTL) planning ------------------------------------------------------------- Not much update on this but we will be seeing the election schedule proposed soon. 2023.1 cycle TC PTG planning ------------------------------------ We discussed about how to best encourage/invite operators into the PTG (I wrote in the above section) and based on the operators feedback we will proceed next. We will continue the discussion in the next meeting also. 2021 User Survey TC Question Analysis ----------------------------------------------- No update on this. The survey summary is up for review[9]. Feel free to check and provide feedback. Zed cycle Leaderless projects ---------------------------------- Dale Smith volunteer to be PTL for Adjutant project [10] Fixing Zuul config error ---------------------------- Requesting projects with zuul config error to look into those and fix them which should not take much time[11]12]. Project updates ------------------- * Retire openstack-helm-addons[13] 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] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting [2] https://review.opendev.org/c/openstack/governance/+/849997 [3] https://etherpad.opendev.org/p/tc-zed-tracker [4] https://review.opendev.org/q/projects:openstack/governance+status:open [5] https://lists.openstack.org/pipermail/openstack-discuss/2022-August/029886.… [6] https://etherpad.opendev.org/p/2022-08-board-openstack-sync [7] https://docs.google.com/presentation/d/1yCiZy_9A6hURXD0BRdr33OlK7Ugch5EgSvF… [8] https://lists.openstack.org/pipermail/openstack-discuss/2022-August/029968.… [9] https://review.opendev.org/c/openstack/governance/+/836888 [10] https://review.opendev.org/c/openstack/governance/+/849606 [11] https://etherpad.opendev.org/p/zuul-config-error-openstack [12] http://lists.openstack.org/pipermail/openstack-discuss/2022-May/028603.html [13] https://review.opendev.org/c/openstack/governance/+/849997 [14] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [15] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0

Re: [Ansible] [Yoga] Not recognising Rocky Linux as supported
by Father Vlasie 12 Aug '22

12 Aug '22

> On Aug 12, 2022, at 3:13 PM, openstack-discuss-request(a)lists.openstack.org wrote: > > Comparing https://opendev.org/openstack/openstack-ansible/src/branch/stable/yoga/play… <https://opendev.org/openstack/openstack-ansible/src/branch/stable/yoga/play…> to https://opendev.org/openstack/openstack-ansible/src/branch/master/playbooks… <https://opendev.org/openstack/openstack-ansible/src/branch/master/playbooks…> it appears that OpenStack Ansible has removed CentOS Stream/RHEL/Rocky 8 support on master, but the assertion allows it under Yoga. Based on the failure above you must be running master OSA? I would try running the Yoga branch instead. > > The master branch documentation likely needs to be updated as well. That worked perfectly, thank you! :)

1 0

[tc] November 2022 OpenInfra Board Sync
by Jeremy Stanley 12 Aug '22

12 Aug '22

The Open Infrastructure Foundation Board of Directors is endeavoring to engage in regular check-ins with official OpenInfra projects. The goal is for a loosely structured discussion one-hour in length, involving members of the board and the OpenStack TC, along with other interested community members. This is not intended to be a formal presentation, and no materials need to be prepared in advance. I've started an Etherpad where participants can brainstorm potential topics of conversation, time-permitting: https://etherpad.opendev.org/p/2022-11-board-openstack-sync At the conclusion of the August 10 discussion, we agreed to tentatively schedule the next call for 20:00 UTC on Wednesday, November 16, so I've attached a calendar file which can serve as a convenient schedule hold for this, in case anyone needs it. -- Jeremy Stanley

1 0