- openstack-discuss - lists.openstack.org

Openstack.io is down
by Elvira Garcia Ruiz 13 Sep '22

13 Sep '22

Hi everyone! I noticed that stackalytics.io has been down for several days now. As far as I know this was widely used by the community, although it is not part of OpenInfra as a project. I'm not sure who was maintaining this, but I just wanted to make them aware of the problem, and also thank them for keeping it up and running. Kind regards! Elvira García (irc:elvira)

5 5

[openstack yova][nova-spiceproxy] Spice proxy behind SSL termination: protocol mismatch error in horizon web UI
by 박경원 13 Sep '22

13 Sep '22

2 1

[tripleo] puppetlabs-apache: soon a just a bad memory?
by Cédric Jeanneret 13 Sep '22

13 Sep '22

Hello Community! TLDR; puppetlabs-apache broke us so many times, I'm proposing a way to get rid of it, using plain ansible. Some work is needed, but it's "easy", and will allow us to keep a hand on the whole configuration code. Longer version: You probably saw mails about issues with puppetlabs-apache releases breaking the CI (and, by extension, TripleO). Over and over and over again. Well, good news: this may be just a bad memory - though it will require some work :). I've been working on a couple of ansible roles[1] in order to just get the needed pieces we really need in TripleO: file generation. Once we get those 2 roles in, we'll be able to switch, service by service, away from puppet management for apache/httpd. There's already an on-going example[2] with ironic. Of course, as you can see, there's some work to do, even on the puppet side. But it's not really complicated, and can be done quickly. I'll do my best to move things, but be prepared to get pings from time to time if help is needed. I can't do all by myself, can I? ;) And if anyone wants to jump in and work on the transition, please do, and don't hesitate to reach to me, either by mail, or on #tripleo - I go there as Tengu. Cheers, C. [1] https://review.opendev.org/c/openstack/tripleo-ansible/+/853481 [2] https://review.opendev.org/q/topic:standalone%252Fapache -- Cédric Jeanneret (He/Him/His) Sr. Software Engineer - OpenStack Platform Deployment Framework TC Red Hat EMEA https://www.redhat.com/

1 0

[tripleo] Switching to nftables - it's coming soon!
by Cédric Jeanneret 13 Sep '22

13 Sep '22

