Jump to: navigation, search

Difference between revisions of "Meetings/InfraTeamMeeting"

(Agenda for next meeting)
(Agenda for next meeting)
 
(26 intermediate revisions by 3 users not shown)
Line 10: Line 10:
  
 
* Announcements
 
* Announcements
** Service coordinator nominations open February 6, 2024 - February 20, 2024
 
*** https://lists.opendev.org/archives/list/service-discuss@lists.opendev.org/thread/TB2OFBIGWZEYC7L4MCYA46EXIX5T47TY/
 
*** No nominees as of the time the agenda was put together. Nominations stay open 4 hours beyond the end of our meeting.
 
  
 
* Actions from last meeting
 
* Actions from last meeting
Line 19: Line 16:
  
 
* 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
 +
*** https://etherpad.opendev.org/p/opendev-focal-server-upgrades
 
*** https://review.opendev.org/q/topic:jitsi_meet-jammy-update
 
*** https://review.opendev.org/q/topic:jitsi_meet-jammy-update
*** https://review.opendev.org/c/opendev/system-config/+/908512 Ensure new servers have sufficient CPU version levels.
 
 
*** Started looking at the wiki there are rough notes at: https://etherpad.opendev.org/p/opendev-bionic-server-upgrades#L58
 
*** Started looking at the wiki there are rough notes at: https://etherpad.opendev.org/p/opendev-bionic-server-upgrades#L58
*** Hound looks to be a fairly simple service with indexed/ached data on disk.  It's currently running Focal with "bookwork" containers Any reason to stay there?
+
** MariaDB Upgrades (clarkb 20240220)
*** I think there was a suggestion we could implement prometheus and once were happy with that drop cacti, Is that correct?
 
** PrePTG Summary (clarkb 20240220)
 
*** https://lists.opendev.org/archives/list/service-discuss@lists.opendev.org/thread/GJFCZJ5QECXYNIIF62RCOT2DDKRGTAC6/
 
** MariaDB Upgrades (clarkb 20240220)
 
 
*** Relying on the container image MARIADB_AUTO_UPGRADE flag
 
*** Relying on the container image MARIADB_AUTO_UPGRADE flag
*** Paste, Etherpad, Gitea, Gerrit, Refstack, and Mailman could use upgrades. Starting with Paste due to its simplicity.
+
*** Everything but Gerrit is done now. When do we think we want to do Gerrit?
** AFS Mirror cleanups (clarkb 20240220)
+
** AFS Mirror cleanups (clarkb 20240220)
*** We will remove OpenSUSE Leap, Debian Buster, CentOS 7, and Ubuntu Xenial
+
*** 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.
 
*** 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
 +
*** https://review.opendev.org/c/opendev/system-config/+/918333 Need updated and promoted 3.9 image before doing more testing.
 +
*** 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.
 +
** Wiki SSL Cert Renewal (clarkb 20240423)
 +
*** Clarkb will renew Friday ish (May 10)
  
 
* Open discussion
 
* Open discussion
Line 42: 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/

Latest 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/