Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -53,6 +53,10 @@ for svc_role in ${SVC_ROLES}; do
openstack role add --user "${SVC_ID}" --system all reader
openstack role add --user "${SVC_ID}" --system all member
;;
?*.manager)
# DOMAIN.manager is granted on the domain itself, not inherited by projects
openstack role add --user "${SVC_ID}" --domain "${svc_role%%.*}" manager
;;
?*.?*)
# DOMAIN.ROLE, e.g. a role on every project in the named domain
openstack role add --user "${SVC_ID}" --domain "${svc_role%%.*}" --inherited "${svc_role#*.}"
Expand Down
3 changes: 2 additions & 1 deletion docs/deploy-guide/openstack-automation-users.md
Original file line number Diff line number Diff line change
Expand Up @@ -27,7 +27,8 @@ Possible roles are:

A role can also be written as `DOMAIN.ROLE`, which grants the Keystone role
`ROLE` on the Keystone domain `DOMAIN`, inherited by every project in that
domain. Both forms can be mixed in one list.
domain. The one exception is `DOMAIN.manager`, which is granted on the domain
only and is not inherited by its projects. Both forms can be mixed in one list.

If any entry uses the `DOMAIN.ROLE` form, the account is created in the
`machine` Keystone domain, and that domain must already exist. Otherwise it is
Expand Down
Loading