Bug 683146 - [RFE] allow scheduling against system.devices, also support alias
Summary: [RFE] allow scheduling against system.devices, also support alias
Keywords:
Status: CLOSED DUPLICATE of bug 784026
Alias: None
Product: Beaker
Classification: Retired
Component: scheduler
Version: 0.6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified vote
Target Milestone: ---
Assignee: Bill Peck
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-08 16:58 UTC by Bill Peck
Modified: 2014-08-12 04:33 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-04-27 18:31:47 UTC

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

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 ***
Note You need to log in before you can comment on or make changes to this bug.