This task will track the racking and setup of wdqs100[45].eqiad.wmnet.
Racking Proposal: These shouldn't be in any racks with existing wdqs systems (if possible), so do NOT place in a4 (wdqs1001). Place in any other 1GbE rack, since these use internal subnets. No two wdqs systems should share a rack, and try to put the three new ones in rows B, C, and D.
Please note that it is likely that d3 (wdqs1001), c7(wdqs1002) will be decommissioned after these are fully online. So if there isn't 1GbE rack space outside of D3 or c7, those two racks can be used. If there is space outside them, place these systems elsewhere to eliminate potential redundancy issues until the old ones are decommissioned.
wdqs1004:
[x] - receive in system on #procurement task T166780
[x] - rack system with proposed racking plan (see above) & update racktables (include all system info plus location)
[x] - bios/drac/serial setup/testing
[x] - mgmt dns entries added for both asset tag and hostname
[x] - network port setup (description, enable, internal vlan)
** end on-site specific steps
[x] - production dns entries added (internal vlan)
[] - operations/puppet update (install_server at minimum, other files if possible)
[] - OS installation
[] - puppet/salt accept/initial run
[] - handoff for service implementation
wdqs1005:
[x] - receive in system on #procurement task T166780
[x] - rack system with proposed racking plan (see above) & update racktables (include all system info plus location)
[x] - bios/drac/serial setup/testing
[x] - mgmt dns entries added for both asset tag and hostname
[x] - network port setup (description, enable, internal vlan)
** end on-site specific steps
[x] - production dns entries added (internal vlan)
[] - operations/puppet update (install_server at minimum, other files if possible)
[] - OS installation
[] - puppet/salt accept/initial run
[] - handoff for service implementation