Open
Bug 1687802
Opened 3 years ago
Updated 22 days ago
[tracker] socorro gcp migration (2024)
Categories
(Socorro :: General, task, P2)
Socorro
General
Tracking
(Not tracked)
NEW
People
(Reporter: willkg, Unassigned)
References
(Depends on 15 open bugs, Blocks 2 open bugs)
Details
In bug #1512641, we started moving to GCP. That migration was abandoned for non-technical and we switched back to AWS SQS for the processing queues so Socorro was entirely in a single data center again.
This project covers a new migrating to GCP project.
Project plan: https://docs.google.com/document/d/1J9f60UwU68Z-v7twoCcHQY6qkytPngq9fQaMX68J4IE/edit
|
Reporter | |
Comment 1•3 years ago
|
||
Documents from last time that we can crib from when building the new plan:
- Socorr: Pub/Sub migration plan 2019q1: https://docs.google.com/document/d/13_PbjSncCH60tLjkWst91B6TQQDaJYlSuSvPLqaWN5A/edit#
|
|
Reporter | |
Updated•3 years ago
|
Summary: [tracker] move to gcp (2020) → [tracker] move to gcp (2021)
|
|
Reporter | |
Comment 2•2 years ago
|
||
Updating year.
Summary: [tracker] move to gcp (2021) → [tracker] move to gcp (2022)
|
|
Reporter | |
Updated•1 year ago
|
Summary: [tracker] move to gcp (2022) → [tracker] move to gcp (2023)
|
|
Reporter | |
Updated•1 year ago
|
Summary: [tracker] move to gcp (2023) → [tracker] socorro gcp migration (2023)
|
||
Updated•2 months ago
|
Summary: [tracker] socorro gcp migration (2023) → [tracker] socorro gcp migration (2024)
You need to log in
before you can comment on or make changes to this bug.
Description
•