Go to file

Jean-Philippe Evrard e32a664a6e Use the good configuration directive for memcache servers

Under Pike, both the backend argument and memcache_servers work.
They both end-up with connections to the backend of memcache.

The latter doesn't have the bug when multiple servers are given,
though. So let's use this one exclusively.

This massive template change is for backwards compatibility:
If a deployer has set on of those keystone variables, the servers
used won't change.

Change-Id: I7e29aa0a9055b737dd4cf171c40e2105e4b32e94
Related-Bug: #1743036
(cherry picked from commit e87e2bd737)

2018-03-19 08:56:08 +00:00

defaults

Use the good configuration directive for memcache servers

2018-03-19 08:56:08 +00:00

doc

Fix 404 for os_keystone

2017-01-13 14:58:11 +00:00

examples

[DOCS] Move keystone federation role docs

2016-08-16 08:46:08 +00:00

files

Implement keystone venv support

2015-10-14 13:59:47 -05:00

handlers

Implement serialisable rolling upgrade

2017-06-23 17:07:55 +00:00

library

Resolved Keystone Federation bugs

2017-02-08 11:20:45 +00:00

README.rst

Team and repository tags

OpenStack-Ansible keystone

Ansible role that installs and configures OpenStack Keystone. Keystone is installed behind the Apache webserver listening on port 5000 and port 35357 by default.

Documentation for the project can be found at: http://docs.openstack.org/developer/openstack-ansible-os_keystone/ The project home is at: http://launchpad.net/openstack-ansible