Go to file

Jean-Philippe Evrard cee7a02143 Allow the split of install and config

If keystone install is done separately from the config (filtering
or interruption), a re-run of the role will not mark the venv
as changed, and the db sync will not trigger.

Here we force a flush on file next to the venv change, and use
this file (local fact) as a way to know if a db sync is required.

When a dbsync is considered done, i.e after the expand and migrate
stages, we mark the db_migrate as done for all the nodes.

Change-Id: I318700582a65cc1ea6571d9460fd58bed949a4e9
Depends-On: Ie4a47e85bf31e1ac3a2bd6f0dec510bb24abdbbd

2017-04-03 14:05:07 +00:00

defaults

Ensure the components are isolated from the system

2017-03-28 23:48:01 -05:00

doc

Use https instead of http for git.openstack.org

2017-02-06 17:01:49 +07: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

Remove Trusty support from os_keystone role

2016-12-15 13:18:55 +00:00

library

Resolved Keystone Federation bugs

2017-02-07 21:01:09 -06: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