Execute MDN Cut-Over Plan

[escattone]

User story

As an MDN developer, I want to move off of the MozMEAO-based infrastructure and onto the MozIT-based infrastructure.

Acceptance Criteria

• MDN Stage (developer.allizom.org) is running from MozIT-based infrastructure
• MDN Production (developer.mozilla.org) is running from MozIT-based infrastructure
• Interactive examples (interactive-examples.mdn.mozilla.net) are served from the MozIT-based infrastructure (S3 bucket and CDN)
• File attachments (mdn.mozillademos.org) are served from the MozIT-based CDN

Tasks:

• Execute the cut-over plan listed here (also see MDN Cutover plan #43)

[escattone]

This has been delayed until the next sprint. The new cut-over date is Wednesday Oct. 10, 2018.

[escattone]

Here is the cut-over plan.

[escattone]

Here's the content of a message that I sent to AWS support today:

We'd like to schedule the actual rollover for 11:00am PST Monday Oct. 29th. Would it be possible to have someone from AWS on hand at that time to perform the CloudFront CNAME changes?

We'd like to make the following CloudFront CNAME changes at that time:

1. CloudFront CNAME for developer.allizom.org from d2qvj2imcvj3x.cloudfront.net (the current CDN) to d3dnonefiwc0m5.cloudfront.net (the destination CDN)
2. CloudFront CNAME for developer.mozilla.org from d2jhm933xpgpf7.cloudfront.net (the current CDN) to d1avawhiqh9uo1.cloudfront.net (the destination CDN)
3. CloudFront CNAME for mdn.mozillademos.org from d12hez81brmsmv.cloudfront.net (the current CDN) to d2t4o13y32ehby.cloudfront.net (the destination CDN)
4. CloudFront CNAME for interactive-examples.mdn.mozilla.net from d2ln8dq04bm8td.cloudfront.net (the current CDN) to d3qsf99tp0r2vu.cloudfront.net (the destination CDN)

We've already created the following TXT records to support these changes:

1. _developer.allizom.org --> d3dnonefiwc0m5.cloudfront.net
2. _developer.mozilla.org --> d1avawhiqh9uo1.cloudfront.net
3. _mdn.mozillademos.org --> d2t4o13y32ehby.cloudfront.net
4. _interactive-examples.mdn.mozilla.net--> d3qsf99tp0r2vu.cloudfront.net

[limed]

AWS has responded and we will have someone available during that period to make the swap for us

[escattone]

Other than the manual transfer of the MozMEAO EFS data to the MozMEAO shared-backup bucket, which seemed to run into rate-limiting issues, the cut-over went very smoothly from 9am to 1pm PST on Monday Oct. 29th.

Regarding the transfer of the MozMEAO EFS content from EFS to S3 , we determined that no new files had been created since the hourly CronJob that performed that function had run at 8am PST.