Closed Bug 828006 Opened 13 years ago Closed 13 years ago

need buildvpn access for all vcs-sync hosts

Categories

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

task
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: hwine, Assigned: arzhel)

Details

(Whiteboard: [reit-ops])

there are four hosts currently being used for the vcs-sync tooling: Host VPN github-sync1-dev.dmz.scl3.mozilla.com mpt-vpn github-sync1.dmz.scl3.mozilla.com mpt-vpn github-sync2.dmz.scl3.mozilla.com mpt-vpn github-sync3.dmz.scl3.mozilla.com build-vpn Only the last is accessible via SSH from the build-vpn. As more team members are trouble shooting this tooling, the inconsistancy of access is causing confusion late at night with upset customers. To be clear, only ssh (port tcp/22) access is needed.
Oops - wrong component
Assignee: nobody → server-ops-devservices
Component: Release Engineering: Developer Tools → Server Operations: Developer Services
QA Contact: hwine → shyam
Over to netops for network plumbings.
Assignee: server-ops-devservices → network-operations
Component: Server Operations: Developer Services → Server Operations: Netops
QA Contact: shyam → ravi
Component: Server Operations: Netops → Server Operations: ACL Request
[xionox@vpn1.dmz.releng.scl3 ~]$ nc -zv github-sync1-dev.dmz.scl3.mozilla.com 22 Connection to github-sync1-dev.dmz.scl3.mozilla.com 22 port [tcp/ssh] succeeded! [xionox@vpn1.dmz.releng.scl3 ~]$ nc -zv github-sync1.dmz.scl3.mozilla.com 22 Connection to github-sync1.dmz.scl3.mozilla.com 22 port [tcp/ssh] succeeded! [xionox@vpn1.dmz.releng.scl3 ~]$ nc -zv github-sync2.dmz.scl3.mozilla.com 22 Connection to github-sync2.dmz.scl3.mozilla.com 22 port [tcp/ssh] succeeded! [xionox@vpn1.dmz.releng.scl3 ~]$ nc -zv github-sync3.dmz.scl3.mozilla.com 22 Connection to github-sync3.dmz.scl3.mozilla.com 22 port [tcp/ssh] succeeded!
Assignee: network-operations → arzhel
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Thanks!
Status: RESOLVED → VERIFIED
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.