ab4c114d5b
Adjust the enable-stf.yaml to work with the latest recommendations for use with Service Telemetry Framework. These changes provide the appropriate parameters to result in telemetry data being sent to STF in a format that it expects for dashboarding and alerting purposes. Recommend configuration of ceilometer and collectd collection agents plus data transport configuration with existing environment files in order to avoid duplicating the resource registry for service enablement. By separating the data collectors and data transports from the configuration more flexibility for different architectures is possible. Configuration options that have existing defaults defined in other locations have also been removed in order to keep things cleaner. Change-Id: I38d06056b56fb14c7162d546f6d688ba6ad59a5b Signed-off-by: Leif Madsen <lmadsen@redhat.com>
21 lines
891 B
YAML
21 lines
891 B
YAML
---
|
|
prelude: >
|
|
Enablement of data collection and transportation to an STF instance is now
|
|
handled via existing templates.
|
|
upgrade:
|
|
- |
|
|
When upgrading a deployment with the use of enable-stf.yaml, add the
|
|
following files to your overcloud deployment command in order to maintain
|
|
the existing services defined in enable-stf.yaml.
|
|
|
|
- environments/metrics/collectd-write-qdr.yaml
|
|
- environments/metrics/ceilometer-write-qdr.yaml
|
|
- environments/metrics/qdr-edge-only.yaml
|
|
other:
|
|
- |
|
|
Using enable-stf.yaml now defines the expected configuration in OpenStack
|
|
for use with Service Telemetry Framework. Removal of the defined
|
|
resource_registry now requires passing additional environment files to
|
|
enable the preferred data collectors and transport architecture, providing
|
|
better flexibility to support additional architectures in the future.
|