Duong Ha-Quang f7870e1d2f Implement Keystone zero-downtime upgrade ... 1- Expand and migrate database in first keystone node 2- Upgrade all nodes sequentially along with updation of each node's configuration file with latest release version 3- Last keystone node, contract database With this patch, there is small downtime when all containers are restarted. It will be fixed in other patch. [1] http://docs.openstack.org/developer/keystone/upgrading.html#upgrading-without-downtime Co-Authored-By: Surya Prakash Singh <surya.singh@nectechnologies.in> Co-Authored-By: Eduardo Gonzalez <dabarren@gmail.com> Co-Authored-By: Duong Ha-Quang <duonghq@vn.fujitsu.com> Partially-Implements: blueprint ks-rolling-upgrade-role Change-Id: I2159af567c40848840ff5e483e7d1f6de760b435		2017-11-16 11:13:50 +07:00
..
bootstrap.yml	Fix the database user name for all roles	2017-06-20 21:19:31 +08:00
bootstrap_service.yml	Optimize reconfiguration for keystone	2017-01-05 14:15:20 +08:00
check.yml	Fix deployment with public TLS enabled	2017-10-05 08:36:34 +00:00
config.yml	Specify 'become' for only necessary tasks (default roles)	2017-10-31 02:55:31 +00:00
deploy.yml	Simplify condition check on standalone services	2017-06-15 17:15:17 +02:00
init_fernet.yml	Wait keystone_fernet running before init tokens	2017-07-26 10:52:59 +00:00
main.yml	Allow keystone role to pull images	2016-01-06 04:23:28 +00:00
precheck.yml	Generalize api_interface_address variable usage	2017-05-23 08:35:15 +00:00
pull.yml	Fix the error when pull keystone image	2017-01-18 13:38:50 +08:00
reconfigure.yml	Remove symlink in reconfigure tasks	2017-07-03 09:34:21 +00:00
register.yml	Fix deployment with public TLS enabled	2017-10-05 08:36:34 +00:00
upgrade.yml	Implement Keystone zero-downtime upgrade	2017-11-16 11:13:50 +07:00