7a438651af
Remove scripts and templates which dealt with Pacemaker and its
resource restarts before we moved to containerized deployments. These
should all now be unused.
Many environments had this mapping:
OS::TripleO::Tasks::ControllerPreConfig: OS::Heat::None
OS::TripleO::Tasks::ControllerPostConfig: OS::Heat::None
OS::TripleO::Tasks::ControllerPostPuppetRestart: ../../extraconfig/tasks/post_puppet_pacemaker_restart.yaml
The ControllerPostPuppetRestart is only ever referenced from
ControllerPostConfig, so if ControllerPostConfig is OS::Heat::None, it
doesn't matter what ControllerPostPuppetRestart is mapped to.
Change-Id: Ibca72affb3d55cf62e5dfb52fe56b3b1c8b12ee0
Closes-Bug: #1794720
16 lines
707 B
YAML
16 lines
707 B
YAML
---
|
|
upgrade:
|
|
- |
|
|
The environment file puppet-pacemaker.yaml has been removed, make
|
|
sure that you no longer reference it. The docker-ha.yaml file
|
|
should have already been used in place of puppet-pacemaker.yaml
|
|
during upgrade from Ocata to Pike. The environment file
|
|
puppet-pacemaker-no-restart.yaml has been removed too, it was only
|
|
used in conjunction with puppet-pacemaker.yaml.
|
|
- |
|
|
The environment file deployed-server-pacemaker-environment.yaml
|
|
has been removed, make sure that you no longer reference it. Its
|
|
current contents result in no tangible difference from the default
|
|
resource registry state, so removing the file should not change
|
|
the overcloud.
|