588782 - Move cm-bbot-xp-{001,002,003} to community network

Status: RESOLVED FIXED

(mozilla.org Graveyard :: Server Operations, task)

Description

[Chris AtLee [:catlee]]

Will need static networking information.

I'll also need RDP access to these machines, similar to how ssh access works in bug 575984 (only accessible from internal IPs).

Comment 1

[Justin Dow [:jabba]]

Derek, I'll need IPs for these as well as switch ports moved to the community network. Once that is done, assign to me and I can go to the colo to set the static IPs on them.

Comment 2

[Derek Moore [:dmoore]]

For the record, we're starting to get tight on community build IP address space. After this, there are about 7 usable address left. If we intend to continue growing in this manner, we'll have to discuss a migration of the community build network.

cm-bbot-xp-001 63.245.210.52
cm-bbot-xp-002 63.245.210.53
cm-bbot-xp-003 63.245.210.54


gateway: 63.245.210.1
netmask: 255.255.255.192

Comment 3

[Justin Dow [:jabba]]

These three are online now. We are updating DNS so that they are resolvable. RDP is accessible from internal machines.

Comment 4

[Chris AtLee [:catlee]]

(In reply to comment #2)
> For the record, we're starting to get tight on community build IP address
> space. After this, there are about 7 usable address left. If we intend to
> continue growing in this manner, we'll have to discuss a migration of the
> community build network.

All of these community buildbot slaves can be behind a NAT.  There's no need for them to have public IPs.

Comment 5

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

For my reference:

Connect to these systems with RDP - they do not run VNC.  Do so via the MPT VPN, with an extra route added for their subnet.

Each has three console windows open: one running buildslave, one at the prompt, and one running as admin.  Do installs of new packages as admin - use easy_install <whatever> in that console.