----- Original Message -----
From: "Amit Saha" asaha@redhat.com To: "Beaker development" beaker-devel@lists.fedorahosted.org Cc: "Jeffrey Burke" jburke@redhat.com Sent: Sunday, February 8, 2015 7:37:48 PM Subject: Re: [Beaker-devel] Design proposal: Predefined Access Policies for Systems
Hi Jeff,
Amit, I read the Link you provided. I do have a question. Is this work being done to satisfy additional BZ or other long term goal? Who or What it the actual "use case". I see there is a "grey area" of dependency for "Scheduler Integration for System Pools"
Sorry, I don't understand what you mean by "grey area" of dependency.
The main goal of this work is to implement "Predefined Access Policies". The use case is to make it possible for multiple systems to share the same access policy without the same policy needing to be defined separately for all the systems which was first introduced in Beaker 0.15 [1].
Upon some discussions (on this mailing list) and thought, we reached the conclusion that this goal would be best met by introducing the "system pools" feature which we had earlier only considered as a standalone change and also included the "Scheduler Integration for System Pools" change [2].
A dependency is what I meant by "grey area". It was poorly worded on my part.
So, here is a sample use case:
You create a system pool and define a "pool policy". Now any system in Beaker (both outside and inside the system pool) can be access controlled by this pool policy or by its own custom policy.
I understand the changes. I will start a new thread with my other questions.
Thanks, Jeff
[1] https://beaker-project.org/dev/proposals/access-policies-for-systems.html [2] https://beaker-project.org/dev/proposals/system-pools.html
Best, Amit.
-- Amit Saha SED, Hosted & Shared Services Red Hat, Inc.