Jump to: navigation, search

Difference between revisions of "Meetings/InfraTeamMeeting"

(Agenda for next meeting: EMS discontinuing legacy/consumer hosting plans)
(Agenda for next meeting: Cleaning up the openstack.org DNS zone)
(45 intermediate revisions by 5 users not shown)
Line 10: Line 10:
  
 
* Announcements
 
* Announcements
** No meetings December 12, 26, and January 2.
+
** Clarkb out 5/17 and 5/20
  
 
* 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)
+
*** Meetpad is done. Just need to clean up old servers when we feel confident we won't rollback.
*** py36 tox unittesting broken -- proposal to drop https://review.opendev.org/c/openstack/diskimage-builder/+/901093
+
*** What is next?
*** unit testing has been kept this long to ensure in-chroot tools are python3.6 clean -- bionic only platform still supported
+
** AFS Mirror cleanups (clarkb 20240220)
*** one suggestion is to pause bionic builds - see comment in https://review.opendev.org/c/openstack/project-config/+/901692 and comments in PS1
+
*** Ubuntu Xenial cleanups are starting to show up under topic:drop-ubuntu-xenial
**** clarkb points out this is painful if cloud providers change, and dib _probably_ won't break the build anyway
+
*** Can followup with webserver log processing to determine which other mirrors may be dead.
*** 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.
+
** Building Ubuntu Noble Nodes (clarkb 20240416)
** Python container updates (tonyb 20230718)
+
*** Next step is to add Noble to our mirrors
*** https://review.opendev.org/q/(topic:bookworm-python3.11+OR+hashtag:bookworm)+status:open Next round of image rebuilds onto bookworm.
+
** Gerrit 3.9 Upgrade Planning (clarkb 20240423)
*** zuul-operator is the last hold out on python3.10. Working through failures in CI there.
+
*** Upgrade prep notes are going in https://etherpad.opendev.org/p/gerrit-upgrade-3.9
**** https://review.opendev.org/c/zuul/zuul-operator/+/881245 is the change we need to get landed.
+
*** https://www.gerritcodereview.com/3.9.html Release Notes
** Gitea 1.21.1 Upgrade (clarkb 20230926)
+
*** Downgrade is possible with an offline reindex using the old war.
*** https://review.opendev.org/c/opendev/system-config/+/902490 Configure Gerrit to use new SSH key
+
*** Things to think about:
*** 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.
+
**** Do we want to enable diff3 diffs on merge changes?
*** https://review.opendev.org/c/opendev/system-config/+/897679 Upgrade to Gitea 1.21.0
+
**** Change topic limit seems to only apply to open changes. Being over the limit doesn't seem to impact the upgrade process
** Updating Zuul's database server (clarkb 20231121)
+
**** https://gerrit-review.googlesource.com/c/gerrit/+/424404 Upstream change to have release war build target without webfonts
*** Currently this is an older mysql 5.7 trove instance
+
**** 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.
*** 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.
+
*** Server could stand to be upgraded as well but I think it is probably best to decouple these concerns.
*** Are there other services we should consider this for as well?
+
** Cleaning up the openstack.org DNS zone (fungi 20240514)
*** Research/Planning questions: https://etherpad.opendev.org/p/opendev-zuul-mysql-upgrade
+
*** Proposed for deletion: https://paste.opendev.org/show/bVHJchKcKBnlgTNRHLVK/
** 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 20240102)
 
*** We have until 2024-02-07 to upgrade to a business hosting plan (prepaying a year at 10x the current price) or move elsewhere.
 
  
 
* 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 52: 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/