Jump to: navigation, search

Difference between revisions of "Meetings/InfraTeamMeeting"

(add twitter topic)
(Agenda for next meeting)
Line 16: Line 16:
  
 
* Topics
 
* Topics
** Bastion host (ianw 20221108)
+
** Bastion host (ianw 20221115)
 
*** 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
+
** Upgrading Bionic servers to Focal/Jammy (clarkb 20221115)
*** https://review.opendev.org/c/opendev/system-config/+/863568
 
** 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 20221108)
 
*** 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
+
*** Currently debugging why updated images aren't working as expected. Appears to be some problem with django.
** Updating base python docker images to use `pip wheel` (clarkb 20221108)
+
** Updating base python docker images to use `pip wheel` (clarkb 20221115)
*** Pip changed how it addresses wheels in its wheel cache which broke our assemble script's ability to build packages on our image builds.
+
*** Will aim to land this change soon, then double check images built with new assemble process are happy.
*** 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.
+
** Etherpad docker container logs growth (clarkb 20221115)
*** https://github.com/pypa/pip/issues/11527
+
*** https://review.opendev.org/c/opendev/system-config/+/864060
*** https://github.com/pypa/pip/pull/11538
+
** Quo vadis storyboard (frickler 20221115)
*** 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
 
*** ML thread https://lists.opendev.org/pipermail/service-discuss/2022-October/000370.html
*** Many people interested in moving away from storyboard
+
*** No new movement on the mailing list. Maybe give it another week then we can consider feedback collected?
*** No volunteers to update our installation
+
** Nova server rescue behavior in vexxhost (clarkb 20221115)
*** How long can we/do we want to commit to running an outdated installation on an EOL OS?
+
*** There are image settings that need to be set for rescue images. A dedicated rescue image would also be able to set a non colliding disk label.
** 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
 
 
** Goodbye birdsite, hello tooters? (frickler 20221115)
 
** Goodbye birdsite, hello tooters? (frickler 20221115)
 
*** Twitter seems to be on a downward spiral and we should consider stopping using it
 
*** Twitter seems to be on a downward spiral and we should consider stopping using it

Revision as of 17:56, 15 November 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
  • 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/