openstack
/
ironic
Code Issues Proposed changes
ironic/ironic
History
Dmitry Tantsur 7efbbcc2d9 Support using JSON-RPC instead of oslo.messaging 
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
 		2019-02-14 12:56:20 +01:00
..
api Merge "Expose is_smartnic in port API" 2019-02-12 23:20:49 +00:00
cmd Allocation API: database and RPC 2019-01-07 12:51:10 +01:00
common Support using JSON-RPC instead of oslo.messaging 2019-02-14 12:56:20 +01:00
conductor Support using JSON-RPC instead of oslo.messaging 2019-02-14 12:56:20 +01:00
conf Support using JSON-RPC instead of oslo.messaging 2019-02-14 12:56:20 +01:00
db Add description field to node 2019-02-01 10:25:58 +08:00
dhcp Merge "Add meaningful exception in Neutron port show" 2018-03-16 13:49:39 +00:00
drivers Merge "Add support for Smart NICs" 2019-02-08 23:21:25 +00:00
hacking Follow-up to improve pep8 checking with hacking 2018-07-26 10:29:41 +07:00
objects Allocation API: REST API implementation 2019-02-08 18:47:25 +01:00
tests Support using JSON-RPC instead of oslo.messaging 2019-02-14 12:56:20 +01:00
__init__.py Move eventlet monkey patch code 2017-03-02 13:48:18 +02:00
version.py Correct version.py and update current version string 2014-03-21 13:50:05 -07:00