Hello there, TLDR; we're about to switch to nftables[1], there are some changes described in the up-to-date doc. Reason is: faster, more modern interface, close to no possibility to get locked out of the system. Also, once it's switched, please use `nft list ruleset' instead of `iptables -L'. [1] https://review.opendev.org/c/openstack/tripleo-heat-templates/+/852808 Longer version: I've been working a good amount of time in order to get rid of the current tripleo_iptables custom action. On of the reasons here was the fact we could get locked out the overcloud if, for any reason, a network reset happens in ansible during the application of the rules. For the records, tripleo_iptables is calling the native "iptables" module from ansible, just doing a batching of the ruleset in an attempt to apply everything faster. It has some weird things, such as reversing the rule order before applying them using the "insert" action, meaning it will lock everything first, then open one by one the accesses. Knowing "ssh" is like 003 rule, you can imagine how things can go wrong. So, I took the opportunity to make some changes. While doing so, I saw `iptables' was just a compatibility wrapper for nftables - basically, `iptables' is a symlink to `iptables-nft', so I also took the opportunity to bypass it, and go straight for `nft'. Doing so, I created a new tripleo_nftables role in tripleo-ansible project; it's "just" creating files based on templates, then validates the whole lot of files, and applies all the rules in one single transaction. Compared to tripleo_iptables, it's really more robust, while being faster, and less prone to lock out and other unwanted things. The current state is: we're close, really close to switch things up. We're missing 2 patches in the CI to make the infra properly supported, and then, there's "the" switch itself. What will change: almost nothing: the way we create rules in tripleo-heat-templates and the different parameters therein doesn't change at all; the thing that will really change is the way to list the rules: instead of calling `iptables -vnL' or the like, you'll need to call `nft list ruleset'. Now, in order to make things easier, the doc is already up-to-date: https://docs.openstack.org/project-deploy-guide/tripleo-docs/latest/feature… As you will see, there will be some differences in the actual layout: all of the tripleo rules will be in dedicated chains, prefixed by TRIPLEO_ - for instance, TRIPLEO_INPUT, TRIPLEO_OUTPUT, TRIPLEO_FORWARD, and so on. This allows to get a cleaner layout, cleaner way to filter the output and, really important thing, to ensure we're cleaning dangling rules - the TRIPLEO_* chains will be flushed before the ruleset are added. All in one single transaction. Some more information/content: tripleo_nftables role: https://opendev.org/openstack/tripleo-ansible/src/branch/master/tripleo_ans… Doc: https://docs.openstack.org/project-deploy-guide/tripleo-docs/latest/feature… Debug files available in the CI: log of dropped packets: https://logserver.rdoproject.org/54/31954/87/check/periodic-tripleo-ci-cent… nftables configuration dump: https://logserver.rdoproject.org/54/31954/87/check/periodic-tripleo-ci-cent… nftables configuration: https://logserver.rdoproject.org/54/31954/87/check/periodic-tripleo-ci-cent… All of that can help understanding the potential issues you may encounter. As a side note, we've been testing the whole thing for about a month now, correcting issues, updating the doc and making sure at least all of the current CI jobs (yes: ALL) are green without any weird behavior. A doc has been created in order to list the current state, with what we've seen, what we've done: https://hackmd.io/F0W2gYw_SiaiWkowjFU9cw?view#NFTABLES-testing-results Brace yourself, the change is coming :). But it should be transparent ;). -- Cédric Jeanneret (He/Him/His) Sr. Software Engineer - OpenStack Platform Deployment Framework TC Red Hat EMEA https://www.redhat.com/

1 0

[publiccloud-sig] Bi-weekly meeting reminder
by Tobias Rydberg 13 Sep '22

13 Sep '22

Hi all, Tomorrow we will have our bi-weekly meeting at 0800 UTC in #openstack-operators. Notes from previous meeting can be found here [0]. Please go in prior to the meeting and vote for for the naming conventions suggested, which you believe are the most important or if you think some of them should not be considered at all. Hope to chat with you tomorrow! [0] https://etherpad.opendev.org/p/publiccloud-sig-meeting BR, Tobias Rydberg

1 0

[ptl][tc][election][adjutant][barbican][OpenStackSDK][OpenStack_Charms][sahara][swift][venus] Leaderless project for 2023.1 cycle
by Ghanshyam Mann 13 Sep '22

13 Sep '22

Hello, As you know, 2023.1 cycle election nomination is ended and we end up with 11 leaderless projects. List is in the etherpad: https://etherpad.opendev.org/p/2023.1-leaderless Out of 11, we have found 4 projects leaders but 7 (in the subject list) projects still need some leaders to volunteer: 1. Adjutant 2. Barbican 3. OpenStackSDK 3. OpenStack_Charms 4. Sahara 5. Swift 6. Venus Please reply here or ping us in #openstack-tc channel if you would like to lead these projects. -gmann

2 4

[cinder][stable] cinder-stable-core additions
by Rajat Dhasmana 13 Sep '22

13 Sep '22

Hi All, After discussing with the current members of the cinder stable core team, I've decided to add the following members to the cinder stable core team. 1) Walter Boring - (Currently cinder core) 2) Sofia Enriquez - (Currently cinder core) Sofia and Walt have been long term contributors in the Cinder project and I'm happy to have them as part of the stable core team. I will proceed with making changes to the stable core team[1]. [1] https://review.opendev.org/admin/groups/1b3ca2faf07b15efff426901a387eb7c914… Thanks and Regards Rajat Dhasmana

1 0

[all][elections][ptl][tc] Conbined PTL/TC antelope cycle Election Voting Kickoff
by Ian Y. Choi 13 Sep '22

13 Sep '22

Polls for PTL and TC elections are now open and will remain open for you to cast your vote until Sep 19, 2022 23:45 UTC. We are selecting 4 TC members, and are having PTL elections for Ironic. Please rank all candidates in your order of preference. You are eligible to vote in the TC election if you are a Foundation individual member[0] that also has committed to any official project team's deliverable repositories[1] over the Sep 17, 2021 00:00 UTC - Sep 07, 2022 00:00 UTC timeframe (Yoga to Zed) or if you are in the list of extra-atcs[2] for any official project team. You are eligible to vote in a PTL election if you are a Foundation individual member[0] and had a commit in one of that team's deliverable repositories[1] over the Sep 17, 2021 00:00 UTC - Sep 07, 2022 00:00 UTC timeframe (Yoga to Zed) or if you are in that team's list of extra-atcs[2]. If you are eligible to vote in an election, you should find your email with a link to the Condorcet page to cast your vote in the inbox of your Gerrit preferred email[3]. What to do if you don't see the email and have a commit in at least one of the projects having an election: * check the trash or spam folders of your gerrit Preferred Email address, in case it went into trash or spam * wait a bit and check again, in case your email server is a bit slow * find the sha of at least one commit from the project's deliverable repos[0] and email the election officials [4] * requires opt-in to CIVS polling to receive email communications from the voting system [5]. If we can confirm that you are entitled to vote, we will add you to the voters list for the appropriate election. Our democratic process is important to the health of OpenStack, please exercise your right to vote! Candidate statements/platforms can be found linked to Candidate names on this page: https://governance.openstack.org/election/ Happy voting, /Ian, as one of OpenStack Election Officials [0] https://www.openstack.org/community/members/ [1] The list of the repositories eligible for electoral status: https://opendev.org/openstack/governance/src/tag/oct-2022-elections/referen… [2] Look for the extra-atcs element in [1] [3] Sign into review.openstack.org: Go to Settings > Contact Information. Look at the email listed as your preferred email. That is where the ballot has been sent. [4] https://governance.openstack.org/election/#election-officials [5] https://lists.openstack.org/pipermail/openstack-discuss/2022-September/0304…

1 0

[baremetal-sig][ironic] Future of baremetal-sig
by Jay Faulkner 13 Sep '22

13 Sep '22

Stackers, An item came up in the Ironic meeting today regarding the future of the baremetal sig. Essentially, Arne was doing great work sourcing talks for it, but now he's going to be unable to continue hosting it and proactively sourcing talks. (A seriously big thanks is owed to Arne for doing a great job on this!) This led us to wonder if BM SIG in its current form remains sustainable. Some options we can consider include: - Keep the BM SIG as-is, cancel it months where there's not a talk available. - Change the BM SIG meetings to more of a meetup style for operators to talk about Ironic - Something else entirely we haven't thought about yet. What do you all think? - Jay Faulkner

1 0

OpenInfra Summit Vancouver 2023 Track Chair Nominations Now Open
by Helena Spease 12 Sep '22

12 Sep '22

Hey everyone! Track Chair nominations <https://openinfrafoundation.formstack.com/forms/trackchairnominations2023 <https://openinfrafoundation.formstack.com/forms/trackchairnominations2023>> for the 2023 OpenInfra Summit in Vancouver (June 13-15, 2023) are now open! Track Chairs for each Track will help build the Summit schedule, and are made up of individuals working in open infrastructure. Responsibilities include: Help the Summit team put together the best possible content based on your subject matter expertise Promote the individual Tracks within your networks Review the submissions and Community voting results in your particular Track Determine if there are any major content gaps in your Track, and if so, potentially solicit additional speakers directly to submit Ensure diversity of speakers and companies represented in your Track Avoid vendor sales pitches, focusing more on real-world user stories and technical, in-the-trenches experiences Identify which submissions would make good content for OpenInfra Live, the virtual show hosted by the OpenInfra Foundation that encourages live questions from a global audience 2023 Summit Tracks: 5G/NFV & Edge AI/Machine Learning/HPC CI/CD Container Infrastructure Getting Started Hardware Enablement Open Development Private & Hybrid Cloud Public Cloud Security Hands On Workshops Full track descriptions are available here <https://openinfra.dev/summit/vancouver-2023/summit-tracks/ <https://openinfra.dev/summit/vancouver-2023/summit-tracks/>>. If you’re interested in nominating yourself or someone else to be a member of the Summit Track Chairs for a specific Track, please fill out the nomination form <https://openinfrafoundation.formstack.com/forms/trackchairnominations2023 <https://openinfrafoundation.formstack.com/forms/trackchairnominations2023>>. Nominations will close on October 28th, 2022. Track Chairs selections will occur before we close the Call for Presentations (CFP) so that the Chairs can host office hours to consult on submissions, and help promote the event. CFP will be opening in November, registration <https://openinfrasummit2023.eventbrite.com/ <https://openinfrasummit2023.eventbrite.com/>> and sponsorship <http://openinfra.dev/summit/vancouver-2023/summit-sponsor/ <http://openinfra.dev/summit/vancouver-2023/summit-sponsor/>> information are already available. Please email speakersupport(a)openinfra.dev <mailto:speakersupport@openinfra.dev> with any questions or feedback. Cheers, Helena Spease

1 0

[all][tc] Technical Committee next weekly meeting on 2022 Sept 15 at 1500 UTC
by Ghanshyam Mann 12 Sep '22

12 Sep '22

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

1 0

[tc][ptl][election][masakari] I volunteer to become Masakari PTL again
by Radosław Piliszek 12 Sep '22

12 Sep '22

As in the topic - I saw Masakari did not receive a candidate and I don't want to see this project disappear so I volunteer to be the PTL. I don't have any major plans regarding Masakari except for keeping it afloat and working where it works already. Cheers, Radek -yoctozepto

2 1

[horizon][QA][release] Cycle With Intermediary without recent deliverables
by Előd Illés 12 Sep '22

12 Sep '22

Hi, Quick reminder that for deliverables following the cycle-with-intermediary model, the release team will use the latest Zed release available on release week. The following deliverables have done a Zed release, but it was not refreshed in the last two months: horizon tempest 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

3 2

[neutron] [ovn] Distributed routing ingress traffic flow
by Roman Pomazanov 12 Sep '22

12 Sep '22

1 0

[monasca][kolla-ansible] Help for a monasca newbie to get metrics for instances needed
by Christian Stelter 12 Sep '22

12 Sep '22

Hi! I'm trying to explore monasca, but I'm bit lost in how to get metrics from a project/tenant collected. I'm using kolla-ansible in my test setup running ubuntu-source images. Ubuntu release is Yoga. Monasca seems to be up and running. I can see the default metrics with a appropriate user in the monasca_control_plane project. cpu.* disk.* io.* load.* mem.* monasca.* net.* ntp.* And I find measurements in the influxdb, but only metrics/measurements for the openstack hypervisor nodes yet. What I'm missing after searching the existing documentation is how I can enable a plugin as for libvirt for example or whatever the recommendation for monitoring the instances is. As I have found the plugins directory on the hypervisors under /etc/kolla/monasca-agent-collector/plugins I thought putting a config file like in the documentation [1] for the libvirt plugin and restart the monasca-agent-collector would be sufficient. But all I got was an error message: 2022-09-11 12:22:26,412 | ERROR | collector | monasca_agent.common.util(util.py:529) | Unable to import check module libvirt.py from checks_d Traceback (most recent call last): File "/var/lib/kolla/venv/lib/python3.8/site-packages/monasca_agent/common/util.py", line 520, in load_check_directory check_module = load_module('checksd_%s' % check_name, check) File "/var/lib/kolla/venv/lib/python3.8/site-packages/monasca_agent/common/util.py", line 470, in load_module module_spec.loader.exec_module(module) File "<frozen importlib._bootstrap_external>", line 848, in exec_module File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed File "/var/lib/kolla/venv/lib/python3.8/site-packages/monasca_agent/common/../collector/checks_d/libvirt.py", line 20, in <module> import libvirt ModuleNotFoundError: No module named 'libvirt' As it seems the plugin system dependencies like libvirt-dev are missing. So I assume I have to rebuild the container myself and/or open an issue on opendev.org. Or is there another way to get metrics for instances? Next question: even if I had a running libvirt plugin. What has to be done to enable another user in a normal tenant project to use these metrics? Just add the monasca-read-only-user to user(s) which shall be enabled to manage alarm definitions, alarms and notifications? Will the tenant then see or at least use the metrics for his (and only his) project? I found a lot of high level documentation, (base) installation instructions, hints for developers on how to extend monasca, but nothing beyond the initial setup for monasca newbies like me. I queried the all-knowing, all-seeing trash heap, mailing lists, and the YT academy already. May be I just missed something. So hints are welcome! BTW. Is the kolla-ansible part of monasca still in active maintenance and development? I stumpled upon the same error as in [2] and I'm getting an HTTP 500 error when trying to open the monitoring overview and is still unassigned. Thanks in advance! Kind regards, Christian Stelter [1] https://github.com/openstack/monasca-agent/blob/master/docs/Libvirt.md#conf… [2] https://bugs.launchpad.net/kolla-ansible/+bug/1967278

2 2

[First Contact][SIG][PTG] Planning October 2022
by Kendall Nelson 12 Sep '22

12 Sep '22

Hello Party People, I started putting together the etherpad[1] for planning our time at the PTG! Add your topics and your name if you plan on attending :) If the time I selected doesn't work for folks, we can book other time (instead or in addition to), I just know historically we have been a mix of Americas/ APAC and so this time block should work for folks. Also, gentle reminder to register if you haven't already - it is free afterall [2]. -Kendall Nelson (diablo_rojo) [1] https://etherpad.opendev.org/p/oct2022-ptg-first-contact [2] https://openinfra-ptg.eventbrite.com/

1 0

[all] GovStack community seeking for infrastructure expertise
by Lueck, Nico GIZ 11 Sep '22

11 Sep '22

Do you believe in the potential of digital public goods for positive impact? Ever wished for more digitally-enabled government services? GovStack [1] is a community-driven initiative on a mission to accelerate the digital transformation of government services in order to better serve citizens - and we want you to join us! We create and maintain an openly licenced blueprint for a modular architecture based on reusable building blocks [2]. Our various working groups work to define the (non-)functional and API specifications for building blocks, leveraging existing standards such as OpenStack. These specifications are then used for implementations in our partner countries across the world, to facilitate the delivery of foundational, life-enhancing services. Learn more about the call for contributions here [3]. We are specifically looking for experts with experience in infrastructure and security. The initiative is founded by the German Federal Ministry for Economic Cooperation and Development, Deutsche Gesellschaft fuer Internationale Zusammenarbeit (GIZ), the Ministry of Foreign Affairs of the Republic of Estonia, the International Telecommunication Union (ITU) and the Digital Impact Alliance. Thank you to the team of the Open Infrastructure Foundation for their support. Also, thank you to the whole community and please feel free to directly contact us. Nico (Lueck) <nico.lueck(a)giz.de> [1] https://www.govstack.global/ [2] https://govstack.gitbook.io/ [3] https://www.govstack.global/call-for-expression-of-interest/ ________________________________ Deutsche Gesellschaft fuer Internationale Zusammenarbeit (GIZ) GmbH; Sitz der Gesellschaft Bonn und Eschborn/Registered offices Bonn and Eschborn, Germany; Registergericht/Registered at Amtsgericht Bonn, Germany; Eintragungs-Nr./Registration no. HRB 18384 und/and Amtsgericht Frankfurt am Main, Germany; Eintragungs-Nr./Registration no. HRB 12394; USt-IdNr./VAT ID no. DE 113891176; Vorsitzender des Aufsichtsrats/Chairman of the Supervisory Board: Jochen Flasbarth; Vorstand/Management Board: Tanja Goenner (Vorstandssprecherin/Chair of the Management Board), Ingrid-Gabriela Hoven, Thorsten Schaefer-Guembel

3 2

[designate] zone sharing between projects and how to create classless PTR
by Tomáš Bredár 10 Sep '22

10 Sep '22

Hi Folks, I have a few questions: 1. Is there a possibility to share DNS zones between tenants? I've found this [1] patchset, but it's not merged yet. 2. Is there a way to create a classless reverse zone? According to [2], it should work. Creating a zone is ok: openstack zone create --email tomas.bredar(a)gmail.com \ --ttl 3600 --description "in-addr.arpa. zone for reverse lookups for e-devel subnet 10.254.226.0/26" \ 0-26.226.254.10.in-addr.arpa. But when I try to add a recordset, I get an error: openstack recordset create --record testvm.bredytest.abc.com. --type PTR --ttl 600 0-26.226.254.10.in-addr.arpa. 1.226.254.10.in-addr.arpa. RecordSet is not contained within it's parent zone I'm using OpenStack Wallaby If this won't work, I'm considering using the neutron integration with external DNS. Thanks for your help Tomas [1] https://review.opendev.org/c/openstack/designate/+/726334 [2] https://docs.openstack.org/designate/latest/user/manage-ptr-records.html

3 4

[manila] Bugsquash postponed by one week
by Carlos Silva 10 Sep '22

10 Sep '22

Hello, Zorillas! I'm sending this email to inform you that the bugsquash we planned for this week will be postponed by one week. We currently have some FFEs and we could use the change owners and reviewers energy to get those changes moving forward. We hope to have the FFE changes merged by the end of this week, so next week we could use some focus time on the bugsquash. Regards, carloss

1 1

[release] Release countdown for week R-3, Sep 12 - 16
by Előd Illés 09 Sep '22

09 Sep '22

Development Focus ----------------- The Release Candidate (RC) deadline is next Thursday, September 15th, 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/zed branch will be cut. This branch will track the Zed release. Once stable/zed has been created, the master branch will be ready to switch to 2023.1 Antelope development. While the master branch will no longer be feature-frozen, please prioritize any work necessary for completing Zed plans. Release-critical bugfixes will need to be merged in the master branch first, then backported to the stable/zed 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/zed 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 2023.1 Antelope) 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 Zed release so far. Finally, now is a good time to finalize release highlights. Release highlights help shape the messaging around the release and make sure that your work is properly represented. Upcoming Deadlines & Dates -------------------------- RC1 deadline: September 15th, 2022 (R-3 week) Final RC deadline: September 29th, 2022 (R-1 week) Final Zed release: October 5th, 2022 Virtual PTG: October 17-21, 2022 Előd Illés irc: elodilles

1 0

[all][tc] What's happening in Technical Committee: summary 2022 Sept 9
by Slawek Kaplonski 09 Sep '22

09 Sep '22

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * We had this week's meeting on Sept 08. Most of the meeting discussions are summarized in this email. Meeting logs are available @https://meetings.opendev.org/meetings/tc/2022/tc.2022-09-08-15.00.log.html * Next TC weekly meeting will be on Sept 15 Thursday at 15:00 UTC, feel free to add the topic on the agenda[1] by Sept 14. 2. Activities In progress: ================== TC Tracker for Zed cycle ------------------------------ * Zed tracker etherpad includes the TC working items[2], four are completed and others items are in-progress. Open Reviews ----------------- * Five open reviews for ongoing activities[3]. 2023.1 cycle Technical Election (TC + PTL) ------------------------------------------------------------- Nomination period is now over. We are currently in the campaign time. Please remember that there is an action required if You want to receive ballot from CIVS. Please check [4] for more details. Define 2023.1 cycle testing runtime ------------------------------------------- Testing runtime for the 2023.1 cycle is up for review [5]. 2023.1 cycle TC PTG planning ------------------------------------ Updates on PTG planning: * "TC + Leader interaction" sessions is scheduled for Oct 17 Monday 15-17 UTC[6], * gmann created the TC PTG etherpad to collect the topic[7]. * gmann sent an email about the 'Operator Hours' slots in this PTG, please check and reserve the operator hour slot for your project[8]. 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. Fixing Zuul config error ---------------------------- Requesting projects with zuul config error to look into those and fix them which should not take much time[10][11]. Project updates ------------------- * Switch release management to distributed leadership[12] 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[13]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15 UTC [14] 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://lists.openstack.org/pipermail/openstack-discuss/2022-September/0304… [5] https://review.opendev.org/c/openstack/governance/+/854375 [6] https://lists.openstack.org/pipermail/openstack-discuss/2022-September/0303… [7] https://etherpad.opendev.org/p/tc-2023-1-ptg [8] https://lists.openstack.org/pipermail/openstack-discuss/2022-September/0303… [9] https://review.opendev.org/c/openstack/governance/+/836888 [10] https://etherpad.opendev.org/p/zuul-config-error-openstack [11] http://lists.openstack.org/pipermail/openstack-discuss/2022-May/028603.html [12] https://review.opendev.org/c/openstack/governance/+/855276 [13] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [14] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0

[neutron] Drivers meeting agenda - 9.09.2022.
by Lajos Katona 09 Sep '22

09 Sep '22

Hi Neutron Drivers, The agenda for tomorrow's drivers meeting is at [1]. We have the following RFE to discuss: [RFE] OVN support for vnic type virtio-forwarder (#link https://bugs.launchpad.net/neutron/+bug/1988542 ) [1] https://wiki.openstack.org/wiki/Meetings/NeutronDrivers#Agenda See you at the meeting tomorrow. Lajos Katona (lajoskatona)

1 0

[rabbitmq][kolla-ansible] How to enable rabbitmq plugin via configuration file?
by A Tom 09 Sep '22

09 Sep '22

Hi, I’m trying to enable rabbitmq_tracing plugin in my kolla-ansible. In „typical” installation you have to enable plugin via rabbitmq-plugins enable and (in case of this particular plugin) add directory,username and password to rabbitmq.conf. These changes (adding username,password and directory) are obvious, but how do I enable particular plugin by kolla-ansible configuration file? Should I put something in globals.yaml? Best regards Adam Tomas

1 0

[baremetal-sig][ironic] No meeting in September
by Iury Gregory 08 Sep '22

08 Sep '22

Hello everyone, This email is just to let you know that we won't have any presentation/meeting for the Baremetal-sig this month. -- *Att[]'s* *Iury Gregory Melo Ferreira * *MSc in Computer Science at UFCG* *Ironic PTL * *Senior Software Engineer at Red Hat Brazil* *Social*: https://www.linkedin.com/in/iurygregory *E-mail: iurygregory(a)gmail.com <iurygregory(a)gmail.com>*

1 0

[all][elections][ptl][tc] Combined PTL/TC antelope cycle Election Nominations End
by Amy Marrich 08 Sep '22

08 Sep '22

Please note we are in the process of adding a standalone TC Campaigning period before opening the TC election for voting. This will allow the candidates to answer any questions and also people to opt-in to the CIVS system before we start the voting process. Pending a patch being added and merged we are looking at starting the voting early to mid next week. Thanks, Amy +++++++++++++++++++++++++++++++++++++++++++++++++++ The PTL and TC Nomination period is now over. The official candidate lists for PTLs [0] and TC seats [1] are available on the election website. -- PTL Election Details -- There are 11 projects without candidates, so according to this resolution[2], the TC will have to decide how the following projects will proceed: Adjutant, Barbican, Keystone, Masakari, OpenStackSDK, OpenStack_Charms, Sahara, Senlin, Swift, Venus, Zun -- TC Election Details -- There are 1 projects that will have elections: Ironic. Now begins the campaigning period where candidates and electorate may debate their statements. Polling will start Sep 07, 2022 23:45 UTC. Thank you, [0] https://governance.openstack.org/election/#antelope-ptl-candidates [1] https://governance.openstack.org/election/#antelope-tc-candidates [2] https://governance.openstack.org/resolutions/20141128-elections-process-for…

2 1