Revision as of 21:55, 31 January 2022

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
  • OpenInfra Summit CFP needs your input: https://openinfra.dev/summit/
  • Service Coordinator nomination time has begun. You have until February 8, 2022

• Actions from last meeting

• Specs Review

• Topics
  • Improving OpenDev's CD throughput (clarkb 20220201)
    • Bootstrapping bridge via Zuul is now a complicated subject. Can use zuul secrets to make it happen. Are we comfortable with this?
    • https://review.opendev.org/c/opendev/infra-specs/+/821645 -- spec outlining some of the issues with secrets
    • https://review.opendev.org/c/opendev/system-config/+/821155 -- sample of secret writing; more info in changelog
  • Container maintenance (clarkb 20220201)
    • https://etherpad.opendev.org/p/opendev-container-maintenance
    • Running container with dedicated users. Next up all the ircbots.
    • Upgrading Zookeeper
    • Upgrading MariaDB
    • Eventually convert MariaDB container's from uid 999 to something that makes more sense on the system.
  • Spring cleaning our Nodepool images (clarkb 20220201)
    • http://lists.opendev.org/pipermail/service-announce/2021-December/000029.html cleanup announcement
    • Changes to remove CentOS 8 are up. Are we ready to go ahead with this? In order they should be merged:
      • https://review.opendev.org/c/openstack/project-config/+/827183
      • https://review.opendev.org/c/opendev/base-jobs/+/827181
      • https://review.opendev.org/c/openstack/project-config/+/827184
      • https://review.opendev.org/c/opendev/system-config/+/827186
  • Spring cleaning for old reviews? (frickler 20220201)
    • system-config has >300 open reviews, most of them in merge-conflict and >1y old
    • Do we see value in keeping those or could we run some script to auto-abandon those with a helpful comment?
    • Neutron has a script that could be easily adopted for this task
      • https://opendev.org/openstack/neutron/src/branch/master/tools/abandon_old_reviews.sh
    • Clarkb to produce a list of repos that can be retired. We can then retire the repos and abandon their open reviews as step 0
  • 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

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 foo/example -> bar/example: https://review.opendev.org/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/