Relax regex when keystone refuses connections

Seems newer python-keystoneclient have a different excpetion message,
specifically they dropped the HTTP prefix.  Now we allow both messages to be
trapped.

Add some additional cases that are common regex now covers
 (HTTP 400)
 [Errno 111] Connection refused
 503 Service Unavailable
 Max retries exceeded
 HTTP Unable to establish connection
 Unable to establish connection to http://...

Change-Id: I71fada12b3dbb681288c7ef2891603f970910736
Signed-off-by: Paul Belanger <paul.belanger@polybeacon.com>
Signed-off-by: Andrew Woodward <awoodward@mirantis.com>
ensure log_file is absent when using syslog

When using syslog, we don't need to write in keystone.log file, so
log_file param should be absent to avoid any write in the file.

Example: run keystone-manage db_sync will write in ~/keystone.log
instead of /var/log/syslog.

Closes-bug #1292619
Signed-off-by: Emilien Macchi <emilien.macchi@enovance.com>
Change-Id: I9b2613294625f3df27a70f45bd964688a425c88e
Merge "ensure log_file is absent when using syslog"
Add service validation and encapsulation

This patch moves the keystone service resource
to a new class, keystone::service, and adds
a new resource that uses the admin credentials
to confirm the keystone server is accepting
connections and functioning well from the client
perspective. This validation resource is optional
and if specified will be required by all keystone
custom types.

In order to take advantage of this change, consumers
of the keystone service should depend on this class
instead of the keystone service.

Conflicts:
	manifests/init.pp

Change-Id: Ibd92a7c40658bb242b3b55980489949cb5835145