Bug 1081390

Summary:	[RFE] Provide predefined host filters
Product:	[Retired] Beaker	Reporter:	Nick Coghlan <ncoghlan>
Component:	command line	Assignee:	Amit Saha <asaha>
Status:	CLOSED CURRENTRELEASE	QA Contact:	tools-bugs <tools-bugs>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	develop	CC:	aigao, asaha, azelinka, dcallagh, ebaak, psplicha, rmancy, xma
Target Milestone:	0.18	Keywords:	FutureFeature
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-09-04 05:41:18 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Nick Coghlan 2014-03-27 07:42:36 UTC

Currently, Beaker's powerful hardware filtering capabilities are difficult to learn to use effectively. While improving the documentation is highly desirable in the long run, there's a simpler near term solution: provide support for predefined host filters in the command line interface, and ship a useful set of predefined filters.

This serves two purposes: the filters should be useful in their own right, and they also serve as examples for anyone wanting to create their own filters.

Comment 2 Nick Coghlan 2014-06-25 04:43:00 UTC

Bumping the priority on this, as I think the richness of the Beaker hardware inventory feature is difficult for folks that haven't already *used* Beaker to grasp, yet it is also its single most salient feature when distinguishing it not only from generic virtual-only software testing systems, but also from services like MAAS and OnMetal that only offer very rudimentary hardware filtering capabilities.

Adding this feature will thus serve a few purposes:

- drastically lower the barrier to entry to making use of the hardware filtering capabilities by letting experienced Beaker users maintain the list of predefined filters, while new users just need to be able to look up the filter's names

- provide example queries that make it easier to learn what hardware filtering options are available

- make the richness of Beaker's hardware filtering capabilities obvious just by looking at the list of filters that are available (for ease of maintenance, this list could initially just be a literal inclusion of the filter definition file in the documentation - in future, a prettier table could be automatically generated for the docs from the filter definitions)

Comment 3 Nick Coghlan 2014-06-25 05:52:41 UTC

Proposing for 0.18 - will review that proposal in the next sprint planning meeting.

Comment 4 Amit Saha 2014-07-01 01:37:25 UTC

http://gerrit.beaker-project.org/#/c/3176/

Comment 5 Amit Saha 2014-07-04 05:00:28 UTC

Forgot something: http://gerrit.beaker-project.org/#/c/3182/1

Comment 10 Amit Saha 2014-07-08 03:36:24 UTC

As per comment 9.

Comment 12 Dan Callaghan 2014-09-04 05:41:18 UTC

Beaker 0.18.0 has been released.