Excerpts from Nick Coghlan's message of 2015-01-19 11:20 +10:00:
I'd like to suggest one refinement: we should also make it easy
to
*clone* access policies when creating new ones, whether for a system
pool or for a custom policy. The difference between "clone policy from
<system pool X>" and "inherit policy from <system pool X>" is
that in
the latter case, a system will respect future changes to that policy,
while in the former it create an independent copy as a starting point
for future editing.
Yes that is a nice idea. It can be a separate enhancement of the access
policy editor widget: a new button "copy rules from <X>" where X can be
a system or a pool.
At the system pool level, something we may also want to consider is
the
idea of policy *sharing*, rather than inheritance or cloning. [...]
Hmm maybe... this seems like overkill though. If you have multiple pools
that you want to use the same policy on, just create a new pool for that
purpose and put all the systems into it.
That is to say, I am expecting that there will be pools created purely
for the purpose of sharing a policy between systems. Pools are just an
arbitrary collection of systems which owners are free create for any
purpose (easy identification of systems, grouping geographically or to
reflect org chart, for ease of sharing policies, etc... or in a future
release, for making scheduling decisions).
--
Dan Callaghan <dcallagh(a)redhat.com>
Software Engineer, Hosted & Shared Services
Red Hat, Inc.