Team Meeting Agenda for April 26, 2022

[Clark Boylan]

Hello,

We will meet on April 26, 2022 at 19:00 UTC in #opendev with this agenda:

== Agenda for next meeting ==

* Announcements

* Actions from last meeting

* Specs Review

* Topics
** Improving OpenDev's CD throughput (clarkb 20220426)
*** Bootstrapping bridge via Zuul is now a complicated subject. Can use zuul secrets to make it happen. Are we comfortable with this?
*** https://review.opendev.org/c/opendev/infra-specs/+/821645 -- spec outlining some of the issues with secrets
*** https://review.opendev.org/c/opendev/system-config/+/821155 -- sample of secret writing; more info in changelog
** Container maintenance (clarkb 20220426)
*** https://etherpad.opendev.org/p/opendev-container-maintenance
*** Running containers with dedicated users.
**** Our zuul insecure-ci-registry has been updated.
*** Upgrading Zookeeper
*** Upgrading MariaDB
*** Eventually convert MariaDB container's from uid 999 to something that makes more sense on the system.
** Spring cleaning for old reviews? (frickler 20220426)
*** system-config has >300 open reviews, most of them in merge-conflict and >1y old
**** Some changes have been labeled with topic:system-config-cleanup and are worth landing: https://review.opendev.org/q/project:opendev/system-config+status:open+topic:system-config-cleanup
*** Please look at your changes and update/rebase as necessary and set topic:system-config-cleanup and we can try to get through this backlog. Or abandon unnecessary changes.
** Support for Ubuntu 22.04 LTS aka Jammy Jellyfish (frickler 20220425)
*** Repo mirrors https://review.opendev.org/c/opendev/system-config/+/838923
*** DIB testing https://review.opendev.org/c/openstack/diskimage-builder/+/836228
*** Actual build https://review.opendev.org/c/openstack/project-config/+/839057
*** Nodepool release with fixes?
*** Drop mirroring for Xenial in order to recover AFS quota?
**** We cleaned up a bunch of centos, epel, opensuse, open euler, fedora, etc mirrors to remove unnecessary content which made more than enough room for Jammy.
** Deleting the subunit2sql MySQL Trove instance (clarkb 20220426)
*** The subunit2sql workers and the health api service that sat in front of this database are gone now
*** Currently using 286GB of disk. Do we need to backup/snapshot this or can we simply delete it and move on.

* Open discussion