1503548 - ramp-up another mobile beetmoverworker dedicated for staging environment for various mobile products

Status: RESOLVED FIXED

(Release Engineering :: Release Automation: Uploading, enhancement)

Description

[Mihai Tabara [:mtabara]⌚️GMT]

+++ This bug was initially created as a clone of Bug #1485672 +++

More mobile products incoming, we need a staging mobile beetmoverworker to play with.

Comment 1

[Mihai Tabara [:mtabara]⌚️GMT]

We may have potentially lost the AMI used to built the beetmoverworkers. Currently discussing about using a new centos AMI image or rebuilt from existing.

Comment 2

[Mihai Tabara [:mtabara]⌚️GMT]

We now have a new beetmoverworker[1] for staging purposes.

[1]: https://tools.taskcluster.net/provisioners/scriptworker-prov-v1/worker-types/mobile-beetmover-v1/workers/mobile-beetmover-v1/mobile-beetmover-2

Comment 3

[Mihai Tabara [:mtabara]⌚️GMT]

I'll likely ramp-up another one, just in case we need a different product production one. I can always kill it.
I also want to test the build-cloud-tools end-to-end testing.

Comment 4

[Mihai Tabara [:mtabara]⌚️GMT]

Attachment: [puppet] pin mobile-beetmoverworker to mobile staging environments.

Comment 5

[Mihai Tabara [:mtabara]⌚️GMT]

Comment on attachment 9022152 [details] [review]
[puppet] pin mobile-beetmoverworker to mobile staging environments.

https://github.com/mozilla-releng/build-puppet/commit/d82e534d3304337fcd4b371070cf288245a873a3

Comment 6

[Mihai Tabara [:mtabara]⌚️GMT]

We now have another production machine ready and a staging instance ready
* https://tools.taskcluster.net/provisioners/scriptworker-prov-v1/worker-types/mobile-beetmover-v1/workers/mobile-beetmover-v1/mobile-beetmover-2
* https://tools.taskcluster.net/provisioners/scriptworker-prov-v1/worker-types/mobile-beetmover-v1/workers/mobile-beetmover-v1/mobil-beetmover-dev1