We will meet with this agenda on March 25, 2025 at 19:00 UTC in #opendev-meeting: == Agenda for next meeting == * Announcements * Actions from last meeting * Specs Review * Topics ** Zuul-launcher image builds (corvus 20240910) *** All current x86_64 providers are enrolled in the launcher now. Those with smaller and bigger flavors are setup to provide those labels too. ** Container hygiene tasks (clarkb 20250318) *** https://review.opendev.org/q/topic:%22opendev-python3.12%22+status:open Update images to use python3.12 *** Rebuilding our base images then switching things over to those new base images seems like a good way to get updates. ** Dropping uWSGI (clarkb 20250318) *** frickler provided a workaround for building uwsgi containers (we dropped arm64 container builds since we don't use uwsgi on arm) *** clarkb would still like to switch lodgeit to granian but that is a lower priority now. ** Upgrading Old Servers (clarkb 20230627) *** https://etherpad.opendev.org/p/opendev-bionic-server-upgrades *** https://etherpad.opendev.org/p/opendev-focal-server-upgrades *** https://etherpad.opendev.org/p/opendev-server-replacement-sprint **** wiki.openstack.org: https://etherpad.opendev.org/p/opendev-mediawiki-upgrade **** tonyb looking at cacti after wiki *** clarkb replaced all nodepool builders and the osuosl mirror *** Currently working through updating the nodepool launchers *** Please grab a host or three and work on updating them if you can. This is an activity where we can't boil the ocean so every little bit of help is important. ** Running certcheck on bridge (clarkb 20250114) *** Suggestion is that we just run this as an infra-prod job instead as all state should be available there. ** Working through our TODO list (clarkb 20250107) *** https://etherpad.opendev.org/p/opendev-january-2025-meetup ** Upgrading to Gitea 1.23.6 (clarkb 20250325) *** New release of gitea is available. We should update *** https://review.opendev.org/c/opendev/system-config/+/945414 ** Rotating mailman 3 logs (clarkb 20250325) *** Some of the mailman3 log files have grown quite large and could stand some rotation *** Unfortunately fungi found evidence that the codebase may not handle rotation gracefully. *** Not sure if we want to just force the issue or try to fix it upstream or something else. * Open discussion