Closed Bug 1386370 Opened 7 years ago Closed 7 years ago

Set workerGroup based on datacenter for hardware generic-worker instances

Categories

(Taskcluster :: Workers, enhancement)

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

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: dustin, Assigned: wcosta)

Details

Attachments

(1 file)

Configure worker-group based on fqdn. r=dustin
3.87 KB, patch
dustin
: review+
Details | Diff | Splinter Review 
modules/generic_worker/templates/generic-worker.config.erb
modules/taskcluster_worker/templates/taskcluster-worker.yml.erb

The latter is using a node-level `taskcluster_worker_group`, but I think it makes more sense to just configure that directly based on the datacenter, probably based on a regexp from $fqdn.
What would be the worker-group name convention? generic-worker uses "scl3" part of fqdn but tc-worker adds a prefix based on the machine.
Flags: needinfo?(dustin)
Since the hostname is in the workerId, I think just the datacenter ("scl3", "mdc1") is enough - "moonshot-scl3" isn't a pattern we need to continue.
Flags: needinfo?(dustin)
Can get I loaner yosemite 0200 reimaged without certificate blocked to test my patch?
Flags: needinfo?(arich)
I just repuppetized the existing machine.
Flags: needinfo?(arich)
Extract the datacenter name from fqdn and use that as the worker-group.
Attachment #8893580 - Flags: review?(dustin)
Attachment #8893580 - Flags: review?(dustin) → review+
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Component: Worker → Workers
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: