We will meet with this agenda on June 11, 2024 at 19:00 UTC in #opendev-meeting: == Agenda for next meeting == * Announcements ** clarkb out June 14-19. Will miss the June 18 meeting if we have one. * Actions from last meeting * Specs Review * Topics ** Upgrading Old Servers (clarkb 20230627) *** https://etherpad.opendev.org/p/opendev-bionic-server-upgrades **** wiki.openstack.org: https://etherpad.opendev.org/p/opendev-mediawiki-upgrade **** tonyb looking at cacti after wiki *** https://etherpad.opendev.org/p/opendev-focal-server-upgrades **** tonyb expects to try a simple focal -> noble upgrade this week ** AFS Mirror cleanups (clarkb 20240220) *** Ubuntu Xenial cleanups are starting to show up under topic:drop-ubuntu-xenial *** Can followup with webserver log processing to determine which other mirrors may be dead. ** Gitea 1.22 Upgrade Planning (clarkb 20240528) *** There is a Gitea 1.22.0 release now. Once we have the general upgrade working we can test the doctor tool to fixup the DB case sensitivity. *** https://review.opendev.org/c/opendev/system-config/+/920580 ** Fixing Cloud Launcher Ansible (clarkb 20240604) *** Git updates broke our cloud launcher playbook even after Frickler addressed security group redundancy errors *** https://review.opendev.org/c/opendev/system-config/+/921685 workaround the Git issue *** We should know on the day of the meeting if this is working again. ** Improving mailman email throughput (clarkb 20240604) *** We've noticed slowness delivering emails for openstack-discuss *** Increasing the number of out runners hasn't alleviated this issue (it should prevent openstack-discuss from holding up other lists though) *** Next we need to modify the mailman email batch count and exim verp queue sizes. ** OpenMetal Cloud Rebuild (clarkb 20240604) *** The old cloud is gone and the new cloud is getting configured. *** https://etherpad.opendev.org/p/openmetal-cloud-bootstrapping captures our todo list for bootstrapping the new cloud ** Testing Rackspace's New Cloud Offering (clarkb 20240604) *** Rax reached out via a ticket to our nodepool account indicating we can test out their new offering. They are specifically looking for feedback *** Probably need to reach out to rax and find out a bit more information before determining if we are the target audience, but if so this is a good opportunity for more test nodes and improved clouds. * Open discussion