Closed
Bug 627446
Opened 15 years ago
Closed 15 years ago
need production machine for graphserver 2.0
Categories
(mozilla.org Graveyard :: Server Operations, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: rhelmer, Assigned: jabba)
References
Details
We have been working on a new version of graphserver (http://graphs.mozilla.org) in bug 601796.
We have a staging box thanks to bug 619083, and the plan has been to run alongside current production in a vhost.
However, due to some dependencies we've picked up (node.js and node-canvas which needs a recent libcairo, and varnish for caching), it would probably make more sense to have a new RHEL6 box for this, and leave production undisturbed.
graphs-stage is totally adequate, the specs on that are:
--
Intel(R) Xeon(R) CPU L5420 @ 2.50GHz (/proc/cpu shows 4 cores)
4 GB RAM
200 GB disk
--
This machine would need read/write acces to the same production MySQL database that graphs.m.o uses.
| Assignee | ||
Updated•15 years ago
|
Assignee: server-ops → jdow
| Assignee | ||
Comment 1•15 years ago
|
||
The server is set up per the instructions that rob gave me. Currently the local settings aren't configured, since I don't want to hook this box up to the production database until we are ready to go. Also the cronjobs are commented out.
I'm not sure what the next steps are, so closing this bug out and you should file additional bugs for an eventual switchover of the graphs.mozilla.org DNS record, and the configuration for the production database.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
| Assignee | ||
Comment 2•15 years ago
|
||
The server is at graphs1.dmz.sjc1.mozilla.com
Updated•11 years ago
|
Product: mozilla.org → mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•