Change MDN from NetApp in SCL3 to AWS

RESOLVED FIXED

Status

RESOLVED FIXED
4 years ago
a year ago

People

(Reporter: groovecoder, Assigned: metadave)

Tracking

Details

Comment hidden (empty)
(Reporter)

Updated

4 years ago
Depends on: 1110801
(Reporter)

Updated

4 years ago
Depends on: 1110803
(Reporter)

Updated

4 years ago
Depends on: 1110808
Assignee: nobody → jezdez
Assignee: jezdez → nobody
No longer depends on: 1110801
We have a working process to serve files from EFS in AWS. Most files have been transferred, and we have a process to sync the files on the "go live" date, tracked in the production release plan:

https://github.com/mozmeao/infra/issues/410

EFS is a closer match to NetApp than S3, and chosen to speed the transition. S3 is a better fit, and would potentially enable multi-region support (bug 1110801). However, that will need to wait until post-AWS.
Assignee: nobody → dparfitt
Status: NEW → RESOLVED
Last Resolved: a year ago
Resolution: --- → FIXED
Summary: Change MDN from NetApp in SCL3 to S3 on AWS → Change MDN from NetApp in SCL3 to AWS
You need to log in before you can comment on or make changes to this bug.