Jesse Pretorius e5894cb570 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. Conflicts: >------tasks/keystone_db_setup.yml Depends-On: Ie90cdcbf9e73082a2074c8832b7490d188e178af Change-Id: I5650f16b9a115bd392012b743788057a94d09226 (cherry picked from commit aad8144bfb)		2017-06-23 17:07:55 +00:00
..
main.yml	Implement serialisable rolling upgrade	2017-06-23 17:07:55 +00:00