Closed Bug 1263626 Opened 8 years ago Closed 8 years ago

Create a pool of new workers for performing recurring releng tasks

Categories

(Taskcluster :: Workers, defect)

Product:
Taskcluster
Component:
Workers
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: coop, Unassigned)

References

Details

(Whiteboard: [docker-worker]) 

We need a new worker type on which to run recurring releng tasks. This is meant as a replacement for cronjobs running on cruncher (bug 1235851).

There should be a small pool of these workers to provide some concurrency for tasks. We should also have workers in all the AWS regions we currently run in for resiliency.
We create and destroy instances on demand, so there's no need for a pool. And the workers are dynamically created in the cheapest region, so we are resilient to region failure as well.

I created a workerType named "releng-task" with a maximum capacity of 20 (simultaneous tasks) on m4.large's with a max of two tasks per instance.  I also granted queue:{create,define}-task:aws-provisioner-v1/releng-task to the `releng` LDAP group, so you should be able to do so.
Whiteboard: [docker-worker]
Component: Docker-Worker → Worker
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Component: Worker → Workers
You need to log in before you can comment on or make changes to this bug.