Migrate missioncontrol.tmo to gcp
Categories
(Cloud Services :: Mission Control, task, P1)
Tracking
(Not tracked)
People
(Reporter: wlach, Assigned: benwu)
References
(Depends on 1 open bug, Blocks 1 open bug)
Details
The tentative plan here is to keep missioncontrol v1 running in AWS until we're ready, then swap its replacement (based on the missioncontrol-v2 etl job) in after it is accepted by release management and other stakeholders, sometime in 2020.
Filing this bug for tracking purposes related to the overall GCP migration: issues related to the implementation of missioncontrol v2 should be filed/discussed elsewhere.
|
Reporter | |
Comment 1•5 years ago
|
||
While we are going to keep mission control v1 running in AWS for now, we do want to change it to fetch data from BigQuery/GCP instead of Athena/AWS, see bug 1594111.
|
||
Updated•5 years ago
|
|
|
Reporter | |
Comment 2•5 years ago
|
||
Theoretically this bug was about migrating the dashboard itself to GCP, but that's probably a confusing and subtle thing that we may not actually need to keep track of (we can just turn it off when we have a replacement next year). Ok with leaving this resolved.
Description
•