Closed Bug 1014748 Opened 10 years ago Closed 10 years ago

Allow mysql from bouncer?.webapp.scl3 to bouncer-ro-vip.db.scl3

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: gozer, Assigned: dcurado)

References

Details

Flow request so the new bouncer webheads in SCL3 can reach their database. bouncer[1-5].webapp.scl3 => bouncer-ro-vip.db.scl3 tcp/3306
Blocks: 1010453
Assignee: network-operations → dcurado
working on this
Status: NEW → ASSIGNED
OK, these flows should be in place. If there is any problem, please let me know? I'll fix it. Thanks -- Dave From zone: webapp, To zone: db Source addresses: bouncer5: 10.22.81.195/32 bouncer4: 10.22.81.194/32 bouncer3: 10.22.81.193/32 bouncer2: 10.22.81.192/32 bouncer1: 10.22.81.191/32 Destination addresses: backup1: 10.22.70.29/32 Application: mysql IP protocol: tcp, ALG: 0, Inactivity timeout: 1800 Source port range: [0-0] Destination port range: [3306-3306]
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
W00t. Thanks, Dave.
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.