Difference between revisions of "Meetings/InfraTeamMeeting"
< Meetings
Clark Boylan (talk | contribs) (→Agenda for next meeting) |
Clark Boylan (talk | contribs) (→Agenda for next meeting) |
||
| Line 21: | Line 21: | ||
*** Replace bridge host once existing host is running ansible out of 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? | *** 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 | *** https://review.opendev.org/q/topic:bridge-ansible-venv | ||
** Upgrading Bionic servers to Focal/Jammy (clarkb 20221011) | ** 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 |
| + | **** 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). | ||
| + | **** Needed to use an up to date paramiko out of a virtualenv to run launch node as Jammy doesn't do SSH RSA + SHA1. | ||
** Mailman 3 (clarkb 20221011) | ** Mailman 3 (clarkb 20221011) | ||
*** https://review.opendev.org/c/opendev/system-config/+/851248 Worthy of review at this point | *** https://review.opendev.org/c/opendev/system-config/+/851248 Worthy of review at this point | ||
| Line 32: | Line 33: | ||
*** 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 | *** 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 | ||
** Switch base job nodeset to ubuntu-jammy (frickler 20221007) | ** Switch base job nodeset to ubuntu-jammy (frickler 20221007) | ||
| − | *** Ubuntu | + | *** Switching the default base job's nodeset to Ubuntu Jammy on October 25 (day of the meeting). |
| − | *** | + | ** Removing snapd (clarkb 20221025) |
| − | + | *** In the past we removed snapd as we didn't use it for anything. | |
| − | + | *** Stopped removing snapd in order to install kubectl. | |
| + | *** Should we go back to removing snapd globally and only add it back in where needed? | ||
| + | ** Updating base python docker images to use `pip wheel` (clarkb 20221025) | ||
| + | *** Pip changed how it addresses wheels in its wheel cache which broke our assemble script's ability to build packages on our image builds. | ||
| + | *** 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. | ||
| + | *** https://github.com/pypa/pip/issues/11527 | ||
| + | *** https://github.com/pypa/pip/pull/11538 | ||
| + | *** https://review.opendev.org/c/opendev/system-config/+/862152 | ||
* Open discussion | * Open discussion | ||
Revision as of 15:33, 21 October 2022
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
- PTG next week
- Actions from last meeting
- Specs Review
- Topics
- Bastion host (ianw 20221011)
- 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
- gitea-lb02 was launched using a Jammy image and is now in prod
- 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).
- Needed to use an up to date paramiko out of a virtualenv to run launch node as Jammy doesn't do SSH RSA + SHA1.
- Mailman 3 (clarkb 20221011)
- https://review.opendev.org/c/opendev/system-config/+/851248 Worthy of review at this point
- https://etherpad.opendev.org/p/mm3migration
- 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
- Switch base job nodeset to ubuntu-jammy (frickler 20221007)
- Switching the default base job's nodeset to Ubuntu Jammy on October 25 (day of the meeting).
- Removing snapd (clarkb 20221025)
- In the past we removed snapd as we didn't use it for anything.
- Stopped removing snapd in order to install kubectl.
- Should we go back to removing snapd globally and only add it back in where needed?
- Updating base python docker images to use `pip wheel` (clarkb 20221025)
- Pip changed how it addresses wheels in its wheel cache which broke our assemble script's ability to build packages on our image builds.
- 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.
- https://github.com/pypa/pip/issues/11527
- https://github.com/pypa/pip/pull/11538
- https://review.opendev.org/c/opendev/system-config/+/862152
- Bastion host (ianw 20221011)
- 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
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/
