Closed Bug 757196 Opened 13 years ago Closed 13 years ago

Need network flow from builder1.ateam.phx1.mozilla.com to stage.mozilla.org

Categories

(Infrastructure & Operations Graveyard :: NetOps: DC ACL Request, task)

Product:
Infrastructure & Operations Graveyard
Component:
NetOps: DC ACL Request
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: jgriffin, Assigned: cransom)

References

Details

Need network flow from builder1.ateam.phx1.mozilla.com to releases.mozilla.com, TCP, port 22 (for scp access).
releases.mozilla.com is a load balancer in front of ftp[1|2].dmz.scl3.mozilla.com So we can either open port 22 on the public facing site, allow flows to the backend nodes or stick with ftp/https.
Perhaps allowing the ssh flow to the backend nodes would be best.
My mistake, uploads to releases.mozilla.com get uploaded to stage.mozilla.org. So, the flow needed is from builder1.ateam.phx1.mozilla.com to stage.mozilla.org, TCP, port 22 (for scp access).
Summary: Need network flow from builder1.ateam.phx1.mozilla.com to releases.mozilla.com → Need network flow from builder1.ateam.phx1.mozilla.com to stage.mozilla.org
Assignee: network-operations → cransom
[cransom@builder1.ateam.phx1 ~]$ nc -vz stage.mozilla.org 22 Connection to stage.mozilla.org 22 port [tcp/ssh] succeeded!
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Product: mozilla.org → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.