1285519 - Enable (at least) heavily used worker types in eu-central-1

Status: RESOLVED INACTIVE

(Infrastructure & Operations :: RelOps: General, task)

Description

[Pete Moore [:pmoore][:pete]]

Now we have eu-central-1 support:
https://github.com/taskcluster/aws-provisioner/blob/4e21a3c2edb32566e3b8fad4dcba71105600291d/schemas/create-worker-type-request.yml#L148

We should probably enable worker types in this region, especially ones where we have a large number of instances, such as desktop-test and desktop-test-xlarge.

We should check cloud-mirror et al is enabled before rolling out.

Comment 1

[John Ford [:jhford] CET/CEST Berlin Time]

I just confirmed that Cloud Mirror is allowed in eu-central-1.  For an example URL:

https://cloud-mirror.taskcluster.net/v1/redirect/s3/eu-central-1/https%3A%2F%2Fs3-us-west-2.amazonaws.com%2Ftaskcluster-public-artifacts%2FTTsIG6GcSDWtTFzTmEn8fw%2F0%2Fpublic%2Fbuild%2Ftarget.tar.bz2

This is an old Firefox build, but is an example of cloud-mirror working.

Comment 2

[Pete Moore [:pmoore][:pete]]

Hey Greg,

This might be a nice chance for me to get hands on experience rolling out new AMIs for docker worker. Can we have a short meeting to go through this together before I do it?

Also, do you see any reasons not to roll out, or other things that need to be changed before we do? For example sccache bucket configuration / hg clone bundle region-specific things, or anything else?

Thanks!

Comment 3

[Greg Arndt [:garndt]]

You shouldn't need to roll out a new ami, you can copy the existing one used in us-west-2 to eu-central right?

I would need to test this because the last time I tried to use packer to deploy it didn't support eu-central.  This might no longer be a problem.

Comment 4

[Chris Cooper [:coop] (he/him)]

Found in triage.

Pete: I believe this is done. Can we close this out?

Comment 5

[Pete Moore [:pmoore][:pete]]

I only see eu-central-1 enabled on windows worker types - none of the linux worker types:

gecko-1-b-win2012
gecko-1-b-win2012-beta
gecko-1-b-win2016
gecko-2-b-win2012
gecko-t-win10-64
gecko-t-win10-64-beta
gecko-t-win10-64-cu
gecko-t-win10-64-gpu
gecko-t-win10-64-gpu-b
gecko-t-win7-32
gecko-t-win7-32-beta
gecko-t-win7-32-cu
gecko-t-win7-32-gpu
gecko-t-win7-32-gpu-b

So this still looks like a TODO.

@Wander, any reason the linux workers aren't using eu-central-1 ?

----

Separately, we might want to think about making sure our tools that generate worker type definitions (e.g. our packer scripts in docker-worker, OpenCloudConfig, the code in generic-worker that manages non-gecko worker types like nss-win2012r2) have all regions enabled **by default** so that our worker types only don't use a given region if there is a good reason not to. But that should be a separate bug.

Comment 6

[Wander Lairson Costa]

(In reply to Pete Moore [:pmoore][:pete] from comment #5)
> I only see eu-central-1 enabled on windows worker types - none of the linux
> worker types:
> 
> gecko-1-b-win2012
> gecko-1-b-win2012-beta
> gecko-1-b-win2016
> gecko-2-b-win2012
> gecko-t-win10-64
> gecko-t-win10-64-beta
> gecko-t-win10-64-cu
> gecko-t-win10-64-gpu
> gecko-t-win10-64-gpu-b
> gecko-t-win7-32
> gecko-t-win7-32-beta
> gecko-t-win7-32-cu
> gecko-t-win7-32-gpu
> gecko-t-win7-32-gpu-b
> 
> So this still looks like a TODO.
> 
> @Wander, any reason the linux workers aren't using eu-central-1 ?
> 
> ----
> 
> Separately, we might want to think about making sure our tools that generate
> worker type definitions (e.g. our packer scripts in docker-worker,
> OpenCloudConfig, the code in generic-worker that manages non-gecko worker
> types like nss-win2012r2) have all regions enabled **by default** so that
> our worker types only don't use a given region if there is a good reason not
> to. But that should be a separate bug.

is gecko-t-win* a Linux worker-type?

Comment 7

[Pete Moore [:pmoore][:pete]]

(In reply to Wander Lairson Costa [:wcosta] from comment #6)
> is gecko-t-win* a Linux worker-type?

No. The worker types I listed are the ones that *do* use eu-central-1, and they are all Windows worker types. As far as I know, we should be using eu-central-1 for all our linux worker types too, but they are not using eu-central-1, so didn't appear in the list of worker types that do use eu-central-1.

Comment 8

[[github robot]]

Commit pushed to master at https://github.com/taskcluster/docker-worker

https://github.com/taskcluster/docker-worker/commit/24e1cbae5ea7823901310f63bf4be8a66f1dc17f
Bug 1285519: Add eu-central-1 region for deployment.

Comment 9

[Wander Lairson Costa]

worker-types need to be updated to use the new region.

Comment 10

[Chris Cooper [:coop] (he/him)]

(In reply to Wander Lairson Costa [:wcosta] from comment #9)

worker-types need to be updated to use the new region.

Wander: have the worker types been updated?

Comment 11

[Wander Lairson Costa]

(In reply to Chris Cooper [:coop] pronoun: he from comment #10)

(In reply to Wander Lairson Costa [:wcosta] from comment #9)

worker-types need to be updated to use the new region.

Wander: have the worker types been updated?

It generates the images but worker-types have not been updated. I need to update the deploy scripts to do it.

Comment 12

[Dustin J. Mitchell [:dustin] (he/him)]

I think this is something releops can decide they want to do.

Comment 13

[Pete Moore [:pmoore][:pete]]

Not actively working on this at the moment.