This task will track the receiving, racking, and setup of two new systems, notebook100[34]. These will replace noteboot100[12], which are slated for decommission after the new systems come online (unless Analytics states otherwise, but their request stated this was a refresh/swap not expansion.)
Racking Proposal: These two systems should be in different rows. They can be in ANY of the 4 rows, as they will use the analytics vlan, which is also deployed across all 4 rows. notebook100[12] are currently in rows C and A, but will be replaced by these two systems, so do not need to be taken into consideration. Suggest placing in the rows with the most space.
notebook1003:
[] - receive in system on #procurement task T175603
[] - rack system with proposed racking plan (see above) & update racktables (include all system info plus location)
[] - bios/drac/serial setup/testing
[] - mgmt dns entries added for both asset tag and hostname
[] - network port setup (description, enable, vlan analytics)
** end on-site specific steps
[] - production dns entries added (analytics subnet)
[] - operations/puppet update (install_server at minimum, other files if possible)
[] - OS installation (Jessie)
[] - puppet accept/initial run
[] - handoff for service implementation (to @elukey or @Ottomata)
notebook1004:
[] - receive in system on #procurement task T175603
[] - rack system with proposed racking plan (see above) & update racktables (include all system info plus location)
[] - bios/drac/serial setup/testing
[] - mgmt dns entries added for both asset tag and hostname
[] - network port setup (description, enable, vlan analytics)
** end on-site specific steps
[] - production dns entries added (analytics subnet)
[] - operations/puppet update (install_server at minimum, other files if possible)
[] - OS installation (Jessie)
[] - puppet accept/initial run
[] - handoff for service implementation (to @elukey or @Ottomata)