Bug 683146

Summary:	[RFE] allow scheduling against system.devices, also support alias
Product:	[Retired] Beaker	Reporter:	Bill Peck <bpeck>
Component:	scheduler	Assignee:	Bill Peck <bpeck>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	0.6	CC:	bpeck, dcallagh, jburke, mcsontos, rmancy, rousseau, stl
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-04-27 18:31:47 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Bill Peck 2011-03-08 16:58:25 UTC

Description of problem:

Currently we can't schedule against the hardware details in beaker.  This request is to add support for the following xml:

<hostRequires>
 <device attribute="" op="=" value=""/>
</hostRequires>

attributes:
 vendorid
 deviceid
 subsysvendorid
 subsysdeviceid
 description
 type
 bus
 driver
 alias 

This also requires adding alias to device table and allow admin to edit that field.

Should allow admin to delete and add the device record to systems as well.  Even though re-running inventory on the two machines would do the same thing.

Comment 1 Dan Callaghan 2011-03-08 23:59:17 UTC

Maybe we should use an element <device/>. If I am looking for a system with an Intel NIC, then I could say

<hostRequires>
  <device>
    <vendorid op="=" value="8086" />
    <type op="=" value="NETWORK" />
  </device>
</hostRequires>

which would match any systems having some device with that vendor id and type, as opposed to:

<hostRequires>
  <device>
    <vendorid op="=" value="8086" />
  </device>
  <device>
    <type op="=" value="NETWORK" />
  </device>
</hostRequires>

which would match any systems having a device with that type and a device with that vendor id -- probably not what I want, since it would also match a system with an Intel audio device and some other brand NIC.

Comment 2 Bill Peck 2011-03-09 14:16:33 UTC

Makes sense.

Comment 3 Bill Peck 2012-04-27 18:31:47 UTC


*** This bug has been marked as a duplicate of bug 784026 ***