Closed Bug 767594 Opened 12 years ago Closed 12 years ago

ACL for MDN "Freddo" deployment system

Categories

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

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

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: nmaul, Assigned: arzhel)

References

(
URL
)

Details

We're attempting to set up the new MDN cluster in SCL3 to use Chief and Freddo for deployments. Chief is already done, but Freddo requires an extra ACL. The web node(s) for the 'dev' environment need to be able to access Redis on the admin node, to queue up deployment jobs.

src: developer1.dev.webapp.scl3.mozilla.com, any/tcp
dst: developeradm.private.scl3.mozilla.com, 6388/tcp

Note that only the dev environment (1 server presently) needs this... stage and prod use Chief instead (user-initiated updating vs automatic), which doesn't have this sort of dependency.

Thanks!
Done!
[root@developer1.dev.webapp.scl3 ~]# nc -zv developeradm.private.scl3.mozilla.com 6388
Connection to developeradm.private.scl3.mozilla.com 6388 port [tcp/*] succeeded!
Assignee: network-operations → arzhel
Status: NEW → RESOLVED
Closed: 12 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.