82492442f3
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>
14 lines
492 B
YAML
14 lines
492 B
YAML
---
|
|
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).
|