Configure additional info during bootstrap
Keystone bootstrap can also be passed with additional endpoint information. This will populate the initial catalog. Change-Id: I3e9c1df82b4dfc94253688038215a66ded365a95
This commit is contained in:
parent
6f90cd8528
commit
eeec9a52ee
|
@ -660,6 +660,14 @@ outputs:
|
|||
environment:
|
||||
KOLLA_BOOTSTRAP: true
|
||||
OS_BOOTSTRAP_PASSWORD: {get_param: AdminPassword}
|
||||
OS_BOOTSTRAP_USERNAME: 'admin'
|
||||
OS_BOOTSTRAP_PROJECT_NAME: 'admin'
|
||||
OS_BOOTSTRAP_ROLE_NAME: 'admin'
|
||||
OS_BOOTSTRAP_SERVICE_NAME: 'service'
|
||||
OS_BOOTSTRAP_ADMIN_URL: {get_param: [EndpointMap, KeystoneAdmin, uri_no_suffix]}
|
||||
OS_BOOTSTRAP_PUBLIC_URL: {get_param: [EndpointMap, KeystonePublic, uri_no_suffix]}
|
||||
OS_BOOTSTRAP_INTERNAL_URL: {get_param: [EndpointMap, KeystoneInternal, uri_no_suffix]}
|
||||
OS_BOOTSTRAP_REGION_ID: {get_param: KeystoneRegion}
|
||||
step_4:
|
||||
# There are cases where we need to refresh keystone after the resource provisioning,
|
||||
# such as the case of using LDAP backends for domains. So we trigger a graceful
|
||||
|
|
Loading…
Reference in New Issue