1211734 - Migrate bouncer to AWS [10/15/2015]

Status: RESOLVED FIXED

(Cloud Services :: Operations: Miscellaneous, task)

Description

[Jeremy Orem [:oremj]]

Tracker bug for the bouncer migration.

Comment 1

[Jeremy Orem [:oremj]]

Migration plan:

1) Set on-premise database read only (instant)
2) mysqldump database (~5 min)
3) Import dump in to AWS database (~5 min)
4) Switch DNS for download.mozilla.org (~10 min)
5) Verify download.mozilla.org (?)
6) Deploy sentry (~10 min)
7) Full sentry run and verify again (~45 min)
8) Deploy admin interface (tuxedo) (~10 min)
9) Verify admin interface (?)

Comment 2

[Linda Ypulong [:unixfairy]]

Reviewed in 10/14 CAB

Comment 3

[Jeremy Orem [:oremj]]

Migration is complete.

Comment 4

[Sheeri Cabral [:sheeri]]

Not sure if this is expected, but I'm still seeing connections through the phx1 load balancer to the phx1 bouncer databases (user: download). Reopening....

I'm specifically talking about bouncer[1-4].db.phx1.mozilla.com, database name is "bouncer". (just in case I've got something wrong here).

(if instead we're talking about sentry[1-2].db.phx1.mozilla.com, db name "sentry", username "sentry", I'm still seeing a connection there, too....)

Comment 5

[Jeremy Orem [:oremj]]

The services are still up in phx1, so I suspect it's monitoring hitting the services directly, causing DB traffic. I also didn't shut down the sentry cron jobs, so those will create some db traffic as well.

Comment 6

[Jeremy Orem [:oremj]]

Let's move the db traffic talk to the decommission bug 1216633.