Jump to: navigation, search

Difference between revisions of "Meetings/InfraTeamMeeting"

(Agenda for next meeting)
(Agenda for next meeting)
(267 intermediate revisions by 13 users not shown)
Line 14: Line 14:
  
 
* Specs Review
 
* Specs Review
** Mailman 3 spec https://review.opendev.org/810990
 
  
 
* Topics
 
* Topics
** Improving OpenDev's CD throughput (clarkb 20211026)
+
** Upgrading Old Servers (clarkb 20230627)
*** We can run many of our jobs in parallel in all of our CD pipelines. But this requires we properly document/address dependencies
+
*** https://etherpad.opendev.org/p/opendev-bionic-server-upgrades
**** Need to understand our job dependencies and properly note them in Zuul config or address them by combining jobs.
+
*** https://etherpad.opendev.org/p/opendev-focal-server-upgrades
***** Example 1: Combine service-gitea-lb and service-gitea jobs.
+
*** https://review.opendev.org/q/topic:jitsi_meet-jammy-update
***** Example 2: Combine letsencrypt and nameserver jobs
+
*** Started looking at the wiki there are rough notes at: https://etherpad.opendev.org/p/opendev-bionic-server-upgrades#L58
***** Example 3: Have all jobs with webserver config express a dependency on the letsencrypt job
+
** MariaDB Upgrades (clarkb 20240220)
**** Suggest we document the known job dependencies in a human readable format, then encode this into zuul, then we can switch to parallel runs.
+
*** Relying on the container image MARIADB_AUTO_UPGRADE flag
**** https://review.opendev.org/c/opendev/system-config/+/807672
+
*** Everything but Gerrit is done now. When do we think we want to do Gerrit?
***** should list dependencies for all jobs
+
** AFS Mirror cleanups (clarkb 20240220)
***** zuul doesn't trigger on this?  not sure on best approach to make it mergable
+
*** Ubuntu Xenial cleanups are starting to show up under topic:drop-ubuntu-xenial
**** https://review.opendev.org/c/opendev/base-jobs/+/807807
+
*** Can followup with webserver log processing to determine which other mirrors may be dead.
***** currently every executor adds keys for bridge, then logs in and clones system-config before running playbooks
+
** Building Ubuntu Noble Nodes (clarkb 20240416)
***** this change makes split jobs to do this. however, production remains the same as both are called.
+
*** Next step is to add Noble to our mirrors
**** https://review.opendev.org/c/opendev/system-config/+/807808
+
** Gerrit 3.9 Upgrade Planning (clarkb 20240423)
***** this is a follow-on that adds a base job to clone system-config, and stops the other production jobs re-cloning.
+
*** Upgrade prep notes are going in https://etherpad.opendev.org/p/gerrit-upgrade-3.9
***** this job must run first, but then all other jobs can run in parallel, as they are all in the same buildset and using the same "view" of system-config for that particular run
+
*** https://www.gerritcodereview.com/3.9.html Release Notes
** Gerrit Account cleanups (clarkb 20211026)
+
*** https://review.opendev.org/c/opendev/system-config/+/918333 Need updated and promoted 3.9 image before doing more testing.
*** 33 conflicts remain. Clarkb has written notes on proposed plans for each user in the comments of review02:~clarkb/gerrit_user_cleanups/audit-results-annotated.yaml
+
*** Downgrade is possible with an offline reindex using the old war.
** Fedora 34 test node booting problems (clarkb 20211026)
+
*** Things to think about:
*** Changes to Fedora's kernel packaging broke Xen
+
**** Do we want to enable diff3 diffs on merge changes?
*** Not yet sure if that may have also somehow broken OVH and iweb.
+
**** Change topic limit seems to only apply to open changes. Being over the limit doesn't seem to impact the upgrade process
** Begin planning for Gerrit 3.4 upgrade (clarkb 20211026)
+
**** https://gerrit-review.googlesource.com/c/gerrit/+/424404 Upstream change to have release war build target without webfonts
*** Read through release notes and identify areas of concern.
+
**** 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://www.gerritcodereview.com/3.4.html
+
*** Server could stand to be upgraded as well but I think it is probably best to decouple these concerns.
*** Do we need to modify system-config-run-review-3.4 or system-config-upgrade-review jobs to test any specific behaviors?
+
** Wiki SSL Cert Renewal (clarkb 20240423)
*** Probably worth holding a 3.4 test node and doing a skim for any unexpected behaviors.
+
*** Clarkb will renew Friday ish (May 10)
  
 
* Open discussion
 
* Open discussion
Line 48: Line 47:
 
== Upcoming Project Renames ==
 
== Upcoming Project Renames ==
 
(any additions should mention original->new full names and link to the corresponding project-config rename change in Gerrit)
 
(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.
  
* 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:25, 6 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
  • 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/