openstack/governance
Code Issues Proposed changes

Address minor grammatical issues in RBAC initiative

Browse Source 
This comments originally came out of:

  https://review.opendev.org/#/c/657447/5/reference/upstream-investment-opportunities/2018/rbac.rst

Fixing them here in a follow-up patch.

Change-Id: I91a16af9f8c86f5809a8097c38262fbff06548d9
This commit is contained in:
Lance Bragstad 2019-06-27 15:20:53 +00:00
parent 93acffc3b8
commit 938c64d31c
1 changed files with 12 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

24
reference/upstream-investment-opportunities/2018/rbac.rst
View File

@ -1,5 +1,5 @@
Consistent Role Based Access Control Consistent Role Based Access Control (RBAC)
==================================== ===========================================
Description Description
----------- -----------
@ -26,12 +26,12 @@ Value
Increased Functionality Increased Functionality
~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~
Currently, most OpenStack services have a very binary approach to RBAC Currently, most OpenStack services have a very binary approach to Role Based
enforcement. This approach usually handicaps new functionality from being Access Control (RBAC) enforcement. This approach usually handicaps new
exposed to users because users typically do not fall in one of two camps. functionality from being exposed to users because users typically do not fall
Contributors either need to lock down the feature to only system in one of two camps. Contributors either need to lock down the feature to only
administrators, or open it up to nearly every user in the deployment. This is system administrators, or open it up to nearly every user in the deployment.
especially true for APIs that expose details about multiple tenants. This is especially true for APIs that expose details about multiple tenants.
Implementing better API protection allows contributors to expose more Implementing better API protection allows contributors to expose more
functionality to end users and operators by default. Lowering the bar for users functionality to end users and operators by default. Lowering the bar for users
@ -61,10 +61,10 @@ Interoperability
Because policy configuration gives deployments the flexibility to maintain Because policy configuration gives deployments the flexibility to maintain
complicated policies at their own expense, it is common to see many complicated policies at their own expense, it is common to see many
organizations solve the same problem. Unfortunately, it's unlikely many of them organizations solve the same problem. Unfortunately, it's unlikely
are sharing the same solution. This pattern impedes interoperability between organizations are sharing the same solution. This pattern impedes
deployments, making it frustrating for users interacting with different interoperability between deployments, making it frustrating for users
OpenStack clouds. interacting with different OpenStack clouds.
Offering a reasonable set of roles and implementing basic RBAC improves Offering a reasonable set of roles and implementing basic RBAC improves
interoperability by not requiring each organization to solve the same problem interoperability by not requiring each organization to solve the same problem