[Expired for neutron because there has been no activity for 60 days.]
** Changed in: neutron
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1112634
Title:
allow RPC version evolves independently for each of features
Status in neutron:
Expired
Bug description:
a call back which includes all of features is blocking RPC version
evolves right.
for example:
plugin:
class LinuxBridgeRpcCallbacks(dhcp_rpc_base.DhcpRpcCallbackMixin,
l3_rpc_base.L3RpcCallbackMixin,
sg_db_rpc.SecurityGroupServerRpcCallbackMixin):
RPC_API_VERSION = '1.1'
# Device names start with "tap"
# history
# 1.1 Support Security Group RPC
agent:
linux_bridge_agent:
class LinuxBridgePluginApi(agent_rpc.PluginApi,
sg_rpc.SecurityGroupServerRpcApiMixin):
pass
DHCP_agent
DhcpPluginApi
BASE_RPC_API_VERSION = '1.0'
L3_agent:
class L3PluginApi(proxy.RpcProxy):
BASE_RPC_API_VERSION = '1.0'
If I want to add a function in the L3RpcCallbackMixin:
I have to bump the RCP_API_VERSION to 1.2
and L3PluginApi's version to 1.2 too.
howerver, in ovs plugin:
class OVSRpcCallbacks(dhcp_rpc_base.DhcpRpcCallbackMixin,
l3_rpc_base.L3RpcCallbackMixin):
# Set RPC API version to 1.0 by default.
RPC_API_VERSION = '1.0'
at this time I have to bump RPC_API_VERSION into 1.2 too.
all this 1.2 is due to the LinuxBridgeRpcCallbacks's RPC_API_VERSION version
is 1.1 now.
at the same time, we cannot use one big rpcproxy too.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1112634/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
