This was discussed with Colleen and Kristi in IRC [0]. The following was proposed
- write a patch so that devstack always configures sql as the identity backend
- when ldap is set as KEYSTONE_IDENTITY_BACKEND, ensure it's done in a domain-specific way
- write a patch so keystone fails gracefully with an informative warning saying `bootstrap` is only intended for sql-based deployments
This was discussed with Colleen and Kristi in IRC [0]. The following was proposed
- write a patch so that devstack always configures sql as the identity backend IDENTITY_ BACKEND, ensure it's done in a domain-specific way
- when ldap is set as KEYSTONE_
- write a patch so keystone fails gracefully with an informative warning saying `bootstrap` is only intended for sql-based deployments
Thoughts on the approach?
[0] http:// eavesdrop. openstack. org/irclogs/ %23openstack- keystone/ %23openstack- keystone. 2017-08- 11.log. html#t2017- 08-11T20: 45:37