oslo.messaging/oslo_messaging/rpc
Arnaud Morin 82492442f3 Add a ping endpoint to RPC dispatcher
The purpose of this patch is to add an endpoint directly in RPC
dispatcher, so this endpoint will always be available, in a cross
project manner, without the need for projects to manage it by themself.

This endpoint stay disabled by default, so this change is harmless
without a specific configuration option.

To enable this ping endpoint, an operator will just have to add a new
parameter in the [DEFAULT] section, alongside with rpc_response_timeout
[DEFAULT]
rpc_ping_enabled=true  # default is false

The purpose of this new endpoint is to help operators do a RPC call (a
ping) toward a specific RPC callback (e.g. a nova-compute, or a
neutron-agent).
This is helping a lot for monitoring agents (for example, if agents are
deployed in a kubernetes pod).

The endpoint is named oslo_rpc_server_ping.

Change-Id: I51cf67e060f240e6eb82260e70a057fe599f9063
Signed-off-by: Arnaud Morin <arnaud.morin@corp.ovh.com>
2020-08-18 15:09:29 +02:00
..
__init__.py Add get_rpc_transport call 2017-05-12 12:30:41 -04:00
client.py Remove six usage 2020-05-11 10:21:58 +02:00
dispatcher.py Add a ping endpoint to RPC dispatcher 2020-08-18 15:09:29 +02:00
server.py Remove the deprecated blocking executor 2020-02-18 15:49:27 +01:00
transport.py Update hacking version 2019-01-21 19:45:42 -05:00