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)
(168 intermediate revisions by 10 users not shown)
Line 10: Line 10:
  
 
* Announcements
 
* Announcements
** PTG next week
+
** Clarkb out 5/17 and 5/20
  
 
* Actions from last meeting
 
* Actions from last meeting
Line 17: Line 17:
  
 
* Topics
 
* Topics
** Bastion host (ianw 20221011)
+
** Upgrading Old Servers (clarkb 20230627)
*** Move ansible to a venv.
 
*** Replace bridge host once existing host is running ansible out of a venv
 
*** bastion host OS upgrade.  prioin-place?  new host?  wait until have time to return to some of the bootstrapping/parallel job work?
 
*** Are console log files no longer being written? Did base-jobs playbook get updated too?
 
*** https://review.opendev.org/q/topic:bridge-ansible-venv
 
** Upgrading Bionic servers to Focal/Jammy (clarkb 20221011)
 
 
*** https://etherpad.opendev.org/p/opendev-bionic-server-upgrades
 
*** https://etherpad.opendev.org/p/opendev-bionic-server-upgrades
*** gitea-lb02 was launched using a Jammy image and is now in prod
+
*** https://etherpad.opendev.org/p/opendev-focal-server-upgrades
**** Used upstream image published by Ubuntu uploaded to vexxhost and converted to raw. This allows for max compatibility with bfv on vexxhost (gitea-lb02 is not bfv).
+
*** Started looking at the wiki there are rough notes at: https://etherpad.opendev.org/p/opendev-bionic-server-upgrades#L58
**** Needed to use an up to date paramiko out of a virtualenv to run launch node as Jammy doesn't do SSH RSA + SHA1.
+
*** Meetpad is done. Just need to clean up old servers when we feel confident we won't rollback.
** Mailman 3 (clarkb 20221011)
+
*** What is next?
*** https://review.opendev.org/c/opendev/system-config/+/851248 Worthy of review at this point
+
** AFS Mirror cleanups (clarkb 20240220)
*** https://etherpad.opendev.org/p/mm3migration
+
*** Ubuntu Xenial cleanups are starting to show up under topic:drop-ubuntu-xenial
*** https://review.opendev.org/c/opendev/system-config/+/860157 Forking the upstream images due to lack of attention on issues and PRs we've filed
+
*** Can followup with webserver log processing to determine which other mirrors may be dead.
** Switch base job nodeset to ubuntu-jammy (frickler 20221007)
+
** Building Ubuntu Noble Nodes (clarkb 20240416)
*** Switching the default base job's nodeset to Ubuntu Jammy on October 25 (day of the meeting).
+
*** Next step is to add Noble to our mirrors
** Removing snapd (clarkb 20221025)
+
** Gerrit 3.9 Upgrade Planning (clarkb 20240423)
*** In the past we removed snapd as we didn't use it for anything.
+
*** Upgrade prep notes are going in https://etherpad.opendev.org/p/gerrit-upgrade-3.9
*** Stopped removing snapd in order to install kubectl.
+
*** https://www.gerritcodereview.com/3.9.html Release Notes
*** Should we go back to removing snapd globally and only add it back in where needed?
+
*** Downgrade is possible with an offline reindex using the old war.
** Updating base python docker images to use `pip wheel` (clarkb 20221025)
+
*** Things to think about:
*** Pip changed how it addresses wheels in its wheel cache which broke our assemble script's ability to build packages on our image builds.
+
**** Do we want to enable diff3 diffs on merge changes?
*** I've filed a bug against pip for this and pushed a PR to fix it. However, upstream pip says we shouldn't rely on the wheel cache like this and should use `pip wheel` instead.
+
**** Change topic limit seems to only apply to open changes. Being over the limit doesn't seem to impact the upgrade process
*** https://github.com/pypa/pip/issues/11527
+
**** https://gerrit-review.googlesource.com/c/gerrit/+/424404 Upstream change to have release war build target without webfonts
*** https://github.com/pypa/pip/pull/11538
+
**** 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://review.opendev.org/c/opendev/system-config/+/862152
+
*** 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
 
* Open discussion
Line 51: 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/