os_keystone without database fails

[Jimmy McCrory]

Setting keystone_database_enabled to false does not currently work.

Is this a viable deployment option that needs more logic to support it or should it be removed?

Optionally including the galera_client role fails because the task to gather OS specific variables is skipped, which causes tasks that make use of those vars to fail since they're undefined (even though those tasks are also being skipped).
https://github.com/openstack/openstack-ansible-os_keystone/blob/master/meta/main.yml#L41-L43

The os_keystone role will ultimately fail itself when attempting a db sync.

[Jean-Philippe Evrard (jean-philippe-evrard)]

Git blame shows this is REALLY old.

I agree we should maybe remove this.

Was there a specific use case you were trying to achieve? Should we kill the feature or fix it?

[Jimmy McCrory (jimmy-mccrory)]

Didn't have a use case, just noticed it the other day.
I'm for removing it.

[Lance Bragstad (lbragstad)]

It looks like we still use this option for deploying capstone. Our use case is probably best captured by the capstone design summary [0].

[0] https://github.com/rackerlabs/capstone#design

[Dolph Mathews (dolph)]

FWIW, Capstone [1] deploys Keystone using OSA (using the keystone_database_enabled option [2]) and then plugs in it's own non-SQL drivers.

[1] https://github.com/rackerlabs/capstone
[2] https://github.com/rackerlabs/capstone/blob/master/deploy/deploy.yml#L20

[Jean-Philippe Evrard (jean-philippe-evrard)]

See also our discussion here:
http://eavesdrop.openstack.org/irclogs/%23openstack-ansible/%23openstack-ansible.2016-11-29.log.html#t2016-11-29T16:48:05