openstack/kolla-ansible
Code Issues Proposed changes

Add some missing parameters for Monasca Notification

Browse Source 
Partially-Implements: blueprint monasca-roles
Change-Id: I21de7748156f8d3689ebfc29f2fc4dc5f7f36ddf
This commit is contained in:
Doug Szumski 2018-09-25 15:52:36 +00:00
parent da1fa3f578
commit c502e0b17a
1 changed files with 7 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
ansible/roles/monasca/defaults/main.yml
View File

@ -98,6 +98,13 @@ monasca_raw_logs_topic: "logs"
monasca_transformed_logs_topic: "transformed-logs" monasca_transformed_logs_topic: "transformed-logs"
monasca_events_topic: "events" monasca_events_topic: "events"
monasca_alarm_state_transitions_topic: "alarm-state-transitions" monasca_alarm_state_transitions_topic: "alarm-state-transitions"
monasca_alarm_notifications_topic: "alarm-notifications"
monasca_alarm_notifications_retry_topic: "retry-notifications"
monasca_periodic_notifications_topic: "60-seconds-notifications"
# NOTE(dszumski): Due to the way monasca-notification is currently
# implemented it is not recommended to change this period.
monasca_periodic_notifications_period: 60
# Processing pipeline threads. In a large scale deployment you will likely # Processing pipeline threads. In a large scale deployment you will likely
# want to tune these with finer precision. For example, if you have a very # want to tune these with finer precision. For example, if you have a very