This task will track the receiving, setup, and installation of two new labnet servers, labnet1003 and labnet1004, ordered on T163822.
Racking Proposal: These have to be in the labs-hosts subnet to be with the other labs hosts, similar to where labnet1001 and labnet1002 are racked. Both of those older systems are out of warranty, and my understanding is these two systems will replace them. The old ones will have to stay online until these have completed service implementation. So rack in any free space/power/network 1Gbps rack.
We may want to have someone in cloud services confirm that these MUST be in the row B, sharing the vlan/subnet with the virt hosts. I imagine it does, but if it doesn't, we should spread these to other rows.
labnet1003:
[] - receive in system on T163822
[] - 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
[] - production dns entries added (labs-hosts1-b-eqiad subnet)
[] - network port setup (description, enable, labs-hosts1-b-eqiad vlan)
[] - operations/puppet update (install_server at minimum, other files if possible)
[] - OS installation
[] - puppet/salt accept/initial run
[] - handoff for service implementation
labnet1004:
[] - receive in system on T163822
[] - 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
[] - production dns entries added (labs-hosts1-b-eqiad subnet)
[] - network port setup (description, enable, labs-hosts1-b-eqiad vlan)
[] - operations/puppet update (install_server at minimum, other files if possible)
[] - OS installation
[] - puppet/salt accept/initial run
[] - handoff for service implementation