Browse Source
Rather than using a new service, we can use the existing HeatEphemeral service we added to ensure the undercloud is prepared for the overcloud deployment usage of the ephemeral heat version. Additionally this will properly tear down the previous containered heat services once the data has been extracted from the existing databases. Change-Id: I13270a4866f9b339cb31ebba223121978e52b499changes/22/797522/2
8 changed files with 57 additions and 83 deletions
@ -1,69 +0,0 @@
|
||||
heat_template_version: wallaby |
||||
|
||||
description: > |
||||
Upgrade an undercloud to use ephemeral Heat |
||||
|
||||
parameters: |
||||
ServiceData: |
||||
default: {} |
||||
description: Dictionary packing service data |
||||
type: json |
||||
ServiceNetMap: |
||||
default: {} |
||||
description: Mapping of service_name -> network name. Typically set |
||||
via parameter_defaults in the resource registry. This |
||||
mapping overrides those in ServiceNetMapDefaults. |
||||
type: json |
||||
RoleName: |
||||
default: '' |
||||
description: Role name on which the service is applied |
||||
type: string |
||||
RoleParameters: |
||||
default: {} |
||||
description: Parameters specific to the role |
||||
type: json |
||||
EndpointMap: |
||||
default: {} |
||||
description: Mapping of service endpoint -> protocol. Typically set |
||||
via parameter_defaults in the resource registry. |
||||
type: json |
||||
OvercloudStackRoleDataFileMap: |
||||
default: {} |
||||
description: | |
||||
Mapping of overcloud stack name, and the absolute path to the |
||||
roles data file used when deploying/updating the stack. |
||||
For example: {'overcloud': '/home/stack/roles_data.yaml'} |
||||
type: json |
||||
|
||||
outputs: |
||||
role_data: |
||||
description: Role data for the TripleO Undercloud Upgrade Ephemeral Heat service. |
||||
value: |
||||
service_name: undercloud_upgrade_ephemeral_heat |
||||
upgrade_tasks: |
||||
- name: Create /var/lib/tripleo-config/scripts dir |
||||
file: |
||||
path: /var/lib/tripleo-config/scripts |
||||
state: directory |
||||
recurse: true |
||||
when: |
||||
- step|int == 1 |
||||
- name: Copy undercloud-upgrade-ephemeral-heat.py to /var/lib/tripleo-config/scripts |
||||
copy: |
||||
dest: /var/lib/tripleo-config/scripts/undercloud-upgrade-ephemeral-heat.py |
||||
content: {get_file: ../../scripts/undercloud-upgrade-ephemeral-heat.py} |
||||
mode: 0755 |
||||
when: |
||||
- step|int == 1 |
||||
- name: Store OvercloudStackRoleDataFileMap on file |
||||
vars: |
||||
role_data_file_map: {get_param: OvercloudStackRoleDataFileMap} |
||||
copy: |
||||
dest: /var/lib/tripleo-config/overcloud-stack-role-data-file-map.yaml |
||||
content: "{{ role_data_file_map | to_nice_yaml }}" |
||||
when: |
||||
- step|int == 1 |
||||
- name: Run undercloud-upgrade-ephemeral-heat.py |
||||
shell: /var/lib/tripleo-config/scripts/undercloud-upgrade-ephemeral-heat.py |
||||
when: |
||||
- step|int == 1 |
@ -1,8 +1,5 @@
|
||||
--- |
||||
features: |
||||
- A new service, OS::TripleO::Services::UndercloudUpgradeEphemeralHeat is |
||||
added to the Undercloud role. The service is mapped to OS::Heat::None by |
||||
default, but when environments/lifecycle/undercloud-upgrade-prepare.yaml is |
||||
included, the service will be enabled and will migrate any already deployed |
||||
stacks in the undercloud's Heat instance to be able to be used with the |
||||
ephemeral Heat deployment option from tripleoclient. |
||||
- Added Heat container tear down to the HeatEphemeral service to occur during |
||||
upgrades. This will convert an undercloud from non-ephemeral heat to |
||||
ephemeral heat when the service is enabled. |
||||
|
Loading…
Reference in new issue