Closed Bug 595358 Opened 14 years ago Closed 14 years ago

Need DB dump from Input prod -> staging

Categories

(mozilla.org Graveyard :: Server Operations, task)

Product:
mozilla.org Graveyard
Component:
Server Operations
Type:
task
Priority:
Not set
Severity:
blocker

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: stephend, Assigned: justdave)

References

(
URL
)

Details

In order to properly test Input's 1.8 milestone, we'll need a dump of the production database.  Dave Dash should know more...
Actually we need a daily dump to be cron'd somehow from production to staging.
Can you take care of your imports if we just get the dump to you?  Do you have access to cm-webdev01-master01 where we drop all of the current drops that webdev gets?
Assignee: server-ops → justdave
I have access to the drops, I don't have write access to the staging database... but if I'm given access to it, I can setup a cron.
QA needs this for testing on staging; justdave: think you'll have some time to get this set up today or early tomorrow?
Just to escalate, but we have a push to production happening on thursday night and this is a blocker for us.
Severity: major → critical
in the middle of Boy Scout stuff right now, but I should be able to get to this as soon as I get back from that (probably about 3 to 4 hours)
Back to the pool.
Assignee: justdave → server-ops
Assignee: server-ops → justdave
still mine, I'm working on it.
production's been copied to stage.  Still working on the cron job to make it persistent.
I have this set up where I can essentially press a button and have it happen if we need it again, but I'm holding off on making it automatic right now because I'll probably have to do it two or three times manually to make sure it works right (it involves flag files to know when the dump file has shown up and so forth) and I don't want to screw it up when you have QA on a tight deadline.  If you'd like it refreshed again with the data from the 14th (it has the 13th's backup restored to it right now) let me know when I can do it without screwing anyone over (it'll be about 15 minutes of downtime for the DB when it runs).  When this QA cycle finishes, I'll finish the job and get it cronned.
Also, from Dave Dash:

1. Schematic needs to be run after the database cron
2. We need a cron task (Also run after schematic) to make staging adjustments.
care to elaborate?  Is that a script somewhere?
2. is not written.... so you're blocked on me - stephen is there a bug for that?

1. is schematic, it's already run whenever there's a git pull on staging, just re-run it after the db dump, and then I think we're good.
(In reply to comment #13)
> 2. is not written.... so you're blocked on me - stephen is there a bug for
> that?

Nah, you guys told me to just put this stuff in the bug -- now's a perfect time to reinstate your bug-filing skills, Dave!
Dave, can we resume this/get it on a cron?  I think we need a recent dump to re-fix bugs like bug 595349.
Blocks: 602427
Still blocking testing.
Severity: critical → blocker
OK, cron job is now in place.  This should automatically deploy daily now.  There's a trigger on it set to trigger the import as soon as the current day's database backup of production shows up.  The backup server pushes to tm-stage01-master01 every hour at 25 minutes past the hour.  At 30 minutes past every hour, tm-stage01-master01 will check if there's a new file, and import it if it shows up.  The backups usually finish sometime between 6am and 9am every morning.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Verified FIXED for the DB dump; thanks!
Status: RESOLVED → VERIFIED
No longer blocks: 602427
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.