Jesse Pretorius aad8144bfb Implement serialisable rolling upgrade
The current rolling upgrade implementation
relies on the role to orchestrate the rolling
upgrade. When the role is executed using
playbook serialisation, the db sync contract
is executed before all hosts are upgraded,
potentially resulting in data corruption.

This patch returns the role to the simpler,
best practice model of expecting that the role
is applied to a single host and that the
playbook handles orchestration. This method
can be used with any form of serialisation.

Depends-On: Ie90cdcbf9e73082a2074c8832b7490d188e178af
Change-Id: I5650f16b9a115bd392012b743788057a94d09226
2017-06-19 19:32:45 +00:00
2017-04-13 14:19:43 +00:00
2017-02-07 21:01:09 -06:00
2017-04-21 16:44:30 +01:00
2017-05-23 10:25:37 +08:00
2017-06-17 12:41:45 +01:00
2016-02-26 14:13:43 -06:00
2016-09-28 08:56:33 +01:00
2016-11-25 16:13:03 +01:00
2016-09-20 14:21:45 +05:30
2017-03-02 11:51:52 +00:00

Team and repository tags

image

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

Description
Role os_keystone for OpenStack-Ansible
Readme 11 MiB
Languages
Jinja 69.4%
Python 22%
Shell 8.6%