[tracker][infra] Move MDN from SCL3 to AWS

RESOLVED FIXED

Status

RESOLVED FIXED
4 years ago
a year ago

People

(Reporter: groovecoder, Assigned: jwhitlock)

Tracking

(Blocks: 1 bug, {meta})

Details

(URL)

(Reporter)

Updated

4 years ago
Depends on: 1110800
(Reporter)

Updated

4 years ago
Depends on: 1110805
(Reporter)

Updated

4 years ago
Depends on: 1110807

Updated

4 years ago
Keywords: meta
Summary: Move MDN from SCL3 to AWS → [tracker][infra] Move MDN from SCL3 to AWS
Depends on: 1223122
Depends on: 1159930
Depends on: 1218563
Depends on: 1142203
Depends on: 1223109
Depends on: 1119433
Depends on: 1225574
Depends on: 1238806
(Assignee)

Updated

3 years ago
Blocks: 1259503
(Assignee)

Updated

3 years ago
Blocks: 1268254
(Assignee)

Updated

a year ago
No longer depends on: 1142203
(Assignee)

Updated

a year ago
Depends on: 1391084
(Assignee)

Updated

a year ago
No longer depends on: 1159930
(Assignee)

Comment 1

a year ago
There's been a lot of work on the migration to Kubernetes (k8s) under the MozMEAO SRE team.  Dependencies in Bugzilla are out of date. Some migration strategies have changed, and some actions will be deferred to post-migration. I'll update over the next week.

The AWS migration project is tracked at:

https://github.com/mozmeao/infra/projects/4
Assignee: nobody → jwhitlock
(Assignee)

Updated

a year ago
Depends on: 1402708
(Assignee)

Updated

a year ago
Blocks: 1020491

Comment 2

a year ago
Commits pushed to master at https://github.com/mozilla/kuma

https://github.com/mozilla/kuma/commit/1979fe828a367917ceb5dd156ed62655c4d71b0f
bug 1110799: Add newrelic config file

This is the default config, with some settings expected from the
environment:

* NEW_RELIC_LICENSE_KEY for license_key
* NEW_RELIC_APP_NAME for app_name
* NEW_RELIC_MONITOR_MODE for monitor_mode (1 to talk to NR)

The changes from the default:

* log_file = stderr
* high_security = true (Mozilla standard)
* browser_monitoring.enabled = false (added, Mozilla standard)
* browser_monitoring.auto_instrument = false (Mozilla standard)

https://github.com/mozilla/kuma/commit/e869bacc510957659d0abe5c3b623ba842401cb8
Merge pull request #4447 from jwhitlock/newrelic-1110799

bug 1110799: Add New Relic config

Comment 3

a year ago
Commits pushed to master at https://github.com/mozilla/kuma

https://github.com/mozilla/kuma/commit/b07501fb9441f96056dc2703e2a61b8db5266780
bug 1110799: Expand raven/sentry configuration

* Send the revision hash, for release tracking
* Set a syncronous transport, which may be more compatible with meinheld
* Set the repos name, which may make tracebacks more useful
* Ignore DisallowedHost exceptions, which happen in AWS

https://github.com/mozilla/kuma/commit/c7b8ea91fe09d93df4fcd8ad6192496c4b412839
Merge pull request #4445 from jwhitlock/raven-1110799

bug 1110799: Update raven, expand configuration

Comment 4

a year ago
Commits pushed to master at https://github.com/mozilla/kuma

https://github.com/mozilla/kuma/commit/20b3afda67606000d52524d9ae4f639a4335e6f7
bug 1110799: Don't set repos in RAVEN_CONFIG

More research is needed to determine what this should be set to.

https://github.com/mozilla/kuma/commit/de455a8ba8b4e53e608c611b3d3e064e154b5c8c
Merge pull request #4448 from jwhitlock/raven2-1110799

bug 1110799: Don't set repos in RAVEN_CONFIG
(Assignee)

Comment 5

a year ago
The AWS migration is planned for October 10, 9:30 AM to 1:30 PM PST (4:30 PM - 8:30 PM UTC)
Status: NEW → ASSIGNED
(Assignee)

Updated

a year ago
Blocks: 1405519
(Assignee)

Updated

a year ago
No longer depends on: 1238806
See Also: → bug 1238806
(Assignee)

Comment 6

a year ago
The migration went smoothly, with one issue that was handled during the maintenance window [1].  We've been in AWS for 48 hours, and have added some resources to more smoothly handle some traffic spikes. There are many follow-on actions [2], but it looks like it will work.

We'd like to keep SCL3 up as an emergency backup for awhile, but it looks like we're in AWS for good.

Thanks to everyone who worked on the first phase of this project. Etherpad is having trouble staying available, so I made a copy of the original plan [3]. It was a lot more ambitious, both in schedule (Q3 2015) and in scope. Hopefully we can return to implement some of the ideas.

[1] https://github.com/mozmeao/infra/issues/410#issuecomment-336236391
[2] https://github.com/mozmeao/infra/projects/5
[3] https://gist.github.com/jwhitlock/c9db443399607bc858dffbc5baebbe00
Status: ASSIGNED → RESOLVED
Last Resolved: a year ago
Resolution: --- → FIXED

Comment 7

a year ago
Commits pushed to master at https://github.com/mozilla/kuma

https://github.com/mozilla/kuma/commit/82fa693d3ec43cec1de3c1199494965e108721dd
bug 1110799: redirect legacy domains

https://github.com/mozilla/kuma/commit/21953192b56795ad33582d402eed2119ce36ed5f
Merge pull request #4589 from escattone/redirect-legacy-domains-1110799

bug 1110799: redirect legacy domains
You need to log in before you can comment on or make changes to this bug.