This task will track the receiving, racking, and setup of the two new kubernetes staging hosts ordered for eqiad on T163459.
Hostname proposal: There are already kubernetes1XXX systems in eqiad, as well as the conf1XXX systems running conftool for kubernetes. Staging and development are often done on the same box, would these be acceptable to call kubernetes-dev1XXX?
Racking proposal: Since none of these boxes currently exist in eqiad, the current suggestion is to place in two different racks/rows, but otherwise in any available 1Gbps network racks.
kubernetes-dev1001:
[x] - receive in system on #procurement task T163459
[x] - 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 (internal subnet)
[] - network port setup (description, enable, internal vlan)
[] - operations/puppet update (install_server at minimum, other files if possible)
[] - OS installation
[] - puppet/salt accept/initial run
[] - handoff for service implementation
kubernetes-dev1001:
[x] - receive in system on #procurement task T163459
[x] - 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 (internal subnet)
[] - network port setup (description, enable, internal vlan)
[] - operations/puppet update (install_server at minimum, other files if possible)
[] - OS installation
[] - puppet/salt accept/initial run
[] - handoff for service implementation