Browse code
Unset admin_project config options for Keystone
Until the policy changes land for Nova, Glance, etc, this
value is not used. Additionally, by having it set, it actually
makes it hard/impossible for the required changes to land in
the other services. Disable/comment out the changes in the
Keystone specific lib file for now, and we will re-enable once
the Services can make use of them.
Change-Id: Ia1de9083c21107dac2f0abb56bda166bdb37a69d
Adam Young authored on 2016/10/26 18:40:08Showing 1 changed files
| ... | ... |
@@ -344,8 +344,8 @@ function configure_keystone {
|
| 344 | 344 |
# Configure the project created by the 'keystone-manage bootstrap' as the cloud-admin project. |
| 345 | 345 |
# The users from this project are globally admin as before, but it also |
| 346 | 346 |
# allows policy changes in order to clarify the adminess scope. |
| 347 |
- iniset $KEYSTONE_CONF resource admin_project_domain_name Default |
|
| 348 |
- iniset $KEYSTONE_CONF resource admin_project_name admin |
|
| 347 |
+ #iniset $KEYSTONE_CONF resource admin_project_domain_name Default |
|
| 348 |
+ #iniset $KEYSTONE_CONF resource admin_project_name admin |
|
| 349 | 349 |
} |
| 350 | 350 |
|
| 351 | 351 |
# create_keystone_accounts() - Sets up common required keystone accounts |