Change Details

When we had issues with labsdb1002, I asked @Cmjohnson to install one of the latest new db1XXXX as labsdb1008 to help with the load. Now that we have labsdb1009/10/11 close to be installed, it is not needed anymore on labs-support. However, an extra db1XXX would now be now very useful as a temporary sanitarium alternative. When @Chasemp gives the ok (he is the current main user of labsdb1008 and probably still has data on it he wants to keep), starting from anytime next week, I would like to move labsdb1008 from labs-support to production. Any rack will work except D1. It is 1U, so I hope it could fit anywhere. == reinstallation checklist == [x] - mgmt dns update [x] - production dns update [x] - install_module update [x] - physical label update (sub-task created for async implementation) [] - reinstall OS [] - sign puppet/salt [] - service implementation handoff

When we had issues with labsdb1002, I asked @Cmjohnson to install one of the latest new db1XXXX as labsdb1008 to help with the load. Now that we have labsdb1009/10/11 close to be installed, it is not needed anymore on labs-support. However, an extra db1XXX would now be now very useful as a temporary sanitarium alternative. When @Chasemp gives the ok (he is the current main user of labsdb1008 and probably still has data on it he wants to keep), starting from anytime next week, I would like to move labsdb1008 from labs-support to production. Any rack will work except D1. It is 1U, so I hope it could fit anywhere. == reinstallation checklist == [x] - mgmt dns update [x] - production dns update [x] - install_module update [x] - physical label update (sub-task created for async implementation) [x] - reinstall OS [x] - sign puppet/salt [x] - service implementation handoff

When we had issues with labsdb1002, I asked @Cmjohnson to install one of the latest new db1XXXX as labsdb1008 to help with the load. Now that we have labsdb1009/10/11 close to be installed, it is not needed anymore on labs-support. However, an extra db1XXX would now be now very useful as a temporary sanitarium alternative. When @Chasemp gives the ok (he is the current main user of labsdb1008 and probably still has data on it he wants to keep), starting from anytime next week, I would like to move labsdb1008 from labs-support to production. Any rack will work except D1. It is 1U, so I hope it could fit anywhere. == reinstallation checklist == [x] - mgmt dns update [x] - production dns update [x] - install_module update [x] - physical label update (sub-task created for async implementation) [x] - reinstall OS [x] - sign puppet/salt [x] - service implementation handoff