Meetings/InfraTeamMeeting
< Meetings
Contents
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 and programming committee need your input: https://openinfra.dev/summit/
- Service Coordinator nomination time has begun.
- Actions from last meeting
- Specs Review
- Topics
- Improving OpenDev's CD throughput (clarkb 20220125)
- 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 20220125)
- https://etherpad.opendev.org/p/opendev-container-maintenance
- Buster to Bullseye updates are complete.
- 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 20220125)
- http://lists.opendev.org/pipermail/service-announce/2021-December/000029.html cleanup announcement
- Plan to remove CentOS 8 from Nodepool and Zuul first thing next week.
- Spring cleaning for old reviews? (frickler 20220125)
- 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
- (clarkb) Considering that we had a big shift in approach to config management about 2 years ago I would say abandoning anything prior to that is probably fine. I have a change or two since then that might be good to keep around. Maybe we start at 2 years and see what that looks like? We can always restore changes too.
- Updating Grafana (clarkb 20220125)
- https://review.opendev.org/c/opendev/grafyaml/+/825990 needed to fix api use against newer grafana
- https://review.opendev.org/c/opendev/system-config/+/825410 update to latest grafana
- Improving OpenDev's CD throughput (clarkb 20220125)
- 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/