Bug 977714

Summary:	[RFE] Configure default system settings for a lab controller
Product:	[Retired] Beaker	Reporter:	Nick Coghlan <ncoghlan>
Component:	inventory	Assignee:	beaker-dev-list
Status:	CLOSED WONTFIX	QA Contact:	tools-bugs <tools-bugs>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	0.12	CC:	cbouchar, qwan, tools-bugs
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-11-13 18:25:47 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 2013-06-25 08:03:06 UTC

Currently, if a couple of systems in a mostly private lab are accidentally added to the public pool, this can lead to jobs being queued for that lab instead of aborted automatically as having no available systems.

It may be useful to be able to configure certain system defaults on a per-lab basis, so they're set appropriately whenever a new system is added for that lab.

In particular:

- "Shared" status
- "Secret/NDA" status
- "Group" restrictions

Comment 1 Raymond Mancy 2013-06-25 23:28:03 UTC

(In reply to Nick Coghlan from comment #0)
> Currently, if a couple of systems in a mostly private lab are accidentally
> added to the public pool, this can lead to jobs being queued for that lab
> instead of aborted automatically as having no available systems.
> 

This seems to be a case of admins/system owners doing the wrong thing, not being aware of how they should configure their system for their particular use case. Education would hopefully mitigate most of the problem.

> It may be useful to be able to configure certain system defaults on a
> per-lab basis, so they're set appropriately whenever a new system is added
> for that lab.
> 
> In particular:
> 
> - "Shared" status
> - "Secret/NDA" status
> - "Group" restrictions

This will be tricky to do in the current UI. Currently the LC is assigned as part of the usual system details update, so these permission aspects of the system details could magically change for the person adding the system.

Instead maybe the 'Add (+)' button could lead to a page where we first pick the LC where the system will reside, and we can then present the regular system add page, although pre populated to the extent we want.

Comment 2 Nick Coghlan 2013-06-26 01:09:00 UTC

Yeah, in the near term I'll likely cover this in the much-needed architecture guide (or perhaps in the admin guide, with a reference to the architecture guide).

I also agree that actually make this change would require picking the lab controller before configuring the new system. I'd actually like to make it easier to get the list of lab controllers in the web UI, anyway, along with some basic stats for each lab (like total number of machines, machines in the public pool, a filtered list of systems in that lab), etc.