Jump to: navigation, search

Difference between revisions of "Meetings/InfraTeamMeeting"

(Agenda for next meeting)
(Upcoming Project Renames)
 
(688 intermediate revisions by 43 users not shown)
Line 3: Line 3:
 
= 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 10: Line 10:
  
 
* Announcements
 
* Announcements
 +
** PTG this week.
 +
*** OpenDev session Wednesday October 20, 2021 at 14:00 - 16:00 UTC in https://meetpad.opendev.org/oct2021-ptg-opendev
 +
*** Zuul session Thursday October 21, 2021 at 14:00 UTC in https://meetpad.opendev.org/zuul-2021-10-21
 +
 
* Actions from last meeting
 
* Actions from last meeting
* Specs approval
 
* Priority Efforts
 
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/ansible_puppet_apply.html Ansible Puppet Apply]
 
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/infra-cloud.html Infra-cloud]
 
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/openstackci.html Common OpenStack CI Solution]
 
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/task-tracker.html A Task Tracker for OpenStack]
 
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/zuulv3.html Zuul v3]
 
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/nodepool-zookeeper-workers.html Nodepool: Use Zookeeper for Workers]
 
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/newton-on-xenial.html Newton testing on Xenial]
 
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/doc-publishing.html Docs Publishing via AFS]
 
  
* General topics
+
* Specs Review
** ''cached image reduction changes'' (ianw 1-Nov-2016)
+
** Mailman 3 spec https://review.opendev.org/810990
*** '''summary''' : change devstack's "tools/image_list.sh" to take arguments that allow us to only download test images we use in the gate
+
 
**** https://review.openstack.org/377150 <- devstack change
+
* Topics
**** https://review.openstack.org/377159 <- project-config cache-devstack change
+
** Improving OpenDev's CD throughput (clarkb 20211019)
*** concern -- if we only get certain images, what if we miss new image requirements and start bringing them over network on each run?
+
*** We can run many of our jobs in parallel in all of our CD pipelines. But this requires we properly document/address dependencies
**** https://review.openstack.org/391702 <- devstack change to prevent downloading of images during run
+
**** Need to understand our job dependencies and properly note them in Zuul config or address them by combining jobs.
**** https://review.openstack.org/391713 <- add sentinel file to enable above
+
***** Example 1: Combine service-gitea-lb and service-gitea jobs.
*** thoughts?
+
***** Example 2: Combine letsencrypt and nameserver jobs
**** http://paste.openstack.org/show/587514/ <- current images cached.  not a huge problem
+
***** Example 3: Have all jobs with webserver config express a dependency on the letsencrypt job
** Force gate-{name}-pep8-{node} to build needed wheels - pabelanger
+
**** 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.openstack.org/#/c/391875/
+
**** https://review.opendev.org/c/opendev/system-config/+/807672
*** High chance of breaking pep8 jobs, how to spread the message, date
+
***** 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 20211019)
 +
*** 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
 +
** Gerrit project renames (clarkb 20211019)
 +
*** Overall went well.
 +
*** Possible trouble renaming secrets and doing ZK secrets backups?
 +
*** We accidentally updated all Gitea projects. Should we just do that by default: https://review.opendev.org/c/opendev/system-config/+/814443 ?
 +
** Improve zuul restarts (frickler 20211014)
 +
*** Docs at https://docs.opendev.org/opendev/system-config/latest/zuul.html#restarting-the-scheduler need updating
 +
**** What to restart (scheduler,web,fingergw?) and how (docker restart vs. docker-compose)
 +
**** When to run the re-enqueue
 +
**** Collecting debug information
 +
*** Don't reenqueue periodic jobs
 +
 
 
* Open discussion
 
* Open discussion
  
Line 40: Line 54:
 
(any additions should mention original->new full names and link to the corresponding project-config rename change in Gerrit)
 
(any additions should mention original->new full names and link to the corresponding project-config rename change in Gerrit)
  
[https://review.openstack.org/#/c/381332/ rsc -> valence]
+
* 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:56, 18 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

  • Actions from last meeting
  • Topics
    • Improving OpenDev's CD throughput (clarkb 20211019)
      • 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 20211019)
      • 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
    • Gerrit project renames (clarkb 20211019)
    • Improve zuul restarts (frickler 20211014)
  • 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/