A notification listener exposes a number of endpoints, each of which contain a set of methods. Each method corresponds to a notification priority.
To create a notification listener, you supply a transport, list of targets and a list of endpoints.
A transport can be obtained simply by calling the get_notification_transport() method:
transport = messaging.get_notification_transport(conf)
which will load the appropriate transport driver according to the user’s messaging configuration. See get_notification_transport() for more details.
The target supplied when creating a notification listener expresses the topic and - optionally - the exchange to listen on. See Target for more details on these attributes.
Notification listener have start(), stop() and wait() messages to begin handling requests, stop handling requests and wait for all in-process requests to complete.
Each notification listener is associated with an executor which integrates the listener with a specific I/O handling framework. Currently, there are blocking and eventlet executors available.
A simple example of a notification listener with multiple endpoints might be:
from oslo_config import cfg
import oslo_messaging
class NotificationEndpoint(object):
filter_rule = NotificationFilter(publisher_id='^compute.*')
def warn(self, ctxt, publisher_id, event_type, payload, metadata):
do_something(payload)
class ErrorEndpoint(object):
filter_rule = NotificationFilter(event_type='^instance\..*\.start$',
context={'ctxt_key': 'regexp'})
def error(self, ctxt, publisher_id, event_type, payload, metadata):
do_something(payload)
transport = oslo_messaging.get_notification_transport(cfg.CONF)
targets = [
oslo_messaging.Target(topic='notifications')
oslo_messaging.Target(topic='notifications_bis')
]
endpoints = [
NotificationEndpoint(),
ErrorEndpoint(),
]
pool = "listener-workers"
server = oslo_messaging.get_notification_listener(transport, targets,
endpoints, pool)
server.start()
server.wait()
A notifier sends a notification on a topic with a priority, the notification listener will receive this notification if the topic of this one have been set in one of the targets and if an endpoint implements the method named like the priority and if the notification match the NotificationFilter rule set into the filter_rule attribute of the endpoint.
Parameters to endpoint methods are the request context supplied by the client, the publisher_id of the notification message, the event_type, the payload and metadata. The metadata parameter is a mapping containing a unique message_id and a timestamp.
By supplying a serializer object, a listener can deserialize a request context and arguments from - and serialize return values to - primitive types.
By supplying a pool name you can create multiple groups of listeners consuming notifications and that each group only receives one copy of each notification.
An endpoint method can explicitly return oslo_messaging.NotificationResult.HANDLED to acknowledge a message or oslo_messaging.NotificationResult.REQUEUE to requeue the message.
The message is acknowledged only if all endpoints either return oslo_messaging.NotificationResult.HANDLED or None.
Note that not all transport drivers implement support for requeueing. In order to use this feature, applications should assert that the feature is available by passing allow_requeue=True to get_notification_listener(). If the driver does not support requeueing, it will raise NotImplementedError at this point.
Construct a notification listener
The executor parameter controls how incoming messages will be received and dispatched. By default, the most simple executor is used - the blocking executor.
If the eventlet executor is used, the threading and time library need to be monkeypatched.
| Parameters: |
|
|---|---|
| Raises: | NotImplementedError |
Server for handling messages.
Connect a transport to a dispatcher that knows how to process the message using an executor that knows how the app wants to create new tasks.
Reset service.
Called in case service running in daemon mode receives SIGHUP.
Start handling incoming messages.
This method causes the server to begin polling the transport for incoming messages and passing them to the dispatcher. Message processing will continue until the stop() method is called.
The executor controls how the server integrates with the applications I/O handling strategy - it may choose to poll for messages in a new process, thread or co-operatively scheduled coroutine or simply by registering a callback with an event loop. Similarly, the executor may choose to dispatch messages in a new thread, coroutine or simply the current thread.
Stop handling incoming messages.
Once this method returns, no new incoming messages will be handled by the server. However, the server may still be in the process of handling some messages, and underlying driver resources associated to this server are still in use. See ‘wait’ for more details.
Wait for message processing to complete.
After calling stop(), there may still be some existing messages which have not been completely processed. The wait() method blocks until all message processing has completed.
Once it’s finished, the underlying driver resources associated to this server are released (like closing useless network connections).
Retrieve the RPC endpoint request context for the current thread.
This method allows any code running in the context of a dispatched RPC endpoint method to retrieve the context for this request.
This is commonly used for logging so that, for example, you can include the request ID, user and tenant in every message logged from a RPC endpoint method.
| Returns: | the context for the request dispatched in the current thread |
|---|