Bug 591651

Summary:	[RFE] add attribute that describes a systems as production or pre-production
Product:	[Retired] Beaker	Reporter:	Cameron Meadors <cmeadors>
Component:	inventory	Assignee:	Bill Peck <bpeck>
Status:	CLOSED NOTABUG	QA Contact:
Severity:	medium	Docs Contact:
Priority:	low
Version:	0.5	CC:	bpeck, dcallagh, kbaker, mcsontos, rmancy
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-09-28 00:34:58 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Cameron Meadors 2010-05-12 19:24:23 UTC

There are many systems in rhts that are pre-production (engineering samples) that were added because at the time there was no released hardware and we needed to run automated tests.  We are running into situations where the engineering samples don't always install (because they are beta quality at best).  Also we don't want to be testing on pre-production hardware unless we are doing hardware enablement testing.

I suggest that there should be a way to describe a systems as pre-production (engineering sample/beta quality) or production (released/supported) hardware.  Then testers can decide what if it is ok to test on pre-production hardware or not.

Comment 1 Dan Callaghan 2011-02-02 04:04:00 UTC

Is this solved by having "Machine" vs. "Prototype" in the "type" field for a system?

Comment 2 Dan Callaghan 2012-09-28 00:34:58 UTC

Assuming this is solved by using "Prototype" for the system type.