Provide keystone protocol to keystone.conf, used in v3 endpoints
Register endpoints with public name and FQDN when possible

When using SSL, the common name field in the certificates is checked,
and using IP addresses won't work with that.

Internally to the OpenStack setup, it is always fine to use the FQDN
from the node, so we use this in the internal and admin URLs of the
endpoints.

For the public URL, we prefer to use the public name if it is set. If it
it not set, then we use the public FQDN only if SSL is enabled;
otherwise, we prefer the IP address (like before) because we're not 100%
sure that the administrator will have completed a proper DNS setup where
the public FQDN generated by Crowbar will be announced externally.
Correctly set endpoints in keystone.conf too
Allocate public IP address to keystone-server nodes

The keystone server needs to be accessible from the external network, so
that OpenStack command line tools work.
Merge pull request #99 from vuntz/allocate-public-ip

Allocate public IP address to keystone-server nodes
Merge pull request #96 from saschpe/release/pebbles/master

Provide keystone protocol to keystone.conf, used in v3 endpoints
Enable LDAP as a keystone backend (bnc#785470)

Therefore, changing the identity driver is necessary.  Templatize LDAP
configuration in the chef recipe. There are too many values to present
them in the UI in any meaningful way.
Merge pull request #98 from vuntz/use-public-name

Register endpoints with public name and FQDN when possible
Merge pull request #100 from saschpe/release/pebbles/master-ldap

Enable LDAP as a keystone backend (bnc#785470)
Style edit attributes