Itsuro Oda 18e444ee1f Enable to select an RPC handling plugin under Metaplugin ... Multiple plugins under metaplugin become 'q-plugin' topic consumers and a request from an agent is handled by one of them randomly. Fortunatly most of RPC callbacks are common for plugins but a problem occurs if an RPC is not supported by the received plugin. This is one of risks when using metaplugin. Fundamental fix of this problem (such as RPC delegation handling of metaplugin) is difficult since each plugin needs to modify. But when only one plugin has plugin specific RPCs and other RPCs are independet of plugins, if the plugin can be selected for RPC handling, the problem does not happen. Typical use case of metaplugin such as combination of an agent-based plugin and a controller-based plugin often applies to this condition. This patch adds 'rpc_flavor' configuration parameter to select an RPC handling plugin. If 'rpc_flavor' is specified, only the specified plugin becomes 'q-plugin' topic consumer. If 'rpc_flavor' is not specified, the behavior is same as previous one. Change-Id: If133b054bba53829cebe63c1e0ebe6099eb1fd95 Closes-bug: #1267330 DocImpact		2014-03-19 12:14:18 +09:00
..
__init__.py	Rename Quantum to Neutron	2013-07-06 15:02:43 -04:00
fake_plugin.py	Make metaplugin be used with a router service plugin	2014-02-24 07:24:02 +09:00
test_basic.py	Enhance GET networks performance of metaplugin	2014-03-06 07:30:05 +09:00
test_metaplugin.py	Enable to select an RPC handling plugin under Metaplugin	2014-03-19 12:14:18 +09:00