Difference between revisions of "Meetings/InfraTeamMeeting"
< Meetings
Clark Boylan (talk | contribs) (→Agenda for next meeting) |
|||
| Line 16: | Line 16: | ||
* Topics | * Topics | ||
| − | ** Bastion host (ianw | + | ** Bastion host (ianw 20221108) |
*** https://review.opendev.org/q/topic:prod-bastion-group | *** https://review.opendev.org/q/topic:prod-bastion-group | ||
*** https://review.opendev.org/q/topic:bridge-ansible-venv | *** https://review.opendev.org/q/topic:bridge-ansible-venv | ||
| + | *** https://review.opendev.org/c/opendev/system-config/+/863564 | ||
| + | *** https://review.opendev.org/c/opendev/system-config/+/863568 | ||
** Upgrading Bionic servers to Focal/Jammy (clarkb 20221101) | ** Upgrading Bionic servers to Focal/Jammy (clarkb 20221101) | ||
*** https://etherpad.opendev.org/p/opendev-bionic-server-upgrades | *** https://etherpad.opendev.org/p/opendev-bionic-server-upgrades | ||
| − | + | ** Mailman 3 (clarkb 20221108) | |
| − | |||
| − | |||
| − | ** Mailman 3 (clarkb | ||
*** 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 | ||
*** https://etherpad.opendev.org/p/mm3migration | *** 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 | *** 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 | ||
| − | ** Updating base python docker images to use `pip wheel` (clarkb | + | ** Updating base python docker images to use `pip wheel` (clarkb 20221108) |
*** Pip changed how it addresses wheels in its wheel cache which broke our assemble script's ability to build packages on our image builds. | *** 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. | *** 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. | ||
| Line 41: | Line 40: | ||
*** No volunteers to update our installation | *** No volunteers to update our installation | ||
*** How long can we/do we want to commit to running an outdated installation on an EOL OS? | *** How long can we/do we want to commit to running an outdated installation on an EOL OS? | ||
| + | ** Nova server rescue behavior in vexxhost (clarkb 20221108) | ||
| + | *** Clarkb has tested this and the behaviors are surprising | ||
| + | *** Rescuing a normal disk instance results in the instance boot with the rescue image kernel and the rescued instance's root device mounted on / instead of the rescue image mounted to /. | ||
| + | *** Rescuing a BFV instance fails. First with the default microversion because old Nova API doesn't support this. When using microversion 2.88 it also fails, but only after attempting to rescue. | ||
| + | **** The instance goes into an error state due to "cannot be rescued: Driver Error: Cannot access storage file" | ||
| + | **** Attempting to unrescue the instance also fails because you cannot unrescue an instance that is in an error state | ||
* Open discussion | * Open discussion | ||
Revision as of 23:43, 7 November 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
- Actions from last meeting
- Specs Review
- Topics
- Bastion host (ianw 20221108)
- Upgrading Bionic servers to Focal/Jammy (clarkb 20221101)
- Mailman 3 (clarkb 20221108)
- 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
- Updating base python docker images to use `pip wheel` (clarkb 20221108)
- 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
- Etherpad docker container logs growth (clarkb 20221101)
- Need change to log to syslog instead similar to other services.
- Quo vadis storyboard (frickler 20221107)
- ML thread https://lists.opendev.org/pipermail/service-discuss/2022-October/000370.html
- Many people interested in moving away from storyboard
- No volunteers to update our installation
- How long can we/do we want to commit to running an outdated installation on an EOL OS?
- Nova server rescue behavior in vexxhost (clarkb 20221108)
- Clarkb has tested this and the behaviors are surprising
- Rescuing a normal disk instance results in the instance boot with the rescue image kernel and the rescued instance's root device mounted on / instead of the rescue image mounted to /.
- Rescuing a BFV instance fails. First with the default microversion because old Nova API doesn't support this. When using microversion 2.88 it also fails, but only after attempting to rescue.
- The instance goes into an error state due to "cannot be rescued: Driver Error: Cannot access storage file"
- Attempting to unrescue the instance also fails because you cannot unrescue an instance that is in an error state
- 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/
