Jump to: navigation, search

Difference between revisions of "Meetings/InfraTeamMeeting"

(Agenda for next meeting)
(Agenda for next meeting: Cleaning up the openstack.org DNS zone)
(204 intermediate revisions by 11 users not shown)
Line 10: Line 10:
  
 
* Announcements
 
* Announcements
 +
** Clarkb out 5/17 and 5/20
  
 
* Actions from last meeting
 
* Actions from last meeting
Line 16: Line 17:
  
 
* Topics
 
* Topics
** Improving OpenDev's CD throughput (clarkb 20220621)
+
** 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
*** https://review.opendev.org/c/opendev/system-config/+/846195 Running Zuul cluster upgrade playbook automatically.
+
*** Meetpad is done. Just need to clean up old servers when we feel confident we won't rollback.
** Container maintenance (clarkb 20220621)
+
*** What is next?
*** https://etherpad.opendev.org/p/opendev-container-maintenance
+
** AFS Mirror cleanups (clarkb 20240220)
*** Continue to update services with dedicated users.
+
*** 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)
**** review02's mariadb was upgraded to 10.6 from 10.4 using the process described in https://etherpad.opendev.org/p/gerrit-upgrade-3.5
+
*** Next step is to add Noble to our mirrors
** Gerrit 3.5 upgrade (ianw 20220621)
+
** Gerrit 3.9 Upgrade Planning (clarkb 20240423)
*** https://etherpad.opendev.org/p/gerrit-upgrade-3.5
+
*** Upgrade prep notes are going in https://etherpad.opendev.org/p/gerrit-upgrade-3.9
*** Upgrade completed.
+
*** https://www.gerritcodereview.com/3.9.html Release Notes
*** Couple of issues discovered
+
*** Downgrade is possible with an offline reindex using the old war.
**** https://bugs.chromium.org/p/gerrit/issues/detail?id=16018
+
*** Things to think about:
**** Setting a change to the WorkInProgress state seems to unconditionally mark it as having merge conflicts in change listings (but not on the change page itself)
+
**** Do we want to enable diff3 diffs on merge changes?
*** Time to look at removing our 3.4 image builds and adding 3.6 image builds with updated upgrade testing.
+
**** Change topic limit seems to only apply to open changes. Being over the limit doesn't seem to impact the upgrade process
** Enable webapp on nodepool launchers? (frickler 20220621)
+
**** https://gerrit-review.googlesource.com/c/gerrit/+/424404 Upstream change to have release war build target without webfonts
*** Would help with checking for image freshness / builds failing
+
**** 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.
*** Also look into pushing stats into grafana?
+
*** Server could stand to be upgraded as well but I think it is probably best to decouple these concerns.
** Run a custom URL shortener service (frickler 20220621)
+
** Cleaning up the openstack.org DNS zone (fungi 20240514)
*** Many people use bit.ly or similar in IRC channel topics and elsewhere
+
*** Proposed for deletion: https://paste.opendev.org/show/bVHJchKcKBnlgTNRHLVK/
*** https://opensource.com/article/18/7/apache-url-shortener shows an easy solution that could be git-based
 
*** Should be easy to with some new DNS record on static.o.o
 
*** Data could be managed in a single file (maybe in project-config) or one file per URL
 
  
 
* Open discussion
 
* Open discussion
Line 49: 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/