Page MenuHomePhabricator

eqiad: 1 hardware access request for labs on real hardware
Closed, DeclinedPublic

Description

Labs Project Tested: not applicable
Site/Location: eqiad
Number of systems: 1
Service: labs on real hardware
Networking Requirements: in labs vlan

Dell PowerEdge R420, Dual Intel Xeon E5-2440, 32GB Memory, Dual 300GB SSD, Dual 500GB Nearline SAS or Dell PowerEdge R420, single Intel Xeon E5-2450 v2 2.50GHz, 16GB Memory, (2) 500GB Disks

For testing T95185

Event Timeline

yuvipanda raised the priority of this task from to Needs Triage.
yuvipanda updated the task description. (Show Details)
yuvipanda subscribed.
RobH added subscribers: mark, RobH.

We have 5 of the Dell PowerEdge R420, single Intel Xeon E5-2450 v2 2.50GHz, 16GB Memory, (2) 500GB Disks and 2 of the PowerEdge R420, Dual Intel Xeon E5-2440, 32GB Memory, Dual 300GB SSD, Dual 500GB Nearline SAS.

However, as this is a temp test with a possible transition into permanent use, this needs to be reviewed by @mark as well.

If approved, we can allocate one of the 5 easily, or one of the 2 with SSDs. Is there a pressing need for these to use the SSD misc systems?

Assigning to Mark for his input, questions, etc...

So this is just to -test- (temporarily) bare metal hardware in Labs, and will be returned to the spare pool? Anything works, but I'd default to the weakest specs then, no?

I have someone in mind (halfak / restoring) who will be requesting this once we have this stable, and hence was requesting hardware that might be suitable for those workloads so we can avoid more movement later on :) but sure, if you want us to try this first with other weaker options, that's fine too

Dell PowerEdge R310, Single Intel Xeon X3450, 8GB Memory (2) 500GB 3.5 SATA seems to be the 'weakest' I could find on a quick glance

I approve using any hardware we have for the purpose of getting bare metal hw in Labs working, provided it's not in the way of other hw allocations.

RobH removed RobH as the assignee of this task.Jul 30 2015, 9:44 PM

So immediately after this was last updated Mark & Yuvi were chatting in IRC with others about the scope of this project and the network requirements.

Are we still good to allocate hardware, or does this first need more work on the network planning side?

yuvipanda changed the task status from Open to Stalled.Jul 30 2015, 10:07 PM

After IRC discussions this requires networking expertise we do not have availability of atm, so stalling for now.

Could you elaborate what is it that you need? I don't see it being very networking-intensive as a task, so I think we might able to fit it in, but I may be missing something :)

@yuvipanda: can you describe network expertise you need?

So, the ultimate goal is to have:

  1. Real hardware that we can give arbitrary people root to...
  2. which is in the same network as labs instances, so it can access other labs instances but not access labvirt*, labcontrol*, labnet*** hosts

One possible way to do this is to use https://wiki.openstack.org/wiki/Meetings/Ironic but I was hoping / wondering if there was simpler networking magic that can get us this - https://phabricator.wikimedia.org/T95185#1476228 should get us most of the rest...

Is this blocked by the deployment of T114435 in terms of labs testing on bare metal, or does this still require a bare metal server allocated in eqiad for this now?

yuvipanda claimed this task.

Actually closing and opening a new ticket since it's for a different purpose