[library] add support for keystone ldap integration

[Oleksii Aleksieiev]

Community keystone puppet module allows to deploy keystone with storing identity in ldap backed.
Fuel should support setting ldap configuration on deployment stage at lease by changing settings.yaml.

Documentation about keystone with dap backend
http://docs.openstack.org/admin-guide-cloud/content/configuring-keystone-for-ldap-backend.html

puppet class for configuration keystone with dap backend
https://github.com/stackforge/puppet-keystone/blob/master/manifests/ldap.pp

[Tomasz 'Zen' Napierala (tzn)]

We already have pretty fresh BP for that: https://blueprints.launchpad.net/fuel/+spec/fuel-with-existed-ldap

[Dmitry Borodaenko (angdraug)]

Looks like a duplicate of this blueprint: https://blueprints.launchpad.net/fuel/+spec/fuel-with-existed-ldap

If so, please work with blueprint authors to make sure your ideas are reflected in their spec.

[Sergii Golovatiuk (sgolovatiuk)]

It's already possible with plugins. It's easy to write simple plugin to override keystone settings to use LDAP.

[Oleksii Aleksieiev (alexzzman)]

was the plugin architecture fixed to make sure that fuel and plugin changes to keystone fongi will not revert the into different directions?

The main problem with plugins in 6,1 is that the changes are maid in post deployment step but there is a gap between changes to config made by fuel and changes made by plug so we have several minutes when keystone will work with default setting (without ldap).

Usually ldap used in big deployments and i think its not acceptable to have several minutes of downtime during each change apply.

[Michael Polenchuk (mpolenchuk)]

Please refer to https://github.com/openstack/fuel-plugin-ldap

[Peter Zhurba (pzhurba)]

Due to inactivity, bug was closed. Feel free to reopen the bug by providing the requested information and set the bug status back to "New"