Page MenuHomePhabricator

codfw: (2) hardware access request for labtest
Closed, ResolvedPublic

Description

Site/Location: CODFW
Number of systems: 2
Service: labtestmetal2001 and labtestservices2002
Networking Requirements: internal with 1 external
Processor Requirements: 12 cores
Memory: 64G
Disks: 1T after RAID1
NIC(s): 1G
Partitioning Scheme: RAID1
Other Requirements:
1 of these servers is external to replace the existing labtestservices1001

From the labs hardware budget for Q3 16-17

Related Objects

Event Timeline

chasemp changed the task status from Open to Stalled.Jan 5 2017, 2:39 PM
chasemp triaged this task as Medium priority.
RobH renamed this task from Site: (4) hardware access request for labtest to codfw: (4) hardware access request for labtest.Jan 5 2017, 5:25 PM

I've chatted with Chase about this via IRC. The one host to work as a labvirt/nova/neutron host will be for small VM testing, so it doesn't need to be a virt box, just a misc box. The CPU virtualization flag will need to be enabled on that particular host at time of racking. All of the systems come with 4 1Gbit network ports by default, which should cover the needed network ports for the virt testing host.

Chase will review and decide if we need to split that one special virt host off from this, and will get back to me. Then we'll start processing this request and getting quotes.

chasemp renamed this task from codfw: (4) hardware access request for labtest to codfw: (3) hardware access request for labtest.Jan 5 2017, 10:13 PM
chasemp updated the task description. (Show Details)
chasemp changed the task status from Stalled to Open.Feb 15 2017, 3:48 PM

I've chatted with Chase about this via IRC. The one host to work as a labvirt/nova/neutron host will be for small VM testing, so it doesn't need to be a virt box, just a misc box. The CPU virtualization flag will need to be enabled on that particular host at time of racking. All of the systems come with 4 1Gbit network ports by default, which should cover the needed network ports for the virt testing host.

Chase will review and decide if we need to split that one special virt host off from this, and will get back to me. Then we'll start processing this request and getting quotes.

I was convinced to split it out :) https://phabricator.wikimedia.org/T154706

Ok, this one is slightly confusing when taken in with all the other labs requests, so I had to put all of them in to a single spreadsheet with the CPU/memory/disk/nic requirements.

After doing that, the following tasks have some shared specifications and their shared requirements break down as follows:

While the specifications vary somewhat, the CPU model is the same thoughout (requires 12 cores per cpu between 2.0-2.6 GHz, whatever best priced), so they should all have the same CPU (just some have dual cpu, while specifcation 1 has single CPU).

Specification 1
Quantity: 5
1U system (R430 preferred)
Single CPU at 12 cores, somewhere between 2.0 and 2.6GHz (whatever the best/cheapest to meet this requirement.)
64 GB RAM
onboard 1Gbps NIC
4 * 1TB SFF SATA HDDs

Specification 2
Quantity: 2
1U system (R430 preferred)
Dual CPU at 12 cores, somewhere between 2.0 and 2.6GHz (whatever the best/cheapest to meet this requirement.)
64 GB RAM
onboard 1Gbps NIC
4 * 1TB SFF SATA HDDs

Specification 3
Quantity: 2
1U system (R430 preferred)
Dual CPU at 12 cores, somewhere between 2.0 and 2.6GHz (whatever the best/cheapest to meet this requirement.)
128 GB RAM
onboard 1Gbps NIC
4 * 1TB SFF SATA HDDs

Specification 4
Quantity: 2
1U system (R430 preferred)
Dual CPU at 12 cores, somewhere between 2.0 and 2.6GHz (whatever the best/cheapest to meet this requirement.)
128 GB RAM
onboard 1Gbps NIC
4 * 4TB SFF SATA HDDs

Since the spread of those systems is between codfw and eqiad, my plan is to get the quotes with the specifications and total quantities back from the first round of Dell pricing, and then create the procurement tasks split to the proper sites. The initial quote requests have been sent off, and I've moved all of the affected tasks from 'backlog' to 'in discussion' on the hardware-requests workboard.

RobH mentioned this in Unknown Object (Task).Apr 14 2017, 5:43 PM
RobH added a subtask: Unknown Object (Task).
RobH mentioned this in Unknown Object (Task).Apr 14 2017, 5:57 PM
RobH mentioned this in Unknown Object (Task).Apr 14 2017, 8:25 PM
RobH mentioned this in Unknown Object (Task).Apr 14 2017, 8:35 PM
RobH changed the status of subtask Unknown Object (Task) from Open to Stalled.Apr 25 2017, 7:44 PM

So one of these needs to adjust to 32GB of RAM.

RobH renamed this task from codfw: (3) hardware access request for labtest to codfw: (2) hardware access request for labtest.May 4 2017, 5:48 PM
RobH updated the task description. (Show Details)

These two hosts have been ordered and received in, and are being setup via T168891 and T168892.

faidon closed subtask Unknown Object (Task) as Resolved.Jul 12 2017, 7:30 AM