Jump to: navigation, search

Difference between revisions of "Meetings/InfraTeamMeeting"

(Agenda for next meeting)
(Agenda for next meeting)
(204 intermediate revisions by 11 users not shown)
Line 16: Line 16:
  
 
* Topics
 
* Topics
** Improving OpenDev's CD throughput (clarkb 20220614)
+
** 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
+
*** https://review.opendev.org/q/topic:jitsi_meet-jammy-update
*** Running Zuul cluster upgrade playbook automatically.
+
*** Started looking at the wiki there are rough notes at: https://etherpad.opendev.org/p/opendev-bionic-server-upgrades#L58
** Container maintenance (clarkb 20220614)
+
** MariaDB Upgrades (clarkb 20240220)
*** https://etherpad.opendev.org/p/opendev-container-maintenance
+
*** Relying on the container image MARIADB_AUTO_UPGRADE flag
*** Continue to update services with dedicated users.
+
*** Everything but Gerrit is done now. When do we think we want to do Gerrit?
*** Upgrading Zookeeper
+
** AFS Mirror cleanups (clarkb 20240220)
*** Upgrading MariaDB
+
*** Ubuntu Xenial cleanups are starting to show up under topic:drop-ubuntu-xenial
*** Eventually convert MariaDB container's from uid 999 to something that makes more sense on the system.
+
*** Can followup with webserver log processing to determine which other mirrors may be dead.
** Gerrit 3.5 upgrade planning (ianw 20220614)
+
** Building Ubuntu Noble Nodes (clarkb 20240416)
*** https://etherpad.opendev.org/p/gerrit-upgrade-3.5
+
*** Next step is to add Noble to our mirrors
*** http://lists.opendev.org/pipermail/service-announce/2022-May/000039.html Scheduled for 20:00 UTC June 19, 2022
+
** Gerrit 3.9 Upgrade Planning (clarkb 20240423)
** Zuul changing default Ansible version to v5 soon (clarkb 20220614)
+
*** Upgrade prep notes are going in https://etherpad.opendev.org/p/gerrit-upgrade-3.9
*** Now that Zuul supports Ansible v5 the next step is to default to v5
+
*** https://www.gerritcodereview.com/3.9.html Release Notes
*** Need to send an announcement for the default change in OpenDev happening at the end of June.
+
*** https://review.opendev.org/c/opendev/system-config/+/918333 Need updated and promoted 3.9 image before doing more testing.
** Enable webapp on nodepool launchers? (frickler 20220611)
+
*** Downgrade is possible with an offline reindex using the old war.
*** Would help with checking for image freshness / builds failing
+
*** Things to think about:
*** Also look into pushing stats into grafana?
+
**** Do we want to enable diff3 diffs on merge changes?
** Run a custom URL shortener service (frickler 20220611)
+
**** Change topic limit seems to only apply to open changes. Being over the limit doesn't seem to impact the upgrade process
*** Many people use bit.ly or similar in IRC channel topics and elsewhere
+
**** https://gerrit-review.googlesource.com/c/gerrit/+/424404 Upstream change to have release war build target without webfonts
*** https://opensource.com/article/18/7/apache-url-shortener shows an easy solution that could be git-based
+
**** 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.
*** Should be easy to with some new DNS record on static.o.o
+
*** Server could stand to be upgraded as well but I think it is probably best to decouple these concerns.
*** Data could be managed in a single file (maybe in project-config) or one file per URL
+
** Wiki SSL Cert Renewal (clarkb 20240423)
 +
*** Clarkb will renew Friday ish (May 10)
  
 
* Open discussion
 
* Open discussion
Line 48: Line 49:
 
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: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/