Page MenuHomePhabricator

rack/setup/install pc2007-pc2010
Closed, ResolvedPublic

Description

This task will track the racking and setup of the 4 hosts pc2007, pc2008, pc2009, pc2010, purchased on {T195878}.

Racking Plan: We don't care about the racks, but just let's make sure they all go to different rows.
Important: These hosts need RAID 5

pc2007:

  • - receive in system on procurement task T195878
  • - rack system with proposed racking plan (see above) & update netbox (include all system info plus location)
  • - bios/drac/serial setup/testing
  • - RAID 5
  • - mgmt dns entries added for both asset tag and hostname
  • - network port setup (description, enable, private vlan vlan)
    • end on-site specific steps
  • - production dns entries added (private subnet)
  • - operations/puppet update (install_server at minimum, other files if possible)
  • - OS installation (stretch)
  • - puppet accept/initial run
  • - handoff for service implementation T208383

pc2008:

  • - receive in system on procurement task T195878
  • - rack system with proposed racking plan (see above) & update netbox (include all system info plus location)
  • - bios/drac/serial setup/testing
  • - RAID 5
  • - mgmt dns entries added for both asset tag and hostname
  • - network port setup (description, enable, private vlan vlan)
    • end on-site specific steps
  • - production dns entries added (private subnet)
  • - operations/puppet update (install_server at minimum, other files if possible)
  • - OS installation (stretch)
  • - puppet accept/initial run
  • - handoff for service implementation T208383

pc2009:

  • - receive in system on procurement task T195878
  • - rack system with proposed racking plan (see above) & update netbox (include all system info plus location)
  • - bios/drac/serial setup/testing
  • - RAID 5
  • - mgmt dns entries added for both asset tag and hostname
  • - network port setup (description, enable, private vlan vlan)
    • end on-site specific steps
  • - production dns entries added (private subnet)
  • - operations/puppet update (install_server at minimum, other files if possible)
  • - OS installation (stretch)
  • - puppet accept/initial run
  • - handoff for service implementation T208383

pc2010:

  • - receive in system on procurement task T195878
  • - rack system with proposed racking plan (see above) & update netbox (include all system info plus location)
  • - bios/drac/serial setup/testing
  • - RAID 5
  • - mgmt dns entries added for both asset tag and hostname
  • - network port setup (description, enable, private vlan vlan)
    • end on-site specific steps
  • - production dns entries added (private subnet)
  • - operations/puppet update (install_server at minimum, other files if possible)
  • - OS installation (stretch)
  • - puppet accept/initial run
  • - handoff for service implementation T208383

Event Timeline

Restricted Application added a subscriber: Aklapper. · View Herald Transcript
Marostegui moved this task from Triage to Blocked external/Not db team on the DBA board.
Marostegui added a subtask: Unknown Object (Task).

Change 468221 had a related patch set uploaded (by Marostegui; owner: Marostegui):
[operations/puppet@production] install_server: Allow install the new pc hosts

https://gerrit.wikimedia.org/r/468221

Change 468221 merged by Marostegui:
[operations/puppet@production] install_server: Allow install the new pc hosts

https://gerrit.wikimedia.org/r/468221

Papaul closed subtask Unknown Object (Task) as Resolved.Oct 29 2018, 3:44 PM

@Papaul: @Banyek will be your contact point as he will be the person in charge of the related goal while Manuel is out.

Change 470674 had a related patch set uploaded (by Papaul; owner: Papaul):
[operations/dns@master] DNS: ADD production and mgmt DNS entries for pc200[7-9] and pc2010

https://gerrit.wikimedia.org/r/470674

Change 470674 merged by Dzahn:
[operations/dns@master] DNS: ADD production and mgmt DNS entries for pc200[7-9] and pc2010

https://gerrit.wikimedia.org/r/470674

[authdns1001:~] $ host pc2007.codfw.wmnet
pc2007.codfw.wmnet has address 10.192.0.104

[authdns1001:~] $ host pc2008.codfw.wmnet
pc2008.codfw.wmnet has address 10.192.16.35

[authdns1001:~] $ host pc2009.codfw.wmnet
pc2009.codfw.wmnet has address 10.192.32.10

[authdns1001:~] $ host pc2010.codfw.wmnet
pc2010.codfw.wmnet has address 10.192.48.14

[authdns1001:~] $ host 10.192.0.104
104.0.192.10.in-addr.arpa domain name pointer pc2007.codfw.wmnet.

[authdns1001:~] $ host 10.192.16.35
35.16.192.10.in-addr.arpa domain name pointer pc2008.codfw.wmnet.

[authdns1001:~] $ host 10.192.32.10
10.32.192.10.in-addr.arpa domain name pointer pc2009.codfw.wmnet.

[authdns1001:~] $ host 10.192.48.14
14.48.192.10.in-addr.arpa domain name pointer pc2010.codfw.wmnet.


[authdns1001:~] $ host pc2007.mgmt.codfw.wmnet
pc2007.mgmt.codfw.wmnet has address 10.193.1.208

[authdns1001:~] $ host pc2008.mgmt.codfw.wmnet
pc2008.mgmt.codfw.wmnet has address 10.193.1.209

[authdns1001:~] $ host pc2009.mgmt.codfw.wmnet
pc2009.mgmt.codfw.wmnet has address 10.193.1.210

[authdns1001:~] $ host pc2010.mgmt.codfw.wmnet
pc2010.mgmt.codfw.wmnet has address 10.193.1.211

