We've had disk corruption on two Ciscos in the last month, and I'm losing my patience with them. It would be great to move all our instances over to new HP servers like virt1010-1012. Four of 'em would do the trick, five would give us some breathing room.
Description
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Resolved | RobH | T89752 eqiad: (6) labs virt nodes | |||
Restricted Task |
Event Timeline
Quotes are back in and escalated to @mark for approvals process on https://rt.wikimedia.org/Ticket/Display.html?id=9249
These are now in DC but not yet actually at eqiad.
I'm on clinic duty next week, but would like to start imaging them on the 13th. Thanks!
Andrew,
What naming convention do you want to use? Stick with labs10xx for now or start with something new? Also, do you want these in row D or are there any cisco's we can shed now?
CJ
According to the naming scheme in https://phabricator.wikimedia.org/T95042, let's name these boxes 'labvirt10xx'. You can start with 1001 and when I re-image the other HPs I'll rename them as well, later in the sequence.
I don't know what row they should go in. As long as they can be in the labs-private vlan, a different row from the other virt hosts would be great.
labvirt1001 wmf4669 u13/14 ge-3/0/8
labvirt1002 wmf4670 u15/16 ge-3/0/20
labvirt1003 wmf4671 u17/18 ge-3/0/21
labvirt1004 wmf4672 u33/34 ge-5/0/18
labvirt1005 wmf4673 u35/36 ge-5/0/19
labvirt1006 wmf4674 u37/38 ge-5/0/20