Jump to: navigation, search

Difference between revisions of "Meetings/InfraTeamMeeting"

(Agenda for next meeting)
(Upcoming Project Renames)
 
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
 +
** OpenInfra Summit CFP and programming committee need your input: https://openinfra.dev/summit/
  
 
* 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) is working on Jenkins module split, working with 'shepherd' fungi. Spec was updated to better reflect actual process. Let's get these merged:
+
** Improving OpenDev's CD throughput (clarkb 20220118)
**** https://review.openstack.org/#/c/129768/
+
*** Bootstrapping bridge via Zuul is now a complicated subject. Can use zuul secrets to make it happen. Are we comfortable with this?
**** https://review.openstack.org/#/c/132129/
+
*** https://review.opendev.org/c/opendev/infra-specs/+/821645 -- spec outlining some of the issues with secrets
*** Need to clarify 'last step' of spec for new Jenkins puppet module repo:
+
*** https://review.opendev.org/c/opendev/system-config/+/821155 -- sample of secret writing; more info in changelog
**** Spec: https://review.openstack.org/#/c/134393/1
+
** Container maintenance (clarkb 20220118)
**** New Jenkins repo changes depend on ^^: https://review.openstack.org/#/c/134373/
+
*** https://etherpad.opendev.org/p/opendev-container-maintenance
*** Afterwards, we should be good to do more puppet-module splits in parallel
+
*** Buster to Bullseye updates are complete.
*** nibz has two module splits ready to go, github and pip
+
*** Running container with dedicated users. Next up all the ircbots.
**** pip is a bit weird because we landed the create repo but not the split out
+
*** Upgrading Zookeeper
**** https://review.openstack.org/#/c/134723/ would change it so we don't need to keep track of modules in two places
+
*** Upgrading MariaDB
** Nodepool DIB
+
*** Eventually convert MariaDB container's from uid 999 to something that makes more sense on the system.
** Docs publishing
+
** Spring cleaning our Nodepool images (clarkb 20220118)
*** Holding pattern
+
*** http://lists.opendev.org/pipermail/service-announce/2021-December/000029.html cleanup announcement
** Jobs on trusty
+
*** Tumbleweed has been removed
**** https://etherpad.openstack.org/p/py34-transition
+
*** CentOS 8 removal process has begun. Gave projects until the end of the month before we remove the nodeset and nodepool configs.
* puppet-httpd (ianw 11/18)
+
** Scheduling Gerrit Project Renames (clarkb 20220118)
** import or new?
+
*** Target January 24 around 22:00 UTC?
** Well this ship kindof sailed. Now must do a full new one(nibalizer happy to do it)
+
** Spring cleaning for old reviews? (frickler 20220113)
* ianw outstanding reviews (ianw 11/18)
+
*** system-config has >300 open reviews, most of them in merge-conflict and >1y old
** https://review.openstack.org/131921 (set useful path)
+
*** Do we see value in keeping those or could we run some script to auto-abandon those with a helpful comment?
** https://review.openstack.org/115168 (nodepool images doco)
+
*** Neutron has a script that could be easily adopted for this task
** https://review.openstack.org/133881 (copy apache logs)
+
**** https://opendev.org/openstack/neutron/src/branch/master/tools/abandon_old_reviews.sh
** https://review.openstack.org/133914 (fixup sudo wildcard
+
 
* Zuul reviews (hashar 11/18, can't attend meeting feel free to skip)
 
** There are a few +2ed changes pending a final review + merge
 
** 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://review.openstack.org/86498 "Allow zuul-server to run a merger process" (should simplify setup for third parties)
 
** https://review.openstack.org/114510 "Enforce ref only for gerrit events that supply a ref"
 
** https://review.openstack.org/128921 "Update merge status after merge:merge is submitted"
 
** https://review.openstack.org/131559 "Support stracktracing on Geard embedded server"
 
* 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 foo/example -> bar/example: https://review.opendev.org/123456
* for November 25, 2014 meeting
+
* Skyline project (below repos) moving from skyline/ to openstack/ namespace: https://review.opendev.org/c/openstack/project-config/+/822222
** 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
+
** skyline/skyline-apiserver -> openstack/skyline-apiserver
 +
** skyline/skyline-console -> openstack/skyline-console
  
 
== 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:29, 20 January 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

  • 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/