1563333 - Create VMs for bsdpy service in Releng tier3 network

Status: RESOLVED FIXED

(Infrastructure & Operations :: Virtualization, task)

Description

[Jake Watkins [:dividehex]]

+++ This bug was initially created as a clone of Bug #1484017 +++

Please create 4 new VM in order to support the bsdpy service.

bsdpy1.tier3.releng.mdc1.mozilla.com
bsdpy2.tier3.releng.mdc1.mozilla.com
bsdpy1.tier3.releng.mdc2.mozilla.com
bsdpy2.tier3.releng.mdc2.mozilla.com

Essentially, the service will be serving small files over tftp and large netboot images over http. I think it is safe to start out conservatively on cpu and ram. There shouldn't be a need for much disk space since these should only host a few large image files (~4GB each) that don't change often.

1 cpu core
1G of ram
60GB of disk

Please set to pxe boot. I'll kickstart and puppetize them the 'releng way'.

Thanks!

ps. This is a recently created releng vlan/network in mdc1/2 so there might be extra setup eg. configuring the network and trunking in vsphere. See: https://bugzilla.mozilla.org/show_bug.cgi?id=1562289

Comment 1

[Chris Knowles [:cknowles]]

As you guessed, there's no vlan 260 in the UCS/ESX - and Netops will need to trunk things around for us. I've asked them to do that in bug 1562289.

I've also setup the UCS/ESX to be ready to roll when that vlan gets trunked in.

Chances are we'll also need to setup DNS/DHCP/PXE settings on the VLAN - so there'll be some testing time as well.

Comment 2

[Chris Knowles [:cknowles]]

As expected, DNS wasn't setup. (the IP range existed, but hadn't been configured) - is there a working PXE boot environment I can cheat^H^H^H^H^H learn from? (i.e one that you use and works the way you want this one to?

Comment 3

[Jake Watkins [:dividehex]]

(In reply to Chris Knowles [:cknowles] from comment #2)

As expected, DNS wasn't setup. (the IP range existed, but hadn't been configured) - is there a working PXE boot environment I can cheat^H^H^H^H^H learn from? (i.e one that you use and works the way you want this one to?

Thanks for noticing! I'd guess, anything that applies to the test.releng.mdc[1,2].m.c environments should be ok to crib off of. Releng has always utilized IT managed pxe environments in the datacenters. So the pxe bits in dhcp should point to the same IT admin hosts that support the other releng vlan/networks.

Comment 4

[Chris Knowles [:cknowles]]

OK, while some settings weren't in there right - apparently they've changed bootp/pxe values to inherit - so all releng vlans get the same settings by default. So test.releng.<DC> matches tier3.releng.<DC> as far as bootp/pxe match.

Now we're into thumb twiddling until the vlans get plumbed.

Comment 5

[Chris Knowles [:cknowles]]

And because I despise thumb twiddling. I created the VMs, Inventoried, DNS/DHCP setup, tracking sheets.

Verified that they won't get a DHCP address - so NOW we're really waiting on the plumbing piece.

Comment 6

[Chris Knowles [:cknowles]]

Alright - looks like netops resolved their plumbing issues. I've tested the VMs, and they pxe boot to the menu - I didn't want to take them further and get in your way.

So, you should be good to go - let me know if there are any problems.