search

taskcluster / taskcluster-rfcs

Taskcluster team planning
Mozilla Public License 2.0
11 stars 19 forks source link

RFC: workerPoolId / taskQueueId #145

Closed djmitche closed 5 years ago

djmitche commented 5 years ago

I'd love feedback from @tomprince and some other folks in releng too..

djmitche commented 5 years ago

do we have a way to add some information about a worker somewhere

Yes, we should be able to support that in worker-manager

is there some way to mark that certain workers aren't dynamically spun up and down by the worker manager

worker-manager will know that (they'll have different providers). You can put whatever information you want in the workerPoolId identifier, and I'd expect in most cases that will be the same as the current providerId and workerType. The only bit I really want to change is aws-provisioner-v1 because it's both long and soon-to-be inaccurate.

djmitche commented 5 years ago

That's a good point - we could use gecko-1-ec2/build-linux for example, and give out scopes for just gecko-1-*.

djmitche commented 5 years ago

The value of the two names is to avoid the confusion described in the second paragraph of the motivation section. Aki's comments mention some cases where that mapping might not be 1:1, too.

djmitche commented 5 years ago

OK, that's everyone that's here :)

I'll take this to final-comment now, targeting a decision next Wednesday.