From 874e36ac906960879483bb102d6a81ed91c6e193 Mon Sep 17 00:00:00 2001
From: Clark Boylan <clark.boylan@gmail.com>
Date: Wed, 12 Mar 2025 08:31:59 -0700
Subject: [PATCH] Update infra-prod limit semaphore to a max of 4

The max of 2 seems to be working well and system load on bridge has
remained reasonable. Double this again to 4 as it appears that should be
a safe limit load wise on bridge.

Change-Id: I9afcd76fae0cf0bc28c00fa44dd4390a99372185
---
 zuul.d/infra-prod.yaml | 10 +++-------
 1 file changed, 3 insertions(+), 7 deletions(-)

diff --git a/zuul.d/infra-prod.yaml b/zuul.d/infra-prod.yaml
index 4d79cb2c38..7a1f6db2b5 100644
--- a/zuul.d/infra-prod.yaml
+++ b/zuul.d/infra-prod.yaml
@@ -12,15 +12,11 @@
 # This semaphore limits the total number of production playbook
 # jobs that can run on bridge at one time. We want things to run in
 # parallel but we have a lot of jobs (particularly in the periodic
-# pipeline) that we don't want to run all at once.
+# pipeline) that we don't want to run all at once to avoid overwhelming
+# the bastion host.
 - semaphore:
     name: infra-prod-playbook-limit
-    # TODO(clarkb) this semaphore allows us to stage the rollout of
-    # parallel infra-prod job exceution in two steps. First we reorganize
-    # everything but roughly keep the same behaviors as before (max: 1).
-    # When we are happy with that we can bump this to 2 or higher and see
-    # things run in parallel.
-    max: 2
+    max: 4
 
 - job:
     name: infra-prod-bootstrap-bridge