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>

1 files changed, 13 insertions, 0 deletions

diff --git a/releasenotes/notes/add-ping-endpoint.yaml b/releasenotes/notes/add-ping-endpoint.yaml
new file mode 100644
index 0000000..180f7f2
--- /dev/null
+++ b/releasenotes/notes/add-ping-endpoint.yaml
@@ -0,0 +1,13 @@
+---
+features:
+  - |
+    RPC dispatcher can have an extra endpoint named ping.
+    This endpoint can be enabled thanks to a specific configuration parameter:
+    [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).