1412861 - investigate using releng services to run merge/staging env instance

Status: RESOLVED INACTIVE

(Release Engineering :: Release Automation, enhancement)

Description

[Kim Moir [:kmoir] ET]

From Rok

Instead of deploying to EC2 or or ECS which are always running we can (re/ab)use taskcluster hooks for this. They are still docker images, just on demand docker images.

Here is how it will look:

(1) mozilla-releng/services already have a deployment target taskcluster hooks. every taskcluster hook that starts with "project-releng/services-*" is managed automatically.

(2) those taskcluster hooks are basically scheduled taskcluster tasks which means we can already use any docker image produces by mozilla-releng/services and are running somewhere in AWS.

(3) in your case or in the case where we need on-demand instance we can disable scheduling of taskcluster hook while still keeping it registered.

(4) when that time of the week/month/year comes they can click on the latest execution item and enter the "interactive mode" and voila they can already start playing with staging releases.

There are several advantages with this:
- we don't pay for something running which is only used once a month or even less
- we can give access to the service just by granting correct scopes for specific taskcluster hook
- authentication is taken care by taskcluster
- instead of documenting the steps we can even programmatically create a button somewhere on mozilla-releng.net which will open the interactive session.
- we really offload all the hard maintenance work to taskcluster team :)

Does the above make sense?

Comment 1

[Kim Moir [:kmoir] ET]

Attachment: Dockerfile

Dockerfile with for merging/staging env, not sure how to include credentials.

Comment 2

[Julien Cristau [:jcristau]]

merge day is now automated in scriptworkers