dbece39f54
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
49 lines
1.2 KiB
YAML
49 lines
1.2 KiB
YAML
heat_template_version: 2016-10-14
|
|
description: 'Upgrade for via ansible by applying a step related tag'
|
|
|
|
parameters:
|
|
UpgradeStepConfig:
|
|
type: json
|
|
description: Config (ansible yaml) that will be used to step through the deployment.
|
|
default: ''
|
|
|
|
step:
|
|
type: string
|
|
description: Step number of the upgrade
|
|
|
|
resources:
|
|
|
|
AnsibleConfig:
|
|
type: OS::Heat::Value
|
|
properties:
|
|
value:
|
|
str_replace:
|
|
template: CONFIG
|
|
params:
|
|
CONFIG:
|
|
- hosts: localhost
|
|
connection: local
|
|
tasks: {get_param: UpgradeStepConfig}
|
|
|
|
AnsibleUpgradeConfigImpl:
|
|
type: OS::Heat::SoftwareConfig
|
|
properties:
|
|
group: ansible
|
|
options:
|
|
tags:
|
|
str_replace:
|
|
template: "stepSTEP"
|
|
params:
|
|
STEP: {get_param: step}
|
|
inputs:
|
|
- name: role
|
|
config: {get_attr: [AnsibleConfig, value]}
|
|
|
|
outputs:
|
|
OS::stack_id:
|
|
description: The software config which runs ansible with tags
|
|
value: {get_resource: AnsibleUpgradeConfigImpl}
|
|
upgrade_config:
|
|
description: The configuration file used for upgrade
|
|
value: {get_attr: [AnsibleConfig, value]}
|