Closed Bug 552010 Opened 10 years ago Closed 10 years ago

Update config on personas.stage.mozilla.com

Categories

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

All
Other
task
Not set
critical

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: rdoherty, Assigned: aravind)

References

Details

From server/lib/personas_constants.php.dist copy the slave db info to server/lib/personas_constants.php and add the appropriate values. 

Need asap so we can push this live and alleviate load on the db servers.
Assignee: server-ops → aravind
The app looks like it lives on its own staging server, with its own staging db.. instead of living in the regular staging environment.  Justdave says its easier to clone the personas db into the staging server (and reuse the existing staging slave db for this), than setup an entirely new slave.

He is buried in dealing with graphs.m.o, and so punting this to Toby.
Assignee: aravind → telliott
Assignee: telliott → tellis
I dumped the data out of sm-personas01, copied the dump to Boris, then back over to tm-stage01-master01. Then I loaded up the dump into the master, which replicated to the slave.

Then I shut down sm-personas01 and announced this in #webdev.

I will now take a look at usernames and passwords in the file Ryan lists above to grant properly on tm-stage01-master01 and tm-stage01-slave01.
Note: when I mentioned slave I mean master. I have added extra configuration for the master. The original config should point to the slave.
Also granted all perms on personas DB on tm-stage01-master01 to personas login on both sm-personas01 and mrapp-stage02. Also granted SELECT perms to same on tm-stage01-slave01.

The password remains unchanged and is the same on both master/slave.

Returning bug to Aravind!
Assignee: tellis → aravind
Okay, config has been updated.  The original config points to the slave now, and the master points to the master.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.