[authdns1001:~] $ host 10.193.1.208
208.1.193.10.in-addr.arpa domain name pointer pc2007.mgmt.codfw.wmnet.
208.1.193.10.in-addr.arpa domain name pointer wmf6659.mgmt.codfw.wmnet.

[authdns1001:~] $ host 10.193.1.209
209.1.193.10.in-addr.arpa domain name pointer wmf6660.mgmt.codfw.wmnet.
209.1.193.10.in-addr.arpa domain name pointer pc2008.mgmt.codfw.wmnet.

[authdns1001:~] $ host 10.193.1.210
210.1.193.10.in-addr.arpa domain name pointer pc2009.mgmt.codfw.wmnet.
210.1.193.10.in-addr.arpa domain name pointer wmf6661.mgmt.codfw.wmnet.

[authdns1001:~] $ host 10.193.1.211
211.1.193.10.in-addr.arpa domain name pointer pc2010.mgmt.codfw.wmnet.
211.1.193.10.in-addr.arpa domain name pointer wmf6662.mgmt.codfw.wmnet.

Change 470716 had a related patch set uploaded (by Papaul; owner: Papaul):
[operations/puppet@production] DHCP: Add MAC address entries for pc200[7-9] and pc2010

https://gerrit.wikimedia.org/r/470716

Change 470716 merged by Dzahn:
[operations/puppet@production] DHCP: Add MAC address entries for pc200[7-9] and pc2010

https://gerrit.wikimedia.org/r/470716

pc2007

root@pc2007:~# fdisk -l
Disk /dev/sda: 4.4 TiB, 4799217008640 bytes, 9373470720 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: F98D3408-A164-4FB3-BC1F-33DCD4F5F6F4

Device        Start        End    Sectors  Size Type
/dev/sda1      2048   78125055   78123008 37.3G Linux filesystem
/dev/sda2  78125056   93749247   15624192  7.5G Linux swap
/dev/sda3  93749248 9373468671 9279719424  4.3T Linux LVM


Disk /dev/mapper/tank-data: 4.3 TiB, 4751215296512 bytes, 9279717376 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

pc2008

root@pc2008:~# fdisk -l
Disk /dev/sda: 4.4 TiB, 4799217008640 bytes, 9373470720 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 1224A82A-AFDB-4EA2-B5DA-A5CA4BA5D3A8

Device        Start        End    Sectors  Size Type
/dev/sda1      2048   78125055   78123008 37.3G Linux filesystem
/dev/sda2  78125056   93749247   15624192  7.5G Linux swap
/dev/sda3  93749248 9373468671 9279719424  4.3T Linux LVM


Disk /dev/mapper/tank-data: 4.3 TiB, 4751215296512 bytes, 9279717376 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


pc2009

root@pc2009:~# fdisk -l
Disk /dev/sda: 4.4 TiB, 4799217008640 bytes, 9373470720 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: CA04E04D-4FE7-4B86-8E23-4F351FB7E2BF

Device        Start        End    Sectors  Size Type
/dev/sda1      2048   78125055   78123008 37.3G Linux filesystem
/dev/sda2  78125056   93749247   15624192  7.5G Linux swap
/dev/sda3  93749248 9373468671 9279719424  4.3T Linux LVM


Disk /dev/mapper/tank-data: 4.3 TiB, 4751215296512 bytes, 9279717376 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

pc2010

Disk /dev/sda: 4.4 TiB, 4799217008640 bytes, 9373470720 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: EC922D77-2FE8-4C51-AB85-F373EA3E64CC

Device        Start        End    Sectors  Size Type
/dev/sda1      2048   78125055   78123008 37.3G Linux filesystem
/dev/sda2  78125056   93749247   15624192  7.5G Linux swap
/dev/sda3  93749248 9373468671 9279719424  4.3T Linux LVM


Disk /dev/mapper/tank-data: 4.3 TiB, 4751215296512 bytes, 9279717376 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Papaul updated the task description. (Show Details)
Papaul subscribed.

@Banyek all yours

@Papaul as I checked the storage on the hosts it's set up for with stripe size of 512Kb instead of 256K (https://wikitech.wikimedia.org/wiki/Raid_and_MegaCli)
Could you change this?

Note: I'll be out for the rest of the week, so you don't have to hurry with that as I can resume only on Monday

A larger stripe size should not be a huge issue (unlike a smaller one, which affected performance significantly and we didn't like it). We were thinking of increasing the one we used due to increased capacity anyway, so this would be a nice test (these are 1.6TB disks anyway). Redoing the RAID and reformatting may take a long time and it may be a waste of time.

@Papaul please don't take any action at the moment with these hosts, but for future installations we would like to continue using 256K on regular RAID10 installations, if available, to prevent from introducing more variables (unless we decide to stick with double the strip size or there no option) https://wikitech.wikimedia.org/wiki/Raid_and_MegaCli

@Banyek please check if the performance of the disk is acceptable, considering we are in a RAID5 situation so it cannot be directly compared to a RAID10 host.

@jcrespo actually i can change the stripe size on one of the hosts, and do some comparison, what do you think about this?

If this is in testing mode , I think it needs to be assigned to DB.

Ah sorry we were talking about this off-phab: the stripe size will be good

I agree with Jaime, a bigger stripe size shouldn't be an issue. Plus, we will be having SSDs, which will probably compensate anyways.
Let's keep the stripe size to 256 for future hosts though, for consistency.
The implementation task is: T208383
Thanks @Papaul for getting this up and running for us!