Closed Bug 645841 Opened 14 years ago Closed 14 years ago

point graphs-new.m.o at graphs1.dmz.sjc1.mozilla.com

Categories

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

Product:
mozilla.org Graveyard
Component:
Server Operations
Platform:
x86_64
Linux
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: rhelmer, Unassigned)

References

Details

We already have a CNAME for graphs-new.mozilla.org (right now points to the same box as graphs.mozilla.org). Not sure if there is a public IP for graphs1.dmz.sjc1.mozilla.com yet (server was set up in bug 627446).
Blocks: 601796
Looks like this does not have a public IP at the moment. I've discussed this with Derek Moore, and there is some concern about IP availability on this network. Would it be possible to simply make graphs-new.mozilla.org resolve to the appropriate internal IP, instead of public? Then when you're ready to make the new one live, it'll be simple to switch over the NAT mapping to point to the new machine, rather than the old.
(In reply to comment #1) > Looks like this does not have a public IP at the moment. > > I've discussed this with Derek Moore, and there is some concern about IP > availability on this network. Would it be possible to simply make > graphs-new.mozilla.org resolve to the appropriate internal IP, instead of > public? Then when you're ready to make the new one live, it'll be simple to > switch over the NAT mapping to point to the new machine, rather than the old. Unfortunately I don't think most of the users will have VPN setup (primarily Firefox devs) and it's also used by other projects like SeaMonkey.
(In reply to comment #2) > (In reply to comment #1) > > Looks like this does not have a public IP at the moment. > > > > I've discussed this with Derek Moore, and there is some concern about IP > > availability on this network. Would it be possible to simply make > > graphs-new.mozilla.org resolve to the appropriate internal IP, instead of > > public? Then when you're ready to make the new one live, it'll be simple to > > switch over the NAT mapping to point to the new machine, rather than the old. > > Unfortunately I don't think most of the users will have VPN setup (primarily > Firefox devs) and it's also used by other projects like SeaMonkey. These are the people we want to help us test the new system, BTW ^ :) The idea is that advertise graphs-new.m.o from the old graphs.m.o interface (this is the way it's been done in the past at least).
63.245.208.193 is set up for this. DNS is not changed yet, however... trying to determine how/where exactly to put this in place.
Status: NEW → ASSIGNED
DNS change is committed... it'll take a while to propagate since there was a pre-existing setup for this name, but otherwise this is completed.
Status: ASSIGNED → RESOLVED
Closed: 14 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.