Jump to: navigation, search

Difference between revisions of "Meetings/InfraTeamMeeting"

m (→‎Weekly Project Infrastructure team 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 Efforts
+
 
−
** Swift logs
+
* Specs Review
−
*** https://etherpad.openstack.org/p/swift_logs_next_steps
+
 
−
** Puppet module split
+
* Topics
−
*** asselin (available first 20 mins of meeting) completed Jenkins module split
+
** Upgrading Old Servers (clarkb 20230627)
−
**** module metadata patch needs reviews: https://review.openstack.org/134373
+
*** https://etherpad.opendev.org/p/opendev-bionic-server-upgrades
−
**** spec was updated following prior meetings to better reflect actual process, with one still pending: https://review.openstack.org/134393
+
*** https://etherpad.opendev.org/p/opendev-focal-server-upgrades
−
*** nibz has two module splits ready to go, github and pip
+
*** https://review.opendev.org/q/topic:jitsi_meet-jammy-update
−
**** pip is a bit weird because we landed the create repo but not the split out
+
*** Started looking at the wiki there are rough notes at: https://etherpad.opendev.org/p/opendev-bionic-server-upgrades#L58
−
**** https://review.openstack.org/#/c/134723/ would change it so we don't need to keep track of modules in two places
+
** MariaDB Upgrades (clarkb 20240220)
−
** Nodepool DIB
+
*** Relying on the container image MARIADB_AUTO_UPGRADE flag
−
** Docs publishing
+
*** Everything but Gerrit is done now. When do we think we want to do Gerrit?
−
*** Holding pattern
+
** AFS Mirror cleanups (clarkb 20240220)
−
** Jobs on trusty
+
*** Ubuntu Xenial cleanups are starting to show up under topic:drop-ubuntu-xenial
−
*** https://etherpad.openstack.org/p/py34-transition
+
*** Can followup with webserver log processing to determine which other mirrors may be dead.
−
* puppet-httpd (ianw 11/18)
+
** Building Ubuntu Noble Nodes (clarkb 20240416)
−
** import or new?
+
*** Next step is to add Noble to our mirrors
−
** Well this ship kindof sailed. Now must do a full new one(nibalizer happy to do it)
+
** Gerrit 3.9 Upgrade Planning (clarkb 20240423)
−
* ianw outstanding reviews (ianw 11/18)
+
*** Upgrade prep notes are going in https://etherpad.opendev.org/p/gerrit-upgrade-3.9
−
** https://review.openstack.org/131921 (set useful path)
+
*** https://www.gerritcodereview.com/3.9.html Release Notes
−
** https://review.openstack.org/115168 (nodepool images doco)
+
*** https://review.opendev.org/c/opendev/system-config/+/918333 Need updated and promoted 3.9 image before doing more testing.
−
** https://review.openstack.org/133881 (copy apache logs)
+
*** Downgrade is possible with an offline reindex using the old war.
−
** https://review.openstack.org/133914 (fixup sudo wildcard
+
*** Things to think about:
−
* Zuul reviews (hashar 11/18, can't attend meeting feel free to skip)
+
**** Do we want to enable diff3 diffs on merge changes?
−
** There are a few +2ed changes pending a final review + merge
+
**** Change topic limit seems to only apply to open changes. Being over the limit doesn't seem to impact the upgrade process
−
** List: https://review.openstack.org/#/q/project:openstack-infra/zuul+is:open+label:code-review%252B2+label:verified%252B1+NOT+label:workflow-1,n,z
+
**** https://gerrit-review.googlesource.com/c/gerrit/+/424404 Upstream change to have release war build target without webfonts
−
** https://review.openstack.org/86498 "Allow zuul-server to run a merger process" (should simplify setup for third parties)
+
**** There is a new batched ref updated event that collects multiple ref updated events in a single event. This is disabled by default, but could one day impact zuul. Work sorting out likely.
−
** https://review.openstack.org/114510 "Enforce ref only for gerrit events that supply a ref"
+
*** Server could stand to be upgraded as well but I think it is probably best to decouple these concerns.
−
** https://review.openstack.org/128921 "Update merge status after merge:merge is submitted"
+
** Wiki SSL Cert Renewal (clarkb 20240423)
−
** https://review.openstack.org/131559 "Support stracktracing on Geard embedded server"
+
*** Clarkb will renew Friday ish (May 10)
−
* Puppet module maturity(nibz)
+
 
−
** A few things are comming to the infra modules
 
−
** auto upload to forge on signed tags (upload as openstackci or as openstackinfra or openstack-infra ?)
 
−
** generated html documenation and upload(upload to where)
 
−
** section of infra manual for infra-modules
 
−
** unit (puppet-rspec) and integration (beaker-rspec) tests
 
 
* 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)
−
* stackforge/heat-translator -> openstack/heat-translator (gerrit changes proposal request - https://review.openstack.org/#/c/131558/1)
+
Changes should have their topic set to project-rename.
−
* stackforge/tooz -> openstack/tooz (https://review.openstack.org/#/c/135215/ )
 
  
−
== Items for Future Meetings ==
+
* Rename example/foo -> example/bar: https://review.opendev.org/c/openstack/project-config/+/123456
−
* for November 25, 2014 meeting
 
−
** stackforge ci account naming: proposal from fungi => when a third-party ci is operated by and exclusively testing changes for a single project, it's allowable for their project name to appear as the subsystem being tested within the account display name
 
  
 
== 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 21:25, 6 May 2024

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/

Retrieved from "https://wiki.openstack.org/w/index.php?title=Meetings/InfraTeamMeeting&oldid=184792"