7efbbcc2d9
Using AMQP-based RPC can be an overkill in case of ironic, especially when used standalone. This change allows using a built-in JSON RPC implementation instead. This implementation does not currently support the object indirection API, which does not seem to be used anywhere anyway. The standalone and API test jobs are changed to use JSON RPC. Story: #2004874 Task: #29141 Change-Id: I7cc95935d6bdae43fab5dfbd544c8e6d65fcc38d
9 lines
364 B
YAML
9 lines
364 B
YAML
---
|
|
features:
|
|
- |
|
|
Adds the ability to use JSON RPC for communication between API and
|
|
conductor services. To use it set the new ``rpc_transport`` configuration
|
|
options to ``json-rpc`` and configure the credentials and the ``host_ip``
|
|
in the ``json_rpc`` section. Hostnames of all conductors must be
|
|
resolvable for this implementation to work.
|