Fixes bug 980037
Service managers starting keystone-all have no way of being notified
when the service is ready to accept connections. This commit allows
a configurable command to be called when we are ready e.g.
for systemd setting the statup type of a service unit to "notify" and setting
onready = systemd-notify --ready
in keystone.conf, would notify a waiting systemd that we are ready to
serve
In an automated envirnment (e.g. puppet) this will allow the startup of
the keystone-all service (with systemctl for example) directly followed
by usage of the keystone client without the need for a sleep (or retry)
while we are waiting for the keystone service to be ready.
Change-Id: I3f7aafe9837be60a0f35cae1a7db892f6851cc47
Make sure all the available options are include in the file, add
some more documentation and, rather than set any of the defaults,
just include them as comments.
Change-Id: I2cb6060f47ea88349b1862d4d995c80cf9237066
we shouldn't be using options at all, that was a leftover piece of code
from a long time ago.
invalidates bug 949373
Change-Id: I29fcbd5f641464bda985900172b55bca45843f81
This should be the public_port and not the admin one.
Change-Id: Ib09e7479c0507797532e6bb91d76b7d3083cc761
Signed-off-by: Julien Danjou <julien.danjou@enovance.com>
The Keystone service template parser doesn't do any quote interpolation,
it just splits on ' = ' and passes the two parts on. So we just remove
the quotes for now.
Fixes bug 943523
Change-Id: Ib9e17e70926339ab67f9c50a52a5036eeb7bfb65
keystone.common.policy is copied from nova
leave simple backend in as a shim until devstack stops referencing it
Change-Id: Ibd579cfeb99465706d525b6565818a2d8f5f3b7c
Bug 933852
Merged over the code from the legacy keystone implementation, updated
style and streamlined the API a bit.
* Unit tests can be run against a live OpenLDAP server
* Password hashing done via passlib. Only does salted sha1, which is what simple_bind requires, but is not secure.
* Added pip dependencies
Change-Id: I5296d94f6b7d0a7c7dbc887cdae872171e34bb5f
Middleware rewrites incoming XML requests as JSON, and outgoing JSON as
XML, per Accept and Content-Type headers.
Tests assert that core API methods support WADL/XSD specs, and cover
JSON content as well.
Change-Id: I6897971dd745766cbc472fd6e5346b1b34d933b0
