Closed Bug 870758 Opened 11 years ago Closed 11 years ago

Move production thimble to AWS

Categories

(Webmaker Graveyard :: Thimble, defect)

Product:
Webmaker Graveyard
Component:
Thimble
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: jon, Assigned: jon)

Details

The primary reason for doing this is to make migration less hairy when we switch from Thimble-on-django to Thimble-on-node.

JP: You mentioned you've done some work to do this? Can you fill us in and let us know what else needs to be done?
Oops, forgot the needinfo?
Flags: needinfo?(johns)
I need to:
a) get real data in (it can be a challenge getting thimble dumps)
b) get you guys to QA thimble.mofoprod.net 
c) dance vigorously

Any required timeframe?  I've had this up for a bit.
Flags: needinfo?(johns)
Flags: needinfo?(jon)
Yeah, we'll need to figure out how to do that mysql db transfer again.

As for timeframe, I think next week would be good since the all-hands is the week after that. Is that doable for you?
Flags: needinfo?(jon)
did we get this done? (I thought everything was on S3 at this point =)
Nah, we didn't get it done yet. Perhaps something to do this week!
Taking this so I don't forget to do this.
Assignee: nobody → jon
Status: NEW → ASSIGNED
In lieu of doing this, we'll just be copying the prod DB over to AWS when we hit the switch on prod. Bug 880768
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.