1504856 - feature request: cloudops development environment site

Status: RESOLVED WONTFIX

(Cloud Services :: Operations: Bouncer, enhancement)

Description

[Aki Sasaki (not active)]

Tl;dr: It would be very useful for releng and other teams to be able to go to a site to request n development instances of services like balrog and bouncer. These instances would be created in a known state, with throwaway creds, and could be used for staging release runs that won't affect other, concurrent, staging release runs. After we're done with these instances, we can mark them for deletion.

Details
=======
Problem: Currently releng is able to run staging releases using our existing staging environments. However, we're only able to run a single staging release of a given type at a time; a concurrent staging release would overwrite state in the shared staging environments (staging balrog, staging bouncer, staging s3 bucket, etc); this breaks concurrent testing.

Proposed solution:
If we're able to spin up n development instances of these services and point our staging releases at them, we can keep the staging release runs isolated and get useful information from them.

Also, if we can spin these development instances in a known state, we can make modifications to them before running our staging releases if we want to test specific test cases. By controlling when we spin these down, we can test multiple releases -- can staging release 1 update to staging release 2, for example.

By making this a site rather than a series of bugs, the idea is we'll be more self-serve and less reliant on paging cloudops.

Our staging releases are already close to being usable by other teams, e.g. the Firefox build team, which should remove bottlenecks to development. By allowing those teams to also request dev instances of these services, we reduce releng and cloudops bottlenecks for them to make Firefox build improvements.

Could we get a site up where we can request development instances of balrog and bouncer (and potentially more services in the future)?

Comment 1

[Habibullah Pagarkar (use Slack)]

:oremj and :habib to discuss this in more detail

Comment 2

[Jeremy Orem [:oremj]]

Closing this for now. Please re-open if this is still needed.