tripleo-heat-templates/environments/enable-stf.yaml
Chris Sibbitt 15dfacb655 Disable presettled metrics
Our lab testing shows that message loss is unacceptably high when using
presettled mode for non-trivial metrics volumes. "unsettled" mode (the
alternative) has been shown to be 100% reliable while still acheiving equal or
greater overall max throughput in live testing with a baremetal cloud.

Change-Id: I9388994ee94ab1e3c3e15768a8eb96069c2d8a0b
2020-06-11 15:26:24 -04:00

40 lines
1.5 KiB
YAML

# This heat environment can be used to enable STF client side
resource_registry:
OS::TripleO::Services::Collectd: ../deployment/metrics/collectd-container-puppet.yaml
OS::TripleO::Services::MetricsQdr: ../deployment/metrics/qdr-container-puppet.yaml
OS::TripleO::Services::Redis: ../deployment/database/redis-pacemaker-puppet.yaml
# We want these when smartgateway is able to process ceilometer messages
# OS::TripleO::Services::CeilometerAgentCentral: ../deployment/ceilometer/ceilometer-agent-central-container-puppet.yaml
# OS::TripleO::Services::CeilometerAgentNotification: ../deployment/ceilometer/ceilometer-agent-notification-container-puppet.yaml
# OS::TripleO::Services::ComputeCeilometerAgent: ../deployment/ceilometer/ceilometer-agent-compute-container-puppet.yaml
parameter_defaults:
# Uncomment when smartgateway can handle ceilometer messages
# CeilometerQdrPublish: true
EnableSTF: true
CollectdConnectionType: amqp1
CollectdAmqpInterval: 5
CollectdDefaultPollingInterval: 5
CollectdAmqpInstances:
notify:
notify: true
format: JSON
presettle: false
telemetry:
format: JSON
presettle: false
MetricsQdrAddresses:
- prefix: collectd
distribution: multicast
MetricsQdrSSLProfiles:
- name: sslProfile
# The snippet below should be added to a separate yaml file, edited, and
# passed in at deploy time.
#MetricsQdrConnectors:
# - host: qdr-normal-sa-telemetry.apps.remote.tld
# port: 443
# role: edge
# sslProfile: sslProfile
# verifyHostname: false