Hi Bob, On 2012-05-09, at 6:26 PM, Robert Kukura wrote: >> >> I'm less clear on the need to implement rpc communication between the vif >> driver and quantum plugin, at least as part of this blueprint. Am I missing >> a use-case that is not already handled by Quantum's rest interface? > > At least one of the reasons for this is so that connection of a newly > created tap device to the virtual network by the agent would be > triggered immediately by the RPC, rather than waiting for agent's > periodic poll of the node's local tap devices to discover it. >
I'm afraid I don't see your logic. The path is: Virt driver -> Quantum -> Plugin -> Agent The blueprint in question proposes that communication between plugin and agent be conducted via rpc rather than the current shared database. The proposal ensures that there is no polling involved. I see no reason for communication between the virt driver and quantum be conducted over rpc when a rest interface can do the same job with no extra effort or complexity. Thanks, Maru
-- Mailing list: https://launchpad.net/~netstack Post to : netstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~netstack More help : https://help.launchpad.net/ListHelp
