labnodepool1002 is no longer needed for use in that role, but was purchased back in 2017. Recently, we allocated 2 new spare pool machines for cloud team use as cloudservices100[34]. Since this server will also work, and is already allocated to the cloud team for use, we're just going to rename it to cloudservices1003.

This will free up a previously approved allocation of a brand new spare system from T199727.

Since this is decommissioning the hostname of one host and reusing the system, this is a combined (custom) checlist for use:

cloudservices1003:

• - set all icinga checks for labnodepool1002 to maint mode/disabled
• - remove ALL references to labnodepool1002 in operations/puppet repo
• - shutdown the labnodepool1002 OS/server
• - puppet node clean/deactivate labnodepool1002 on puppetmaster (this clears out monitoring of the old hostname)
• - remove dbmonitor entries on neodymium/sarin: sudo curl -X DELETE https://debmonitor.discovery.wmnet/hosts/${HOST_FQDN} --cert /etc/debmonitor/ssl/cert.pem --key /etc/debmonitor/ssl/server.key
• - change mgmt dns entries from labnodepool1002 to cloduservices1003 in mgmt DNS
• - remove/update/change labnodepool1002 to cloudservices1003 in production DNS
• - hostname entry in racktables changed from labnodepool1002 to cloudservices1003
• - physical hostname label changed from labnodepool1002 to cloudservices1003 - ONLY ONSITE CAN DO THIS
• - physical label field in racktables changed from labnodepool1002 to cloudservices1003 (only after actual physical label step above is done) - ONLY ONSITE SHOULD DO THIS
• - bios/drac/serial setup/testing, firmware updates. this should be done before OS reimage while system is offline.
• - mgmt dns entries updated for hostname from labnodepool1002 to cloudservices1003
• - network port setup (description, enable, vlan) and update description from labnodepool1002 to cloudservices1003 and change to public vlan
• - production dns entries added (remove old entries for labnodepool1002)
• - operations/puppet update (install_server at minimum, other files if possible)
• - OS installation
• - puppet accept/initial run
• - handoff for service implementation