keystone-specs/specs
Harry Rybacki acfc05ae96 Define a set of basic default roles
With the recent work to keystone and oslo.policy, we should be able to
offer tooling to project development teams so they can start evolving
their policies. Before we start changing things, we should come to
consensus on a set of defaults we should offer out of the box.

Moving towards a set of known defaults will make maintenance for
operators much easier. It will also build the foundation for a more
robust RBAC system that is better at modeling complex
organization, ultimately being more useful in the real-world.

Change-Id: Ia6ddf64b4483a73ab79c86d5d794cce561aa19e0
Co-authored-By: Lance Bragstad <lbragstad@gmail.com>
Co-Authored-By: Jamie Lennox <jamielennox@gmail.com>
2018-05-20 13:40:30 -04:00
..
keystone Define a set of basic default roles 2018-05-20 13:40:30 -04:00
keystoneclient Reorder the specs repo 2016-03-31 01:57:42 -04:00
keystonemiddleware Typo fixing 2016-12-07 19:50:32 +08:00
template.rst Add requirement for APIImpact flag 2014-11-19 17:20:39 -06:00