Jump to: navigation, search

Difference between revisions of "Meetings/InfraTeamMeeting"

(Agenda for next meeting)
(Agenda for next meeting)
 
Line 1: Line 1:
  
 
<!-- ## page was renamed from Meetings/CITeamMeeting -->
 
<!-- ## page was renamed from Meetings/CITeamMeeting -->
{{:Header}}
 
 
 
= Weekly Project Infrastructure team meeting =
 
= Weekly Project Infrastructure team meeting =
  
The OpenStack Project Infrastructure Team holds public weekly meetings in <code><nowiki>#openstack-meeting</nowiki></code>, Tuesdays at 1900 UTC. Everyone interested in infrastructure and process surrounding automated testing and deployment is encouraged to attend.
+
The OpenDev Team holds public weekly meetings in <code><nowiki>#opendev-meeting</nowiki></code> 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).
 
Please feel free to add agenda items (and your IRC nick in parenthesis).
  
 
== Agenda for next meeting ==
 
== Agenda for next meeting ==
 +
 +
* Announcements
  
 
* Actions from last meeting
 
* Actions from last meeting
* Priority Specs
+
 
** Storyboard streaming API: https://review.openstack.org/#/c/105252/
+
* Specs Review
** Migrate to Zanata: https://review.openstack.org/#/c/133222/
+
 
* Schedule next project renames
+
* Topics
* Priority Efforts
+
** Improving OpenDev's CD throughput (clarkb 20220621)
** Swift logs
+
*** Bootstrapping bridge via Zuul is now a complicated subject. Can use zuul secrets to make it happen. Are we comfortable with this?
*** https://etherpad.openstack.org/p/swift_logs_next_steps
+
*** https://review.opendev.org/c/opendev/infra-specs/+/821645 -- spec outlining some of the issues with secrets
** Puppet module split
+
*** https://review.opendev.org/c/opendev/system-config/+/821155 -- sample of secret writing; more info in changelog
*** asselin proposing to streamline module split by pre-reviewing & merging the following two patches. Then, a much simpler follow-up patch with lines uncommented & updated can be proposed for each individual module. After module split is done, we can propose a new patch to clean-up unneeded/commented out portions
+
*** https://review.opendev.org/c/opendev/system-config/+/846195 Running Zuul cluster upgrade playbook automatically.
**** https://review.openstack.org/#/c/140523/
+
** Container maintenance (clarkb 20220621)
**** https://review.openstack.org/#/c/140548/
+
*** https://etherpad.opendev.org/p/opendev-container-maintenance
*** Given the above work to speed up & simplify the process, I'd like to propose a mini-sprint to split out as many modules as possible within a timeboxed time. Perhaps Monday Dec 22? (asselin)
+
*** Continue to update services with dedicated users.
** Nodepool DIB
+
*** Upgrading Zookeeper
** Docs publishing
+
*** Upgrading MariaDB
*** Holding pattern
+
**** review02's mariadb was upgraded to 10.6 from 10.4 using the process described in https://etherpad.opendev.org/p/gerrit-upgrade-3.5
** Jobs on trusty
+
** Gerrit 3.5 upgrade (ianw 20220621)
*** https://etherpad.openstack.org/p/py34-transition
+
*** https://etherpad.opendev.org/p/gerrit-upgrade-3.5
* Determine where to land third party testing instructions (pleia2)
+
*** Upgrade completed.
** Currently people in the third party community rely upon a series of blog posts by jaypipes to set things up, which are wonderful but need updating and centralized control for updating
+
*** Couple of issues discovered
** Options:
+
**** https://bugs.chromium.org/p/gerrit/issues/detail?id=16018
*** http://ci.openstack.org/third_party.html
+
**** Setting a change to the WorkInProgress state seems to unconditionally mark it as having merge conflicts in change listings (but not on the change page itself)
*** http://docs.openstack.org/infra/manual/third-party.html
+
*** Time to look at removing our 3.4 image builds and adding 3.6 image builds with updated upgrade testing.
*** Other?
+
** Enable webapp on nodepool launchers? (frickler 20220621)
** jaypipes is prepared to convert to .rst + update his documentation to be ready by early-to-mid January
+
*** Would help with checking for image freshness / builds failing
** pleia2 and anteaya have volunteered for review+testing of this documentation
+
*** Also look into pushing stats into grafana?
* Explore idea of upgrading Gerrit to ver 2.9.x (https://gerrit-documentation.storage.googleapis.com/ReleaseNotes/ReleaseNotes-2.9.2.html)
+
** Run a custom URL shortener service (frickler 20220621)
** sdague wanted the 'conflicts' query (https://gerrit-documentation.storage.googleapis.com/Documentation/2.9.2/user-search.html)
+
*** Many people use bit.ly or similar in IRC channel topics and elsewhere
* Create plugins for Gerrit <-> Storyboard integration instead of using jeepyb:  https://storyboard.openstack.org/#!/story/2000012
+
*** https://opensource.com/article/18/7/apache-url-shortener shows an easy solution that could be git-based
* Strategy for upstreaming Gerrit command to ls-members of 'Registered Users' group
+
*** Should be easy to with some new DNS record on static.o.o
** It's already implemented in plugin (only for Gerrit 2.9.x): https://gerrit.googlesource.com/plugins/admin-console/+/master/src/main/resources/Documentation/cmd-ls-users.md
+
*** Data could be managed in a single file (maybe in project-config) or one file per URL
** Options: attempt to backport to 2.8.x? upgrade Gerrit to 2.9.x first then use plugin as-is? add 'ls-members' feature to Gerrit core (master) then backport to 2.9.x branch?
+
 
* Options for procedural -2 (jeblair)
 
* Fedora 21 (ianw 12/16)
 
** https://review.openstack.org/140857 (F21 nodes on rackspace)
 
** https://review.openstack.org/140889 (F21 experimental job)
 
** https://review.openstack.org/140901 (Nodepool DIB -- handle numeric release)
 
** https://review.openstack.org/140911 (Add F21 image build with released final image)
 
 
* Open discussion
 
* Open discussion
  
 
== Upcoming Project Renames ==
 
== Upcoming Project Renames ==
<!-- * none (any additions should mention original->new full names and link to the corresponding change in Gerrit) -->
+
(any additions should mention original->new full names and link to the corresponding project-config rename change in Gerrit)
* openstack/oslo.version -> openstack-attic/oslo.version (https://review.openstack.org/#/c/141812/)
+
Changes should have their topic set to project-rename.
 +
 
 +
* Rename foo/example -> bar/example: https://review.opendev.org/123456
  
 
== Previous meetings ==
 
== 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/
 
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/

Latest revision as of 22:47, 20 June 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/