From 6c5f7d9e10f059e2bc1e56ea2d4e32a7e4cadc8b Mon Sep 17 00:00:00 2001 From: Derek Higgins Date: Wed, 9 May 2012 21:17:41 +0000 Subject: notify calling process we are ready to serve 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 --- etc/keystone.conf.sample | 4 ++++ 1 file changed, 4 insertions(+) (limited to 'etc/keystone.conf.sample') diff --git a/etc/keystone.conf.sample b/etc/keystone.conf.sample index 4f146d91..7d3d52c8 100644 --- a/etc/keystone.conf.sample +++ b/etc/keystone.conf.sample @@ -46,6 +46,10 @@ # Format string for %(asctime)s in log records. # log_date_format = %Y-%m-%d %H:%M:%S +# onready allows you to run a command when the process is ready to serve +# for example to have it notify using systemd, one could set +# onready = systemd-notify --ready + [sql] # The SQLAlchemy connection string used to connect to the database # connection = sqlite:///keystone.db -- cgit