openstack/vitrage
Code Issues Proposed changes

messaging use blocking instead of threading

Browse Source 
collector notification topic name change

Change-Id: I6ed7ff08ff8c79f656b22731ecb7897ea0df82b1
This commit is contained in:
Idan Hefetz 2017-07-03 10:46:43 +00:00
parent 41f863bbb7
commit e2427934b0
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
vitrage/datasources/__init__.py
View File

@ -49,7 +49,7 @@ OPTS = [
default='vitrage_notifications', default='vitrage_notifications',
help='Vitrage configured notifications topic'), help='Vitrage configured notifications topic'),
cfg.StrOpt('notification_topic_collector', cfg.StrOpt('notification_topic_collector',
default='collector_event_notification', default='vitrage_collector_notifications',
help='The topic on which event will be sent from the ' help='The topic on which event will be sent from the '
'datasources to the graph processor') 'datasources to the graph processor')
] ]

2
vitrage/messaging.py
View File

@ -52,7 +52,7 @@ def get_notification_listener(transport, targets, endpoints,
allow_requeue=False): allow_requeue=False):
"""Return a configured oslo_messaging notification listener.""" """Return a configured oslo_messaging notification listener."""
return oslo_messaging.get_notification_listener( return oslo_messaging.get_notification_listener(
transport, targets, endpoints, executor='threading', transport, targets, endpoints, executor='blocking',
allow_requeue=allow_requeue) allow_requeue=allow_requeue)