diff options
| author |   Sofer Athlan-Guyot <sathlang@redhat.com> | 2017-04-03 18:28:21 +0200 |
|---|---|---|
| committer |   marios <marios@redhat.com> | 2017-04-04 11:44:43 +0300 |
| commit | d286892c785b8b81a866ea3c6a459d1fc4a347e8 (patch) | |
| tree | b0f018e293faf2b2ff15bb8e8afef214d50e053f /puppet/services/database/redis-base.yaml | |
| parent | 0b11bcee715dda0410e98960874cb9e0ad4a6a35 (diff) | |
Ensure upgrade step orchestration accross roles.
Currently we don't enforce step ordering across role, only within
role. With custom role, we can reach a step5 on one role while the
cluster is still at step3, breaking the contract announced in the
README[1] where each step has a guarantied cluster state.
We have to remove the conditional here as well as jinja has no way to
access this information, but we need jinja to iterate over all enabled
role to create the orchestration.
This deals only with Upgrade tasks, there is another review to deal
with UpgradeBatch tasks.
[1] https://github.com/openstack/tripleo-heat-templates/blob/master/puppet/services/README.rst
Closes-Bug: #1679486
Change-Id: Ibc6b64424cde56419fe82f984d3cc3620f7eb028
Diffstat (limited to 'puppet/services/database/redis-base.yaml')
0 files changed, 0 insertions, 0 deletions