diff options
author | Steven Hardy <shardy@redhat.com> | 2016-12-01 10:00:57 +0000 |
---|---|---|
committer | Steven Hardy <shardy@redhat.com> | 2016-12-01 13:40:50 +0000 |
commit | dbece39f549395c85701566edbff9fc19977665d (patch) | |
tree | eb5f368aa417e4c16fb4a071ae2c8e8428b679f2 /puppet/services/services.yaml | |
parent | ea3ace78398015578de77be5a782dfa6176decb7 (diff) |
Initial support for composable upgrades with Heat+Ansible
This shows how we could wire in the upgrade steps using Ansible
as was previously proposed e.g in https://review.openstack.org/#/c/321416/
but it's more closely integrated with the new composable services
architecture.
It's also very similar to the approach taken by SpinalStack where
ansible snippets per-service were combined then run in a series of
steps using Ansible tags.
This patch just enables upgrade of keystone - we'll add support for
other patches in subsequent patches.
Partially-Implements: blueprint overcloud-upgrades-per-service
Change-Id: I39f5426cb9da0b40bec4a7a3a4a353f69319bdf9
Diffstat (limited to 'puppet/services/services.yaml')
-rw-r--r-- | puppet/services/services.yaml | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/puppet/services/services.yaml b/puppet/services/services.yaml index ffe2d2d4..13df5bbe 100644 --- a/puppet/services/services.yaml +++ b/puppet/services/services.yaml @@ -108,3 +108,8 @@ outputs: expression: $.data.role_data.where($ != null).select($.get('service_config_settings')).where($ != null).reduce($1.mergeWith($2), {}) data: {role_data: {get_attr: [ServiceChain, role_data]}} step_config: {list_join: ["\n", {get_attr: [ServiceChain, role_data, step_config]}]} + upgrade_tasks: + yaql: + # Note we use distinct() here to filter any identical tasks, e.g yum update for all services + expression: $.data.where($ != null).select($.get('upgrade_tasks')).where($ != null).flatten().distinct() + data: {get_attr: [ServiceChain, role_data]} |