Jump to: navigation, search

Difference between revisions of "Meetings/InfraTeamMeeting"

(Agenda for next meeting)
(Agenda for next meeting)
(45 intermediate revisions by 5 users not shown)
Line 18: Line 18:
 
** Upgrading Bionic servers to Focal/Jammy (clarkb 20230627)
 
** Upgrading Bionic servers to Focal/Jammy (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://review.opendev.org/q/topic:jitsi_meet-jammy-update
*** 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)
+
** MariaDB Upgrades (clarkb 20240220)
*** py36 tox unittesting broken -- proposal to drop https://review.opendev.org/c/openstack/diskimage-builder/+/901093
+
*** Relying on the container image MARIADB_AUTO_UPGRADE flag
*** unit testing has been kept this long to ensure in-chroot tools are python3.6 clean -- bionic only platform still supported
+
*** Everything but Gerrit is done now. When do we think we want to do Gerrit?
*** one suggestion is to pause bionic builds - see comment in https://review.opendev.org/c/openstack/project-config/+/901692 and comments in PS1
+
** AFS Mirror cleanups (clarkb 20240220)
**** clarkb points out this is painful if cloud providers change, and dib _probably_ won't break the build anyway
+
*** Ubuntu Xenial cleanups are starting to show up under topic:drop-ubuntu-xenial
*** 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.
+
*** Do we want to prefer removing projects from zuul's tenant config or propose changes to projects to cleanup Xenial usage then if/when they break we did our best?
** Python container updates (tonyb 20230718)
+
*** Can followup with webserver log processing to determine which other mirrors may be dead.
*** https://review.opendev.org/q/(topic:bookworm-python3.11+OR+hashtag:bookworm)+status:open Next round of image rebuilds onto bookworm.
+
** Building Ubuntu Noble Nodes (clarkb 20240416)
*** zuul-operator is the last hold out on python3.10. Working through failures in CI there.
+
*** Changes needed in opendev nodepool elements and glean have all merged and DIB is testing Noble builds now
**** https://review.opendev.org/c/zuul/zuul-operator/+/881245 is the change we need to get landed.
+
*** Next step is to add Noble to our mirrors (do we have room within the existing Ubuntu Volume? Is that Volume still small enough for OpenAFS) then we can add image builds to Nodepool.
** Gitea 1.21.1 Upgrade (clarkb 20230926)
+
** Etherpad 2.0.3 Upgrade planning (clarkb 20240416)
*** https://review.opendev.org/c/opendev/system-config/+/902490 Configure Gerrit to use new SSH key
+
*** https://review.opendev.org/c/opendev/system-config/+/914119
*** 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.
+
*** Etherpad 2.0.2 removes the old APIKEY API auth method and now uses Oauth2.0 client_credentials instead. The above change updates docs and testing to accommodate this change.
*** https://review.opendev.org/c/opendev/system-config/+/897679 Upgrade to Gitea 1.21.0
+
** Gerrit 3.9 Upgrade Planning (clarkb 20240423)
** Updating Zuul's database server (clarkb 20231121)
+
*** Upgrade prep notes are going in https://etherpad.opendev.org/p/gerrit-upgrade-3.9
*** Currently this is an older mysql 5.7 trove instance
+
*** https://www.gerritcodereview.com/3.9.html Release Notes
*** 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.
+
*** Downgrade is possible with an offline reindex using the old war.
*** Are there other services we should consider this for as well?
+
*** Things to think about:
*** Research/Planning questions: https://etherpad.opendev.org/p/opendev-zuul-mysql-upgrade
+
**** Do we want to enable diff3 diffs on merge changes?
** Annual Report Season (clarkb 20231128)
+
**** Do we think 5000 changes per topic is too few? If so we need to update a new config option to set a larger value than the default.
*** OpenDev's 2023 Annual Report Draft will live here: https://etherpad.opendev.org/p/2023-opendev-annual-report
+
**** We can build the docs without external fonts, but the release target doesn't do this for us. I've asked how we might do that without forking the bazel configs.
** Mailing lists: Gmail has become more demanding (fungi 20231205)
+
**** 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.
*** https://review.opendev.org/q/topic:%22argh-gmail%22 Add an SPF record for the listserv
+
*** Server could stand to be upgraded as well but I think it is probably best to decouple these concerns.
 +
** Wiki SSL Cert Renewal (clarkb 20240423)
 +
*** We have just under 4 weeks to renew the cert. This is one of the last (maybe the only) manually managed ssl cert.
 +
*** Will probably delay until we have less than a week left before processing it.
  
 
* 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 51: Line 53:
 
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 21:26, 29 April 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
  • Actions from last meeting
  • Specs Review
  • Topics
    • Upgrading Bionic servers to Focal/Jammy (clarkb 20230627)
    • MariaDB Upgrades (clarkb 20240220)
      • Relying on the container image MARIADB_AUTO_UPGRADE flag
      • Everything but Gerrit is done now. When do we think we want to do Gerrit?
    • AFS Mirror cleanups (clarkb 20240220)
      • Ubuntu Xenial cleanups are starting to show up under topic:drop-ubuntu-xenial
      • Do we want to prefer removing projects from zuul's tenant config or propose changes to projects to cleanup Xenial usage then if/when they break we did our best?
      • Can followup with webserver log processing to determine which other mirrors may be dead.
    • Building Ubuntu Noble Nodes (clarkb 20240416)
      • Changes needed in opendev nodepool elements and glean have all merged and DIB is testing Noble builds now
      • Next step is to add Noble to our mirrors (do we have room within the existing Ubuntu Volume? Is that Volume still small enough for OpenAFS) then we can add image builds to Nodepool.
    • Etherpad 2.0.3 Upgrade planning (clarkb 20240416)
    • Gerrit 3.9 Upgrade Planning (clarkb 20240423)
      • Upgrade prep notes are going in https://etherpad.opendev.org/p/gerrit-upgrade-3.9
      • https://www.gerritcodereview.com/3.9.html Release Notes
      • Downgrade is possible with an offline reindex using the old war.
      • Things to think about:
        • Do we want to enable diff3 diffs on merge changes?
        • Do we think 5000 changes per topic is too few? If so we need to update a new config option to set a larger value than the default.
        • We can build the docs without external fonts, but the release target doesn't do this for us. I've asked how we might do that without forking the bazel configs.
        • 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.
      • Server could stand to be upgraded as well but I think it is probably best to decouple these concerns.
    • Wiki SSL Cert Renewal (clarkb 20240423)
      • We have just under 4 weeks to renew the cert. This is one of the last (maybe the only) manually managed ssl cert.
      • Will probably delay until we have less than a week left before processing it.
  • 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/