I have updated the draft design proposal for Beaker 1.1's System Pools
concept:
http://beaker-project.org/dev/proposals/system-pools.html#proposal-system...
There aren't any major changes to the design itself, the updates are
mostly editorial:
- clarify that pools have owning groups, and that it is the owners of
those groups that can change the pool policy
- give some tentative names to the proposed permissions (mostly for use
in the CLI)
- rename the "pool-manage" subcommand to "pool-modify"
- added an example of using autopick
- broke up the UI proposal section with additional heading
- added migration and deferred features sections
I also added a draft design proposal to follow on a release or two after
the initial system pools release:
http://beaker-project.org/dev/proposals/implicit-system-pools.html#propos...
The new proposal covers the automatic creation of implicit system pools
associated with each user group. It's just a rough sketch at the moment,
but I think we're going to see some of our users asking for it after the
explicit system pools feature lands. We may also need some elements from
it anyway, in order to handle the problem of migrating existing
system<->group associations to the pool model.
This is as much as I plan to flesh these out at this point - they're
useful things for us to keep in mind as we work on more near term stuff
for 0.12 and 1.0, but the details are inevitably going to shift based on
the feedback we receive on those earlier releases.
Cheers,
Nick.
--
Nick Coghlan
Red Hat Infrastructure Engineering & Development, Brisbane
Python Applications Team Lead
Beaker Development Lead (http://beaker-project.org/)
PulpDist Development Lead (http://pulpdist.readthedocs.org)