Remove Heat Cloudwatch API during upgrade and disable by default
authormarios <marios@redhat.com>
Fri, 6 Oct 2017 12:47:32 +0000 (15:47 +0300)
committerEmilien Macchi <emilien@redhat.com>
Tue, 17 Oct 2017 17:28:24 +0000 (17:28 +0000)
commit5a1297b02bfe51dd7707dce39eaf40b78f80f28e
tree1fd2cf1829352fbd07115b33e4270e3b94a401a8
parent9d04f0bf0ffcea31e4e51810fde95e276fe24fc2
Remove Heat Cloudwatch API during upgrade and disable by default

This adds a heat-api-cloudwatch-disabled.yaml and wires it up in
the resource registry. During the Ocata to Pike upgrade this service
will thus be stopped and disabled by default.

If you wish to keep the Heat Cloudwatch API then you should instead
use the provided heat-api-cloudwatch.yaml environment file.

Change-Id: I3f90a9799b90ca365f675f593371c1d3701fede6
Related-Bug: 1713531
(cherry picked from commit 4d21451666f2dd7a8935da3a7166a9afc2ccd6bd)
environments/services/heat-api-cloudwatch.yaml [new file with mode: 0644]
overcloud-resource-registry-puppet.j2.yaml
puppet/services/disabled/heat-api-cloudwatch-disabled.yaml [new file with mode: 0644]
releasenotes/notes/disable-heat-api-cloudwatch-d5a471da22472bde.yaml [new file with mode: 0644]