September 2022 - openstack-discuss

[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 10 Sep '22

10 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 09 Sep '22

09 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