Closed Bug 716084 Opened 13 years ago Closed 12 years ago

sketch out a plan for databases' scl3 move

Categories

(Data & BI Services Team :: DB: MySQL, task)

task
Not set
critical

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: dustin, Assigned: cshields)

References

Details

I'd like to get an idea what the move to sjc1 looks like for db services.

I think this includes at *least* mysql and postgres, plus backups.  If there are other "generic" databases services you guys offer that I don't know about, englighten me.  Don't worry too much about individual consumers of the services -- I'll tackle them separately.

I'm not looking for a detailed plan (yet), but a sketch:

  what will be moving, what will be thrown out, what will be purchased anew

  what kinds of creativity will be required/possible to minimize downtime

I made a handy-dandy empty page for the purpose:
  https://mana.mozilla.org/wiki/display/websites/db+services
you can compare
  https://mana.mozilla.org/wiki/display/websites/releng+services
for an idea of what should go in those columns.

Also, if it's OK that I come to your weekly meeting when you talk about this, let me know when it occurs?
Summary: sketch out a plan for scl3 move → sketch out a plan for databases' scl3 move
Assignee: server-ops-database → cshields
from IRC:

dustin: sheeri: is the dedicated-mysql-for-releng-in-scl3 rolled into the database-team's plans already?
Severity: normal → critical
I got some of this today, and filed some bugs.  I will look for the rest from corey as things progress.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Product: mozilla.org → Data & BI Services Team
You need to log in before you can comment on or make changes to this bug.