New issue
Advanced search Search tips

Issue 903847 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: 1
NextAction: ----
OS: Chrome
Pri: 0
Type: Feature

Blocked on: View detail
issue 766386
issue 904440
issue 851138
issue 914899

Blocking:
issue 903845


Show other hotlists

Hotlists containing this issue:
CrOSParallelCQ


Sign in to add a comment

Allocate additional builders for Parallel CQ load

Project Member Reported by jclinton@chromium.org, Nov 9

Issue description

Because PreCQ is removed and CQ+1 will do a non-HWTest dry run of a CL on all CQ builders, we’ll need many more machines in the fleet to support this. Currently, we have about 25 PreCQ jobs in flight concurrently. At 88 builders, that leads us to a pool of about 2,200 machines: 2.5x our current fleet.

The biggest problem that we face in doing this is IP whitelisting which is still used for two cases discussed below. This requires us to allocate external IP address blocks to accommodate the IP’s being publicly identifiable. We will remove these two blockers and avoid the public IP addresses. Allocating new public IP blocks can take up to two months.

 
Blockedon: 766386
Blocking: 903845
Blockedon: 851138
Blockedon: 904440
Labels: Disable-Nags
EstimatedDays: 1
Blockedon: 914899

Sign in to add a comment