This task will track the racking, setup, and installation of the 10 new mw appservers for codfw. The task will have two parts, first determining where to rack the systems, and the second part will be implementation.

racking location determination / old system decom determination

There is an open question on where these will rack. Presently, rack A4 has a lot of space, since a large number of old appservers were decommissioned and removed from them last summer, and replaced with new systems in racks A3 and A4. A4 still has less sytems than A3, these could help balance that.

Additionally, the other mw racks in codfw include: B3, B4, C3, & C4. These racks are full of older mw systems. The 10 oldest mw systems in production use @ codfw are mw2075-mw2084. Half of these are in A4, the other half in B3. FYI: The codfw mw cluster is out of warranty up to host mw2134. hosts mw2135+ are still under warranty past January 2017 (or further.) So racks A4 (5), B3 (all out of warranty), B4 (2/3rds out of warranty) have some out of warranty hosts in them. Row c has only under warranty mw hosts.

Do we need to rack these 10 newly leased systems in different racks than the other newest hosts in A4? If not, continuing to fill it up will keep our racking of mw systems in codfw in sequence. This isn't a hard requirement, but it does help age out systems gracefully from the racks with ease. Unless these new systems must be located away from this summer's mw order, I'd (@RobH) suggest filling out A4.

We'll also need to decide how many older hosts to decommission. If we place these into A4, they have plenty of space in the rack so they'll go in the bottom of the rack, where no existing hosts are placed (since the decom of older hosts this summer.) If we want to place the hosts in rows B or C, we'll need to decom or move hosts around. We'll need to figure this out in advance of racking the hosts if we want the new hosts in B or C rows, if we want them in A4 or row D (no mw systems in row D yet) then we don't need to determine this before the new servers are racked.

Assigning this task to @Joe for his input on where to rack (if it matters) and what hosts to decom (if needed for racking.) Please detail/comment and assign back to @RobH, thanks!

implementation

• - receive in systems normally per parent task T151779
• - mgmt dns entries (asset tag + hostnames) and production dns (hostname, internal vlan)
• - rack according to determination made in part 1 "racking location determination" of this task.
• - bios/drac setup/testing
• - update or create sub task with network port info
• - install_module updates
• - install OS (jessie)
• - accept/sign puppet/salt
• - service implementation