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

Topics
- Upgrading Old Servers (clarkb 20230627)
  - https://etherpad.opendev.org/p/opendev-bionic-server-upgrades
  - https://etherpad.opendev.org/p/opendev-focal-server-upgrades
  - Started looking at the wiki there are rough notes at: https://etherpad.opendev.org/p/opendev-bionic-server-upgrades#L58
  - Meetpad is done. Just need to clean up old servers when we feel confident we won't rollback.
  - What is next?
- AFS Mirror cleanups (clarkb 20240220)
  - Ubuntu Xenial cleanups are starting to show up under topic:drop-ubuntu-xenial
  - Can followup with webserver log processing to determine which other mirrors may be dead.
- Building Ubuntu Noble Nodes (clarkb 20240416)
  - Next step is to add Noble to our mirrors
- 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?
    - Change topic limit seems to only apply to open changes. Being over the limit doesn't seem to impact the upgrade process
    - https://gerrit-review.googlesource.com/c/gerrit/+/424404 Upstream change to have release war build target without webfonts
    - 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.
- Cleaning up the openstack.org DNS zone (fungi 20240514)
  - Proposed for deletion: https://paste.opendev.org/show/bVHJchKcKBnlgTNRHLVK/

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.

Rename example/foo -> example/bar: https://review.opendev.org/c/openstack/project-config/+/123456

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/

@@ Line 10: / Line 10: @@
 * Announcements
-** OpenInfra Summit CFP and programming committee need your input: https://openinfra.dev/summit/
+** Clarkb out 5/17 and 5/20
-** Service Coordinator nomination time has begun.
 * Actions from last meeting
@@ Line 18: / Line 17: @@
 * Topics
-** Improving OpenDev's CD throughput (clarkb 20220125)
+** Upgrading Old Servers (clarkb 20230627)
-*** Bootstrapping bridge via Zuul is now a complicated subject. Can use zuul secrets to make it happen. Are we comfortable with this?
+*** https://etherpad.opendev.org/p/opendev-bionic-server-upgrades
-*** https://review.opendev.org/c/opendev/infra-specs/+/821645 -- spec outlining some of the issues with secrets
+*** https://etherpad.opendev.org/p/opendev-focal-server-upgrades
-*** https://review.opendev.org/c/opendev/system-config/+/821155 -- sample of secret writing; more info in changelog
+*** Started looking at the wiki there are rough notes at: https://etherpad.opendev.org/p/opendev-bionic-server-upgrades#L58
-** Container maintenance (clarkb 20220125)
+*** Meetpad is done. Just need to clean up old servers when we feel confident we won't rollback.
-*** https://etherpad.opendev.org/p/opendev-container-maintenance
+*** What is next?
-*** Buster to Bullseye updates are complete.
+** AFS Mirror cleanups (clarkb 20240220)
-*** Running container with dedicated users. Next up all the ircbots.
+*** Ubuntu Xenial cleanups are starting to show up under topic:drop-ubuntu-xenial
-*** Upgrading Zookeeper
+*** Can followup with webserver log processing to determine which other mirrors may be dead.
-*** Upgrading MariaDB
+** Building Ubuntu Noble Nodes (clarkb 20240416)
-*** Eventually convert MariaDB container's from uid 999 to something that makes more sense on the system.
+*** Next step is to add Noble to our mirrors
-** Spring cleaning our Nodepool images (clarkb 20220125)
+** Gerrit 3.9 Upgrade Planning (clarkb 20240423)
-*** http://lists.opendev.org/pipermail/service-announce/2021-December/000029.html cleanup announcement
+*** Upgrade prep notes are going in https://etherpad.opendev.org/p/gerrit-upgrade-3.9
-*** Plan to remove CentOS 8 from Nodepool and Zuul first thing next week.
+*** https://www.gerritcodereview.com/3.9.html Release Notes
-** Spring cleaning for old reviews? (frickler 20220125)
+*** Downgrade is possible with an offline reindex using the old war.
-*** system-config has >300 open reviews, most of them in merge-conflict and >1y old
+*** Things to think about:
-*** Do we see value in keeping those or could we run some script to auto-abandon those with a helpful comment?
+**** Do we want to enable diff3 diffs on merge changes?
-*** Neutron has a script that could be easily adopted for this task
+**** 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/openstack/neutron/src/branch/master/tools/abandon_old_reviews.sh
+**** https://gerrit-review.googlesource.com/c/gerrit/+/424404 Upstream change to have release war build target without webfonts
-*** (clarkb) Considering that we had a big shift in approach to config management about 2 years ago I would say abandoning anything prior to that is probably fine. I have a change or two since then that might be good to keep around. Maybe we start at 2 years and see what that looks like? We can always restore changes too.
+**** 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.
-** Updating Grafana  (clarkb 20220125)
+*** Server could stand to be upgraded as well but I think it is probably best to decouple these concerns.
-*** https://review.opendev.org/c/opendev/grafyaml/+/825990 needed to fix api use against newer grafana
+** Cleaning up the openstack.org DNS zone (fungi 20240514)
-*** https://review.opendev.org/c/opendev/system-config/+/825410 update to latest grafana
+*** Proposed for deletion: https://paste.opendev.org/show/bVHJchKcKBnlgTNRHLVK/
-** Gerrit mergeabilityComputationBehavior (frickler 20220127)
-*** https://gerrit-documentation.storage.googleapis.com/Documentation/3.5.0/config-gerrit.html#change.mergeabilityComputationBehavior
-*** This was disabled while upgrading to 3.4.0 since the default is "NEVER"
-*** We could set the option to "API_REF_UPDATED_AND_CHANGE_REINDEX" to restore the previous behavior
-*** It doesn't look like we have to have any concerns in regard to CPU load http://cacti.openstack.org/cacti/graph.php?action=view&local_graph_id=70348&rra_id=all
 * Open discussion
@@ Line 53: / Line 47: @@
 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
-* Skyline project (below repos) moving from skyline/ to openstack/ namespace: https://review.opendev.org/c/openstack/project-config/+/822222
-** skyline/skyline-apiserver -> openstack/skyline-apiserver
-** skyline/skyline-console -> openstack/skyline-console
 == 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/

Difference between revisions of "Meetings/InfraTeamMeeting"

Revision as of 18:00, 13 May 2024

Contents

Weekly Project Infrastructure team meeting

Agenda for next meeting

Upcoming Project Renames

Previous meetings