Bug 977714 - [RFE] Configure default system settings for a lab controller
[RFE] Configure default system settings for a lab controller
Status: NEW
Product: Beaker
Classification: Community
Component: inventory (Show other bugs)
0.12
Unspecified Unspecified
unspecified Severity unspecified (vote)
: ---
: ---
Assigned To: beaker-dev-list
tools-bugs
: FutureFeature
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-06-25 04:03 EDT by Nick Coghlan
Modified: 2016-05-26 09:28 EDT (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Nick Coghlan 2013-06-25 04:03:06 EDT
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 19:28:03 EDT
(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-25 21:09:00 EDT
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.

Note You need to log in before you can comment on or make changes to this bug.