Closed
Bug 522923
Opened 15 years ago
Closed 15 years ago
sumo / GLB deployment in Amsterdam/Singapore
Categories
(mozilla.org Graveyard :: Server Operations, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: mrz, Assigned: arzhel)
References
Details
(Whiteboard: 10/22/2009 @ 9pm)
About ready to add sumo into GLB and serve from Amsterdam. It's staged @ 63.245.213.88 & 63.245.213.89. Would like some QA eyes on this. Possible to target Tuesday (10/20) or Thursday (10/21)?
Reporter | ||
Updated•15 years ago
|
Assignee: server-ops → mrz
Flags: needs-downtime+
Whiteboard: [tracking] [10/20/2009?]
Reporter | ||
Comment 1•15 years ago
|
||
And staged @ 180.92.184.28 in Singapore for those in that region.
Comment 2•15 years ago
|
||
(In reply to comment #1) > And staged @ 180.92.184.28 in Singapore for those in that region. Works fine. I clicked around a bit, searches etc seem to fine :)
Comment 3•15 years ago
|
||
mrz, Thursday would be better for me, if that's still doable.
Assignee | ||
Comment 4•15 years ago
|
||
mrz, the GLB is ready for sumo, with HTTP and HTTPS checks on the 3 datacenters.
Comment 5•15 years ago
|
||
I've been getting somewhat frequent "Service Unavailable" when on 63.245.213.89; can you guys check that host? It could also be that it's with the load balancer, and I just gut unlucky -- I'll keep looking off and on tonight.
Reporter | ||
Updated•15 years ago
|
Whiteboard: [tracking] [10/20/2009?] → 10/20/2009
Reporter | ||
Updated•15 years ago
|
Whiteboard: 10/20/2009 → 10/22/2009
Reporter | ||
Updated•15 years ago
|
Whiteboard: 10/22/2009 → 10/22/2009 @ 9pm
Comment 6•15 years ago
|
||
As a side note, this won't impact metrics, as we collect data from db and not log parsing
Reporter | ||
Comment 7•15 years ago
|
||
daniel, does this mean we're okay to do this tonight from your end?
Reporter | ||
Comment 8•15 years ago
|
||
Pushing to Thursday. Was unaware of support.mozilla.com's MX RRs. Over to justdave for postfix massaging.
Assignee: mrz → justdave
Comment 10•15 years ago
|
||
I reverted the DNS changes, looks like we screwed outgoing mail, too (see bug 523533)
Comment 11•15 years ago
|
||
The correct fix: 1) remove all records for support.mozilla.com from the mozilla.com zone. 2) add NS records for support.mozilla.com in the mozilla.com zone pointing at the glb.mozilla.net NS servers 3) tell the GLB servers to handle the entire support.mozilla.com zone 4) set up SOA and MX records in the support.mozilla.com zone on the GLB servers
Reporter | ||
Comment 12•15 years ago
|
||
(In reply to comment #11) > The correct fix: > > 1) remove all records for support.mozilla.com from the mozilla.com zone. > 2) add NS records for support.mozilla.com in the mozilla.com zone pointing at > the glb.mozilla.net NS servers > 3) tell the GLB servers to handle the entire support.mozilla.com zone > 4) set up SOA and MX records in the support.mozilla.com zone on the GLB servers This got more complicated. Over to Arzhel to stage.
Assignee: mrz → ayounsi
Comment 13•15 years ago
|
||
This got pushed about 40 minutes ago, DNS Trace looks good. http://pastebin.mozilla.org/678392
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Updated•9 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
•