Closed Bug 619530 Opened 14 years ago Closed 14 years ago

please allow jimm to be part of the build-vpn

Categories

(Infrastructure & Operations Graveyard :: NetOps, task)

x86
Windows 7
task
Not set
major

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: mozilla, Assigned: phong)

References

Details

I'm not sure if he has MV-vpn; if not, he'll need a firewall port opened.
Is this mini located at the office?  If he is a mozilla employee, then he should already have access to MV-VPN.
Most minis (if not all) are in SCL.
This is neither MPT-VPN nor MV-VPN AFAICT.

He has to be able to reach that machine on the Build-VPN through VNC.
Jimm remembers setting up MV vpn at some point; I've pointed him at the VPN wiki page. I'll close this.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → INVALID
It's in scl1. I can get to it from the office, but Jim can't get to it when ssh tunneling into MV vpn.
Reopening.
Status: RESOLVED → REOPENED
Resolution: INVALID → ---
Assignee: server-ops → network-operations
Component: Server Operations → Server Operations: Netops
Bumping the priority.
Anyone can take this on?
Severity: normal → major
The route for SCL1 isn't pushed to the Mountain View VPN.  It shouldn't either - the whole build-vpn project's goal is to limit access to RelEng hosts to just the build-vpn host.

More easier to add him to the build-vpn for whatever duration he needs.
(In reply to comment #6)
> The route for SCL1 isn't pushed to the Mountain View VPN.  It shouldn't either
> - the whole build-vpn project's goal is to limit access to RelEng hosts to just
> the build-vpn host.
> 
> More easier to add him to the build-vpn for whatever duration he needs.

About a week or so. Maybe less. I'm investigating why shell tests run so slowly on these machines.
can someone from releng ack giving access to build-vpn?
Assignee: network-operations → phong
(In reply to comment #8)
> can someone from releng ack giving access to build-vpn?

ack. Once jimm is done with this experiment, we need to revoke this.

(working offline with zandr to confirm what is the "usual" process IT want to follow for "dev need access to build system" problems going forward)
added.
Status: REOPENED → RESOLVED
Closed: 14 years ago14 years ago
Resolution: --- → FIXED
(going forward we'll use an SSL VPN to handle things like this but we don't have it online yet)
Changing summary to match the actual action that took place.

I filed bug 622819 to revoke the access when his work is done.
I will pass it to ServOps once the work is done.
Summary: please allow jimm remote access to talos-r3-w7-003 via vnc → please allow jimm to be part of the build-vpn
(In reply to comment #11)
> (going forward we'll use an SSL VPN to handle things like this but we don't
> have it online yet)

Anywhere we can track the status of this?
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.