Closed
Bug 1015782
Opened 12 years ago
Closed 11 years ago
Setup Mozilla badgekit infrastructure
Categories
(Webmaker Graveyard :: DevOps, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: johns, Assigned: johns)
Details
We're going to be hosting an instance of badgekit for Mozilla under badgekit.mozilla.org and badgekitapi.mozilla.org (?).
Launch infrastructure and pipeline for this.
| Assignee | ||
Comment 1•12 years ago
|
||
TLDR: I have launched the infrastructure for staging completely, and have the production infrastructure written and ready to launch. http://badgekit-mozilla.mofostaging.net/ and http://badgekit-api-mozilla.mofostaging.net/
More detail:
* I took a dump of both production api and badgekit databases
* I setup new schemas for both of these in the shared staging db (badgekitapimozilla and badgekitmozilla schema names), as well as new users for these apps.
* I wrote all the puppet infrastructure for these new apps, keeping it separate-ish from badgekit as it exists now. I am using the same apt package, but that is easy enough to change if we need to host different versions between the badgekit proper and mozilla instances.
* All the creds are done and stored, and the existing Jenkins jobs for badgekit and badgekit-api are set to also push to these mozilla instances.
* Setup monitoring on both staging ELBS.
* Added these apps to Newrelic.
Let me know what we need further! When we go live, I'll host up the new RDS instances but this time probably put both schemas into one instance.
| Assignee | ||
Comment 2•12 years ago
|
||
Systems/Deploy scripts: https://github.com/mozilla/mofo_systems_scripts/commit/412b39832db431f260e5e6dd9ff01819f4e8cf6e
Puppet modules:
https://github.com/mozilla/mofo_system_configurations/pull/245
| Assignee | ||
Comment 3•11 years ago
|
||
This is all set.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•