725504 - buildvpn migration from sjc1 to scl3?

Status: RESOLVED DUPLICATE of bug 735369

(Infrastructure & Operations :: Infrastructure: Other, task)

Description

[Amy Rich [:arr] [:arich]]

One of the pieces of infra that's in sjc1 is the buildvpn.  Just opening a bug to make sure there's a plan to migrate that before the hardware that it's on now is moved/destrolyed and to work out what the migration plan is (presumably client-side vpn configs will need to change at the very least)

Comment 1

[John O'Duinn [:joduinn] (please use "needinfo?" flag)]

does this need a treeclosure?

Comment 2

[Ravi Pina [:ravi]]

I believe this is the VPN for users to access the environment.  If so then I can't see why.  The two could coexist for a period until a time that Releng is ready to deprecate the host or the power is shut off to the host, whichever comes first.

Comment 3

[Dustin J. Mitchell [:dustin] (he/him)]

Ravi's correct, as amy had pointed out in IRC.

John, to be clear on terminology, the build VPN is how y'all access the build network.  The build *network* is where all the hosts sit, and that's not changing here.

Comment 4

[casey ransom [:casey]]

725504

Comment 5

[casey ransom [:casey]]

er. hi. I think this throws back to an irc conversation last week, but if i recall correctly, build vpn is going to be hosted on the admin1?.private.releng.scl3.  Is there needed from netops to close this?

Comment 6

[Amy Rich [:arr] [:arich]]

ccing jabba, since his group is setting this up (it was unclear what group would be working on this at the time I opened the bug).  jabba, if you don't need this bug, feel free to dupe/close.

Comment 7

[Amy Rich [:arr] [:arich]]

Work to set up the vpn was actually done in different bugs.