Hi Gary, Great work! I also express my interest in this blueprint due to the reasons you mentioned. I would like to address number of points in the proposal. 1. VIF Driver to Quantum Server RPC messages: should it use existing APIs or requires new APIs as code or extension? 2. VIF Un-Plug flow: How it is assured that Quantum Server still has the required information when invoked by Agent? Or what you mean here is the VIF unplug RPC message is a core API 'unpluf_interface' call? 3. Quantum Server to Agent RPC Message content can/should be plug-in specific. Am I right? 4. Agent ID can be generated by using host UUID. 5. Are VIF Plug and Un-Plug the only triggers? Can there be some case when Agent need to get data but it's not due to VIF plug/Un-plug flow?
Thanks a lot, Irena -----Original Message----- From: netstack-bounces+irenab=mellanox....@lists.launchpad.net [mailto:netstack-bounces+irenab=mellanox....@lists.launchpad.net] On Behalf Of Gary Kotton Sent: Wednesday, May 09, 2012 2:42 PM To: <netstack@lists.launchpad.net> Subject: [Netstack] Scalable Agents (https://blueprints.launchpad.net/quantum/+spec/scalable-agent-comms) Hi, I have added a very high level description on how to address the issue. This can be seen at: https://docs.google.com/document/d/1MbcBA2Os4b98ybdgAw2qe_68R1NG6KMh8zdZKgOlpvg/edit Comments will be greatly appreciated. Questions: 1. Do we want agents to be backward compatible (that is, still maintain the polling code) 2. The generation of the Agent ID 3. Any other ideas or thoughts about the matter? I'd like to go ahead with a POC and implement this. Thanks Gary -- Mailing list: https://launchpad.net/~netstack Post to : netstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~netstack More help : https://help.launchpad.net/ListHelp -- Mailing list: https://launchpad.net/~netstack Post to : netstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~netstack More help : https://help.launchpad.net/ListHelp
