Blacklist support for ExtraConfig
authorJames Slagle <jslagle@redhat.com>
Fri, 16 Jun 2017 15:13:25 +0000 (11:13 -0400)
committerJames Slagle <jslagle@redhat.com>
Fri, 16 Jun 2017 15:13:25 +0000 (11:13 -0400)
commitd6c0979eb3de79b8c3a79ea5798498f0241eb32d
tree808607f65fe92d9e57b20c62b48159123818da0b
parent0354927a1143dd766cab4b9a88d4af84e404d6d9
Blacklist support for ExtraConfig

Commit I46941e54a476c7cc8645cd1aff391c9c6c5434de added support for
blacklisting servers from triggered Heat deployments.

This commit adds that functionality to the remaining Deployments in
tripleo-heat-templates for the ExtraConfig interfaces.

Since we can not (should not) change the interface to ExtraConfig, Heat
conditions are used on the actual <role>ExtraConfigPre and
NodeExtraConfig resources instead of using the actions approach on
Deployments.

Change-Id: I38fdb50d1d966a6c3651980c52298317fa3bece4
extraconfig/pre_deploy/rhel-registration/rhel-registration.yaml
extraconfig/pre_network/config_then_reboot.yaml
extraconfig/pre_network/host_config_and_reboot.role.j2.yaml
extraconfig/pre_network/host_config_and_reboot.yaml
extraconfig/tasks/ssh/host_public_key.yaml
puppet/blockstorage-role.yaml
puppet/cephstorage-role.yaml
puppet/compute-role.yaml
puppet/controller-role.yaml
puppet/objectstorage-role.yaml
puppet/role.role.j2.yaml