Device Type Attributes

Registered by Andy Doan on 2012-09-06

NOTE: These are rough notes from a discussion I had that I don't want to loose

We are starting to find ourselves dealing with some naming-scheme stuff with LAVA (ie panda/panda-es). things might work more smoothly if we added some new attributes to a DeviceType in the scheduler like:

* technology (optional) - qemu/fastmodel
* boardlayoutname - panda, beagle, etc
* maj socname - exynos4, exynoys5
* soc majrev - 4460 4430
* soc TO - rev 1, rev2 rev A, rev B

Then job submissions could cue off those things rather than just the readable name we currently use.

Blueprint information

Status:
Not started
Approver:
None
Priority:
Undefined
Drafter:
None
Direction:
Needs approval
Assignee:
None
Definition:
New
Series goal:
None
Implementation:
Unknown
Milestone target:
milestone icon backlog

Related branches

Sprints

Whiteboard

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.