Jump to: navigation, search

Difference between revisions of "Meetings/InfraTeamMeeting"

(Agenda for next meeting)
(Agenda for next meeting: Cleaning up the openstack.org DNS zone)
(41 intermediate revisions by 4 users not shown)
Line 10: Line 10:
  
 
* Announcements
 
* Announcements
** OpenInfra Foundation Individual Board member election is happening now. Look for your ballot via email and vote.
+
** Clarkb out 5/17 and 5/20
** OpenInfra Live will feature OpenDev January 18, 2023.
 
  
 
* Actions from last meeting
 
* Actions from last meeting
Line 18: Line 17:
  
 
* Topics
 
* Topics
** Upgrading Bionic servers to Focal/Jammy (clarkb 20230627)
+
** Upgrading Old Servers (clarkb 20230627)
 
*** https://etherpad.opendev.org/p/opendev-bionic-server-upgrades
 
*** https://etherpad.opendev.org/p/opendev-bionic-server-upgrades
** Python container updates (tonyb 20230718)
+
*** https://etherpad.opendev.org/p/opendev-focal-server-upgrades
*** https://review.opendev.org/c/opendev/system-config/+/905018 Drop Bullseye python3.11 images
+
*** Started looking at the wiki there are rough notes at: https://etherpad.opendev.org/p/opendev-bionic-server-upgrades#L58
*** zuul-operator is the last hold out now
+
*** Meetpad is done. Just need to clean up old servers when we feel confident we won't rollback.
**** https://review.opendev.org/c/zuul/zuul-operator/+/881245 is the change we need to get landed.
+
*** What is next?
** Updating Zuul's database server (clarkb 20231121)
+
** AFS Mirror cleanups (clarkb 20240220)
*** Currently this is an older mysql 5.7 trove instance
+
*** Ubuntu Xenial cleanups are starting to show up under topic:drop-ubuntu-xenial
*** We can move it to a self hosted instance (maybe on a dedicated host?) running out of docker like many of our other services and get it more up to date.
+
*** Can followup with webserver log processing to determine which other mirrors may be dead.
*** Are there other services we should consider this for as well?
+
** Building Ubuntu Noble Nodes (clarkb 20240416)
*** Research/Planning questions: https://etherpad.opendev.org/p/opendev-zuul-mysql-upgrade
+
*** Next step is to add Noble to our mirrors
** EMS discontinuing legacy/consumer hosting plans (fungi 20231219)
+
** Gerrit 3.9 Upgrade Planning (clarkb 20240423)
*** We have until 2024-02-07 to upgrade to a business hosting plan (prepaying a year at 10x the current price) or move elsewhere.
+
*** Upgrade prep notes are going in https://etherpad.opendev.org/p/gerrit-upgrade-3.9
** Followup on 20231216 incident (frickler 20231217)
+
*** https://www.gerritcodereview.com/3.9.html Release Notes
*** Do we want to pin external images like haproxy and only bump them after testing? (Not sure that would've helped for the current issue though)
+
*** Downgrade is possible with an offline reindex using the old war.
*** Use docker prune less aggressively for easier rollback?
+
*** Things to think about:
**** We do so for some services, like https://opendev.org/opendev/system-config/src/branch/master/playbooks/roles/gitea/tasks/main.yaml#L71-L76, might want to duplicate for all containers? Bump the hold time to 7d?
+
**** Do we want to enable diff3 diffs on merge changes?
*** Add timestamps to zuul_reboot.log?
+
**** Change topic limit seems to only apply to open changes. Being over the limit doesn't seem to impact the upgrade process
**** https://opendev.org/opendev/system-config/src/branch/master/playbooks/service-bridge.yaml#L41-L55
+
**** https://gerrit-review.googlesource.com/c/gerrit/+/424404 Upstream change to have release war build target without webfonts
**** Also this is running on Saturdays (weekday: 6), do we want to fix the comment or the dow?
+
**** There is a new batched ref updated event that collects multiple ref updated events in a single event. This is disabled by default, but could one day impact zuul. Work sorting out likely.
*** Do we want to document or implement a procedure for rolling back zuul upgrades? Or do we assume that issues can always be fixed in a forward going way?
+
*** Server could stand to be upgraded as well but I think it is probably best to decouple these concerns.
** AFS quota issues (frickler 20231217)
+
** Cleaning up the openstack.org DNS zone (fungi 20240514)
*** mirror.openeuler has reached its quota limit and the mirror job seems to be failing since two weeks. I'm also a bit worried that they seem do have doubled their volume over the last 12 months
+
*** Proposed for deletion: https://paste.opendev.org/show/bVHJchKcKBnlgTNRHLVK/
*** ubuntu mirrors are also getting close, but we might have another couple of months time there
 
*** mirror.centos-stream seems to have a steep increase in the last two months and might also run into quota limits soon
 
*** project.zuul with the latest releases is getting close to its tight limit of 1GB (sic), I suggest to simply double that
 
** Broken wheel build issues (frickler 20231217)
 
*** wheel builds for centos >=8 seem broken, with nobody maintaining these it might be better to drop them?
 
** Gitea repo-archives filling server disk (clarkb 20240109)
 
*** https://review.opendev.org/c/opendev/system-config/+/904868 update robots.txt on upstream's suggestion
 
*** https://review.opendev.org/c/opendev/system-config/+/904874 Run weekly removal of all cached repo archives
 
** OpenDev Service Coordinator Election happening soon  (clarkb 20240109)
 
  
 
* Open discussion
 
* Open discussion
Line 57: Line 47:
 
Changes should have their topic set to project-rename.
 
Changes should have their topic set to project-rename.
  
* Rename foo/example -> bar/example: https://review.opendev.org/123456
+
* Rename example/foo -> example/bar: https://review.opendev.org/c/openstack/project-config/+/123456
  
 
== Previous meetings ==
 
== Previous meetings ==
 
Previous meetings, with their notes and logs, can be found at http://eavesdrop.openstack.org/meetings/infra/ and earlier at http://eavesdrop.openstack.org/meetings/ci/
 
Previous meetings, with their notes and logs, can be found at http://eavesdrop.openstack.org/meetings/infra/ and earlier at http://eavesdrop.openstack.org/meetings/ci/

Revision as of 18:00, 13 May 2024

Weekly Project Infrastructure team meeting

The OpenDev Team holds public weekly meetings in #opendev-meeting on OFTC, Tuesdays at 1900 UTC. Everyone interested in infrastructure and process surrounding automated testing and deployment is encouraged to attend.

Please feel free to add agenda items (and your IRC nick in parenthesis).

Agenda for next meeting

  • Announcements
    • Clarkb out 5/17 and 5/20
  • Actions from last meeting
  • Specs Review
  • Open discussion

Upcoming Project Renames

(any additions should mention original->new full names and link to the corresponding project-config rename change in Gerrit) Changes should have their topic set to project-rename.

Previous meetings

Previous meetings, with their notes and logs, can be found at http://eavesdrop.openstack.org/meetings/infra/ and earlier at http://eavesdrop.openstack.org/meetings/ci/