Closed
Bug 725107
Opened 13 years ago
Closed 13 years ago
ACL request for orangefactor1.dmz.phx1.mozilla.com
Categories
(Infrastructure & Operations Graveyard :: NetOps: DC ACL Request, task)
Infrastructure & Operations Graveyard
NetOps: DC ACL Request
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jgriffin, Assigned: cransom)
Details
The VM at orangefactor1.dmz.phx1.mozilla.com needs to access the following machines:
pulse.mozilla.org:5672
buildbot-es.metrics.sjc1.mozilla.com:9200, which is a round-robin DNS pointing to:
elasticsearch1.metrics.sjc1.mozilla.com:9200
elasticsearch2.metrics.sjc1.mozilla.com:9200
elasticsearch3.metrics.sjc1.mozilla.com:9200
Assignee | ||
Updated•13 years ago
|
Status: NEW → ASSIGNED
Assignee | ||
Updated•13 years ago
|
Assignee: network-operations → cransom
Assignee | ||
Comment 1•13 years ago
|
||
The flows are set and tested, except for one proviso regarding pulse. Due to how the network is setup currently, orangefactor1 is unable to communicate directly with pulse on the external address because they are actually on the same subnet (.74) and the firewall is doing an address translation to give dp-pulse01 a public IP. In order to make pulse work, you'll need to add a hosts entry for pulse pointing to 10.8.74.40 to avoid the NAT.
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Updated•12 years ago
|
Product: mozilla.org → Infrastructure & Operations
Updated•3 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•