Closed Bug 659204 Opened 13 years ago Closed 13 years ago

move graphs1.stage.dmz.sjc1 from varnish to zeus

Categories

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

x86
macOS
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: rhelmer, Assigned: dumitru)

Details

I am not really taking advantage of varnish for graphserver (ended up doing node.js from cron to generate html5 canvas images instead), it would probably be easier for everybody if this used Zeus instead (less to install/configure).

I'd like to do this for production too, but let's test on staging first (since production has users now).
Assignee: server-ops → dgherman
What is the public-facing side of this?  graphs1.stage.dmz.sjc1 is an internal address.  (do you want an internal zeus vip?)
I think this is behind graphs-stage.mozilla.org or something like that, just need to move that to be a zeus VIP and set it up like our standard ssl offloading sites with caching (not sure if ssl is actually needed).
(In reply to comment #1)
> What is the public-facing side of this?  graphs1.stage.dmz.sjc1 is an
> internal address.  (do you want an internal zeus vip?)

Oops sorry, public facing side is: graphs.allizom.org

This is the graphs 2.0 staging server, we'll want to do this for production 2.0 after making sure everything goes fine on stage (graphs1.dmz.sjc1.mozilla.com aka graphs-new.mozilla.org)
graphs.allizom.org is now behind Zeus with caching enabled. I stopped Varnish on graphs1.stage.dmz.sjc1 and I moved Apache on port 80.
Robert, ping me on IRC if you see anything awry.
Status: NEW → RESOLVED
Closed: 13 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.