summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJoseph Davis <joseph.davis@suse.com>2018-12-19 08:50:36 -0800
committerJoseph Davis <joseph.davis@suse.com>2018-12-19 08:50:36 -0800
commit551984592f6ffda09e98922c7d60574ef2370bf9 (patch)
treee68b18825e36e351fd96b0fd88689bed06b38465
parentabb385478417df3fcc8ef215f20b3ee2ebee3065 (diff)
Fix a few nits in events-listener specHEADmaster
Minor edits to polish the specification. Change-Id: Iab9bfd91359586aa1b389f8bd7c45b9bc7e0cc90 Story: 2003023 Task: 23047
Notes
Notes (review): Code-Review+2: Doug Szumski <doug@stackhpc.com> Workflow+1: Doug Szumski <doug@stackhpc.com> Verified+2: Zuul Submitted-by: Zuul Submitted-at: Wed, 19 Dec 2018 17:21:52 +0000 Reviewed-on: https://review.openstack.org/626362 Project: openstack/monasca-specs Branch: refs/heads/master
-rw-r--r--specs/stein/approved/monasca-events-listener.rst9
1 files changed, 6 insertions, 3 deletions
diff --git a/specs/stein/approved/monasca-events-listener.rst b/specs/stein/approved/monasca-events-listener.rst
index c01d5b1..b0809fe 100644
--- a/specs/stein/approved/monasca-events-listener.rst
+++ b/specs/stein/approved/monasca-events-listener.rst
@@ -218,7 +218,6 @@ Proposed change
218 218
219#. Monasca Events API allows a field called 'payload' which can be in an arbitrary 219#. Monasca Events API allows a field called 'payload' which can be in an arbitrary
220 nested JSON format. 220 nested JSON format.
221 TODO: mappings
222 221
223 Example Monasca Event Format: 222 Example Monasca Event Format:
224 223
@@ -394,7 +393,7 @@ Alternative Solutions
394 architecture. 393 architecture.
395 * Regions may also cause separation of RabbitMQ instances that need to be monitored. 394 * Regions may also cause separation of RabbitMQ instances that need to be monitored.
396 * While it might be possible to have a service/agent in each Cell publish back to 395 * While it might be possible to have a service/agent in each Cell publish back to
397 a centralized to Kafka directly, our authentication and networking for Kafka was 396 a centralized Kafka directly, our authentication and networking for Kafka was
398 not designed to support that. 397 not designed to support that.
399 398
400#. OpenStack Panko [5]_ is a event storage and REST API for Ceilometer and could 399#. OpenStack Panko [5]_ is a event storage and REST API for Ceilometer and could
@@ -460,6 +459,10 @@ Performance Impact
460#. The proposed Monasca Event Listener is a new service, so performance is unknown. However, the 459#. The proposed Monasca Event Listener is a new service, so performance is unknown. However, the
461 Monasca API has been shown to have a high performance throughput. 460 Monasca API has been shown to have a high performance throughput.
462 461
462#. If any part of the Monasca notification pipeline goes down, notifications could back-up in
463 RabbitMQ and bring down the cluster. The risk of this could be mitigated by using a
464 separate RabbitMQ instance for notifications.
465
463 466
464Other deployer impact 467Other deployer impact
465--------------------- 468---------------------
@@ -583,4 +586,4 @@ References
583 586
584[17] Monasca Events API publisher to Kafka: https://github.com/openstack/monasca-events-api/blob/master/monasca_events_api/app/common/events_publisher.py 587[17] Monasca Events API publisher to Kafka: https://github.com/openstack/monasca-events-api/blob/master/monasca_events_api/app/common/events_publisher.py
585 588
586.. [18] Monasca IRC meeting Dec 15, 2018: http://eavesdrop.openstack.org/meetings/monasca/2018/monasca.2018-12-12-15.00.log.html \ No newline at end of file 589.. [18] Monasca IRC meeting Dec 15, 2018: http://eavesdrop.openstack.org/meetings/monasca/2018/monasca.2018-12-12-15.00.log.html