Jump to: navigation, search

Difference between revisions of "Meetings/InfraTeamMeeting"

(Agenda for next meeting)
(Agenda for next meeting)
 
(997 intermediate revisions by 77 users not shown)
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).
Line 12: Line 10:
  
 
* Announcements
 
* Announcements
 +
 
* Actions from last meeting
 
* Actions from last meeting
* Specs approval
+
 
* Priority Efforts
+
* Specs Review
** Gerrit upgrade
+
** Mailman 3 spec https://review.opendev.org/810990
** Swift logs
+
 
** Nodepool DIB
+
* Topics
** Downstream Puppet
+
** Improving OpenDev's CD throughput (clarkb 20211026)
** Maniphest
+
*** We can run many of our jobs in parallel in all of our CD pipelines. But this requires we properly document/address dependencies
*** Changes that need approval: https://review.openstack.org/#/q/status:open+topic:maniphest,n,z
+
**** Need to understand our job dependencies and properly note them in Zuul config or address them by combining jobs.
**** Adding rebuild_phab_infra-dev.sh https://review.openstack.org/#/c/240795/
+
***** Example 1: Combine service-gitea-lb and service-gitea jobs.
**** Re-home migrate-to-phab.sql https://review.openstack.org/#/c/240682/
+
***** Example 2: Combine letsencrypt and nameserver jobs
**** Re-home migrate-to-phab.sql https://review.openstack.org/#/c/240784/
+
***** Example 3: Have all jobs with webserver config express a dependency on the letsencrypt job
** Docs publishing
+
**** Suggest we document the known job dependencies in a human readable format, then encode this into zuul, then we can switch to parallel runs.
*** Holding pattern while Swift logs issues get ironed out
+
**** https://review.opendev.org/c/opendev/system-config/+/807672
 +
***** should list dependencies for all jobs
 +
***** zuul doesn't trigger on this?  not sure on best approach to make it mergable
 +
**** https://review.opendev.org/c/opendev/base-jobs/+/807807
 +
***** currently every executor adds keys for bridge, then logs in and clones system-config before running playbooks
 +
***** this change makes split jobs to do this.  however, production remains the same as both are called.
 +
**** https://review.opendev.org/c/opendev/system-config/+/807808
 +
***** this is a follow-on that adds a base job to clone system-config, and stops the other production jobs re-cloning.
 +
***** this job must run first, but then all other jobs can run in parallel, as they are all in the same buildset and using the same "view" of system-config for that particular run
 +
** Gerrit Account cleanups (clarkb 20211026)
 +
*** 33 conflicts remain. Clarkb has written notes on proposed plans for each user in the comments of review02:~clarkb/gerrit_user_cleanups/audit-results-annotated.yaml
 +
** Fedora 34 test node booting problems (clarkb 20211026)
 +
*** Changes to Fedora's kernel packaging broke Xen
 +
*** Not yet sure if that may have also somehow broken OVH and iweb.
 +
** Begin planning for Gerrit 3.4 upgrade (clarkb 20211026)
 +
*** Read through release notes and identify areas of concern.
 +
**** https://www.gerritcodereview.com/3.4.html
 +
*** Do we need to modify system-config-run-review-3.4 or system-config-upgrade-review jobs to test any specific behaviors?
 +
*** Probably worth holding a 3.4 test node and doing a skim for any unexpected behaviors.
 +
 
 
* Open discussion
 
* Open discussion
  
 
== Upcoming Project Renames ==
 
== Upcoming Project Renames ==
(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-infra/puppet-openstack-health -> openstack-infra/puppet-openstack_health
+
* Rename foo/example -> bar/example: https://review.opendev.org/123456
** https://review.openstack.org/230421
 
* stackforge/networking-bigswitch -> openstack/networking-bigswitch
 
** apologies from kevinbenton for not getting this put on the wiki in time. he thought to be in 'openstack/' as a networking project that it had to be in the stadium, which it currently isn't compatible with due to the dev cycle.
 
** https://review.openstack.org/#/c/237753/
 
* networking-bagpipe-l2 -> networking-bagpipe
 
** https://review.openstack.org/#/c/237936
 
** (the presence of "l2" has proven repeatedly confusing now that this project host things that goes beyond only Neutron L2 networks)
 
  
 
== 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 23:40, 25 October 2021

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
  • Topics
    • Improving OpenDev's CD throughput (clarkb 20211026)
      • We can run many of our jobs in parallel in all of our CD pipelines. But this requires we properly document/address dependencies
        • Need to understand our job dependencies and properly note them in Zuul config or address them by combining jobs.
          • Example 1: Combine service-gitea-lb and service-gitea jobs.
          • Example 2: Combine letsencrypt and nameserver jobs
          • Example 3: Have all jobs with webserver config express a dependency on the letsencrypt job
        • Suggest we document the known job dependencies in a human readable format, then encode this into zuul, then we can switch to parallel runs.
        • https://review.opendev.org/c/opendev/system-config/+/807672
          • should list dependencies for all jobs
          • zuul doesn't trigger on this? not sure on best approach to make it mergable
        • https://review.opendev.org/c/opendev/base-jobs/+/807807
          • currently every executor adds keys for bridge, then logs in and clones system-config before running playbooks
          • this change makes split jobs to do this. however, production remains the same as both are called.
        • https://review.opendev.org/c/opendev/system-config/+/807808
          • this is a follow-on that adds a base job to clone system-config, and stops the other production jobs re-cloning.
          • this job must run first, but then all other jobs can run in parallel, as they are all in the same buildset and using the same "view" of system-config for that particular run
    • Gerrit Account cleanups (clarkb 20211026)
      • 33 conflicts remain. Clarkb has written notes on proposed plans for each user in the comments of review02:~clarkb/gerrit_user_cleanups/audit-results-annotated.yaml
    • Fedora 34 test node booting problems (clarkb 20211026)
      • Changes to Fedora's kernel packaging broke Xen
      • Not yet sure if that may have also somehow broken OVH and iweb.
    • Begin planning for Gerrit 3.4 upgrade (clarkb 20211026)
      • Read through release notes and identify areas of concern.
      • Do we need to modify system-config-run-review-3.4 or system-config-upgrade-review jobs to test any specific behaviors?
      • Probably worth holding a 3.4 test node and doing a skim for any unexpected behaviors.
  • Open discussion

Upcoming Project Renames

(any additions should mention original->new full names and link to the corresponding project-config rename change in Gerrit)

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/