Enable to select an RPC handling plugin under Metaplugin

[OpenStack Infra]

https://review.openstack.org/79858
commit b98704e80b030f3a7db60cf244e29521008e94f2
Author: Itsuro Oda <email address hidden>
Date: Tue Dec 17 10:16:51 2013 +0900

    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

[Edgar Magana (emagana)]

Nachi, Any update on this one?

[Nachi Ueno (nati-ueno)]

I supposed this one solved by updateing help string in neutron code
Let me check

[Nachi Ueno (nati-ueno)]

Resolved by
https://review.openstack.org/#/c/88114/