Closed
Bug 1023561
Opened 10 years ago
Closed 10 years ago
New staging mysql database for RelEng mapper application (https://wiki.mozilla.org/ReleaseEngineering/Applications/Mapper )
Categories
(Data & BI Services Team :: DB: MySQL, task)
Data & BI Services Team
DB: MySQL
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: pmoore, Assigned: mpressman)
Details
Mapper is a RelEngAPI application. We are currently sharing a mysql schema for staging mapper with staging RelEngAPI itself: mysql://relengapi_stage@stage-rw-vip.db.scl3.mozilla.com/relengapi_stage However, we would like to have a separate database for Mapper and RelEngAPI to separate these concerns. It would be good if they could be hosted on the same instance. Please note, the primary user of the Staging Mapper database will be the RelEngAPI staging cluster, which currently has the following (one) host: web1.stage.releng.webapp.scl3.mozilla.com Database size is likely to be ~ 1GB or less. No strict backup requirements - we can blow away and create from scratch relatively easily. I've raised a very similar bug for production too (bug 1023555). The difference between these two bugs is that this one pertains to staging - the other pertains to production. Many thanks, Pete
Assignee | ||
Comment 1•10 years ago
|
||
stage database named mapper created on same host as releng_api_stage. I will email you the credentials
Assignee | ||
Comment 2•10 years ago
|
||
sorry database name is mapper_stage
Assignee | ||
Updated•10 years ago
|
Assignee: server-ops-database → mpressman
Assignee | ||
Comment 3•10 years ago
|
||
Credentials emailed
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 4•10 years ago
|
||
Thanks for that Matt. I was able to migrate our staging environment to use the new schema, populate it, remove the tables from the old schema etc - so all good! Pete
Updated•10 years ago
|
Product: mozilla.org → Data & BI Services Team
You need to log in
before you can comment on or make changes to this bug.
Description
•