Team meeting agenda for June 14, 2022

Clark Boylan cboylan at sapwetik.org
Mon Jun 13 23:41:33 UTC 2022


We will meet on June 14, 2022 at 19:00 UTC in #opendev-meeting with this agenda:

== Agenda for next meeting ==

* Announcements

* Actions from last meeting

* Specs Review

* Topics
** Improving OpenDev's CD throughput (clarkb 20220614)
*** 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
*** Running Zuul cluster upgrade playbook automatically.
** Container maintenance (clarkb 20220614)
*** https://etherpad.opendev.org/p/opendev-container-maintenance
*** Continue to update services with dedicated users.
*** Upgrading Zookeeper
*** Upgrading MariaDB
*** Eventually convert MariaDB container's from uid 999 to something that makes more sense on the system.
** Gerrit 3.5 upgrade planning (ianw 20220614)
*** https://etherpad.opendev.org/p/gerrit-upgrade-3.5
*** http://lists.opendev.org/pipermail/service-announce/2022-May/000039.html Scheduled for 20:00 UTC June 19, 2022
** Zuul changing default Ansible version to v5 soon (clarkb 20220614)
*** Now that Zuul supports Ansible v5 the next step is to default to v5
*** Need to send an announcement for the default change in OpenDev happening at the end of June.
** Enable webapp on nodepool launchers? (frickler 20220611)
*** Would help with checking for image freshness / builds failing
*** Also look into pushing stats into grafana?
** Run a custom URL shortener service (frickler 20220611)
*** Many people use bit.ly or similar in IRC channel topics and elsewhere
*** https://opensource.com/article/18/7/apache-url-shortener shows an easy solution that could be git-based
*** Should be easy to with some new DNS record on static.o.o
*** Data could be managed in a single file (maybe in project-config) or one file per URL

* Open discussion



More information about the service-discuss mailing list