This task will outline where the new es2011-2019 systems (ordered on T118174) should be racked and setup.
Our ES systems work in service groups of 3 systems per cluster, and three clusters to deploy with our new order. These new systems will replace the use of the current es2001-2010, which we will decommission afterwards. (The old ES systems are all out of warranty R510s.) No single service cluster should be in less than two rows. Since we have 4 rows to work with, we'll put once system per service group per row. The current deployment of ES systems is only in rows A and B, we'll re-balance this going forward.
This plan leaves the a6/b6 racks for population last, and they likely won't have room until after the existing es2002, es2004, es2006, and es2009 are removed from those racks. IRC conversation with @jcrespo notes that we don't have to have all 9 new systems racked immediately, we can rack a service group, transfer data from the older es systems, and then decommission those older es systems once the data is migrated to the new es system service group. As such, the racking of any systems into full racks should pause until the ES systems in those racks are removed. (This will require some juggling with Jaime on what to rack first in those cases.)
- - rack and update racktables
- - add mgmt dns entries (both asset tag and hostname)
- - setup and test bios/ilom/redirection
- - setup raid10 of disks in hardware raid
- - switch ports setup (description/enable/vlan)
- - add production dns entries (internal vlan)
- - update install_server module for system (dhcp and netboot entries) standard db partitioning
- - install OS - jessie
- - sign/accept puppet/salt keys
Once you have the network port info on the task, feel free to ping @RobH in IRC to get the switch ports setup quickly.