Jump to: navigation, search

Difference between revisions of "Meetings/InfraTeamMeeting"

(couple of new topics added)
(→‎Agenda for next meeting)
(46 intermediate revisions by 4 users not shown)
Line 10: Line 10:
  
 
* Announcements
 
* Announcements
−
** No meetings December 12, 26, and January 2.
+
** OpenInfra Summit CFP ends May 29, 2024
  
 
* Actions from last meeting
 
* Actions from last meeting
Line 17: 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
−
*** Tonyb is adding new mirror servers.
+
*** https://etherpad.opendev.org/p/opendev-focal-server-upgrades
−
*** New mirror servers should be ready. Is it time to update CNAMEs and plan for old server cleanup?
+
*** Started looking at the wiki there are rough notes at: https://etherpad.opendev.org/p/opendev-bionic-server-upgrades#L58
−
** DIB bionic support (ianw 20231206)
+
*** Tonyb looking at cacti and the wiki as next items.
−
*** py36 tox unittesting broken -- proposal to drop https://review.opendev.org/c/openstack/diskimage-builder/+/901093
+
** AFS Mirror cleanups (clarkb 20240220)
−
*** unit testing has been kept this long to ensure in-chroot tools are python3.6 clean -- bionic only platform still supported
+
*** Ubuntu Xenial cleanups are starting to show up under topic:drop-ubuntu-xenial
−
*** one suggestion is to pause bionic builds - see comment in https://review.opendev.org/c/openstack/project-config/+/901692 and comments in PS1
+
*** Can followup with webserver log processing to determine which other mirrors may be dead.
−
**** clarkb points out this is painful if cloud providers change, and dib _probably_ won't break the build anyway
+
** Building Ubuntu Noble Nodes (clarkb 20240416)
−
*** second option is to drop tox 36 testing, but leave bionic test in dib-functests.  Probably enough coverage for basic support.  Should probably do a release first.
+
*** Mirrors for x86_64 and arm64 are in place. We should be able to add image builds to nodepool.
−
** Python container updates (tonyb 20230718)
+
** Gerrit 3.9 Upgrade Planning (clarkb 20240423)
−
*** https://review.opendev.org/q/(topic:bookworm-python3.11+OR+hashtag:bookworm)+status:open Next round of image rebuilds onto bookworm.
+
*** Upgrade prep notes are going in https://etherpad.opendev.org/p/gerrit-upgrade-3.9
−
*** zuul-operator is the last hold out on python3.10. Working through failures in CI there.
+
*** https://www.gerritcodereview.com/3.9.html Release Notes
−
**** https://review.opendev.org/c/zuul/zuul-operator/+/881245 is the change we need to get landed.
+
*** Planning to upgrade the Gerrit server on May 31, 2024 from 1600-1700 UTC
−
** Gitea 1.21.1 Upgrade (clarkb 20230926)
+
** Linaro Cloud SSL Cert Renewal (clarkb 20240521)
−
*** https://review.opendev.org/c/opendev/system-config/+/902490 Configure Gerrit to use new SSH key
+
*** It has been a couple of months and we need to renew the cert again. Should be documented now. Any volunteers?
−
*** After Gerrit is restarted and using the new key we can remove the old key from Gitea. At that point we should be ready to plan the Gitea upgrade.
+
 
−
*** https://review.opendev.org/c/opendev/system-config/+/897679 Upgrade to Gitea 1.21.0
 
−
** Updating Zuul's database server (clarkb 20231121)
 
−
*** Currently this is an older mysql 5.7 trove instance
 
−
*** 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.
 
−
*** Are there other services we should consider this for as well?
 
−
*** Research/Planning questions: https://etherpad.opendev.org/p/opendev-zuul-mysql-upgrade
 
−
** Annual Report Season (clarkb 20231128)
 
−
*** OpenDev's 2023 Annual Report Draft will live here: https://etherpad.opendev.org/p/2023-opendev-annual-report
 
−
** EMS discontinuing legacy/consumer hosting plans (fungi 20231219)
 
−
*** We have until 2024-02-07 to upgrade to a business hosting plan (prepaying a year at 10x the current price) or move elsewhere.
 
−
** Followup on 20231216 incident (frickler 20231217)
 
−
*** 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)
 
−
*** Use docker prune less aggressively for easier rollback?
 
−
**** 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?
 
−
*** Add timestamps to zuul_reboot.log?
 
−
**** https://opendev.org/opendev/system-config/src/branch/master/playbooks/service-bridge.yaml#L41-L55
 
−
**** Also this is running on Saturdays (weekday: 6), do we want to fix the comment or the dow?
 
−
*** 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?
 
−
** AFS quota issues (frickler 20231217)
 
−
*** 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
 
−
*** 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?
 
 
* Open discussion
 
* Open discussion
−
** (tonyb 20231128) [If time permits].  Could we enable via roles/jobs or with an additional nodepool driver.  The ability for [OpenStack] project teams to run unit tests with the python images we already build eg https://review.opendev.org/c/opendev/system-config/+/898756.
 
  
 
== Upcoming Project Renames ==
 
== Upcoming Project Renames ==
Line 66: Line 40:
 
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 16:11, 21 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
    • OpenInfra Summit CFP ends May 29, 2024
  • 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/

Retrieved from "https://wiki.openstack.org/w/index.php?title=Meetings/InfraTeamMeeting&oldid=184841"