This task will cover the racking, setup, and installation of 4 new cloud-dev hosts purchased on T210781.
Hostname Proposal:
This should be confirmed by cloud-services-team!
T210781 states that the order for it covers: 1 x cloudcontrol2xxx-dev & 1-3 x cloudvirt2xxx-dev. There are NO cloudanything-dev in codfw at present, so these will have the following hostnames:
cloudcontrol2001-dev
cloudvirt2001-dev
cloudvirt2002-dev
cloudvirt2003-dev
Racking Proposal:
This should be confirmed by netops and/or cloud-services-team!
@RobH is making a number of assumptions here, and will need both netops and cloud-services-team to confirm things before @Papaul spends time racking the cloudvirt200[1-3]-dev hosts.
cloudcontrol2001-dev: cloudcontrol100[34] in eqiad are in the public vlan, since it appears they need to interact with both the cloudvirt hosts, and the rest of the world. So cloudcontrol2001-dev can be racked in any 1G rack in ANY row, since it will be placed in the public vlan. Don't rack in c1-codfw, since it has the system that will be counterpoint system.
cloudvirt200[1-3]-dev: cloudvirts have to be in a row that has both the cloud-hosts1 and cloud-instances[12] vlans for proper networking support. Row B in eqiad has those vlans on the switch and they are in use (while they aren't in use on other rows), so it seems row B is the row to put all cloudvirts on in codfw.
cloudcontrol2001-dev:
- - receive in system on procurement task T210781
- - rack system with proposed racking plan (see above) & update netbox (include all system info plus location) (B1)
- - bios/drac/serial setup/testing
- - mgmt dns entries added for both asset tag and hostname
- - network port setup (description, enable, vlan)
- end on-site specific steps
- - production dns entries added
- - operations/puppet update (install_server at minimum, other files if possible) (raid1.cfg)
- - OS installation
- - puppet accept/initial run
- - handoff for service implementation
cloudvirt2001-dev:
- - receive in system on procurement task T210781
- - rack system with proposed racking plan (see above) & update netbox (include all system info plus location) (B3)
- - please ensure BOTH 1G interfaces are hooked up. cloudvirts use the first interface for the OS/host and the second interface for instance traffic.
- - bios/drac/serial setup/testing
- - mgmt dns entries added for both asset tag and hostname
- - network port setup (description, enable, vlan)
- end on-site specific steps
- - production dns entries added
- - operations/puppet update (install_server at minimum, other files if possible) (raid1.cfg)
- - OS installation
- - puppet accept/initial run
- - handoff for service implementation
cloudvirt2002-dev:
- - receive in system on procurement task T210781
- - rack system with proposed racking plan (see above) & update netbox (include all system info plus location) (B5)
- - please ensure BOTH 1G interfaces are hooked up. cloudvirts use the first interface for the OS/host and the second interface for instance traffic.
- - bios/drac/serial setup/testing
- - mgmt dns entries added for both asset tag and hostname
- - network port setup (description, enable, vlan)
- end on-site specific steps
- - production dns entries added
- - operations/puppet update (install_server at minimum, other files if possible) (raid1.cfg)
- - OS installation
- - puppet accept/initial run
- - handoff for service implementation
cloudvirt2003-dev:
- - receive in system on procurement task T210781
- - rack system with proposed racking plan (see above) & update netbox (include all system info plus location) (B8)
- - please ensure BOTH 1G interfaces are hooked up. cloudvirts use the first interface for the OS/host and the second interface for instance traffic.
- - bios/drac/serial setup/testing
- - mgmt dns entries added for both asset tag and hostname
- - network port setup (description, enable, vlan)
- end on-site specific steps
- - production dns entries added
- - operations/puppet update (install_server at minimum, other files if possible) (raid1.cfg)
- - OS installation
- - puppet accept/initial run
- - handoff for service implementation
