Hi Gary,
Great document!
I have few questions and comments considering proposed design:
1.Agent to Plugin messages are RPC messages without any output expected (cast
messages). Am I right? Alternative approach can be triggering this via VIF
driver providing full set of information regarding the VIF?
2. In the same section you talk about future method for network statistics,
this should be 'call' message. I do not quite understand why this message
should be called by Agent. For my understanding it should be triggered by nova.
What is the input/output for this? As you said in this section, Agent is not
aware of Network (only tap devices), so how does it retrieves the network
statistics?
3. when you talk about 2 dictionaries that plugin maintains, you mention that
plugin will use tap-device name as a key to one of them. I think this ties the
agent and a plugin too much. In case you want to change a naming convention of
VM net device, this will require changes on the plugin side. This probably done
in order to simplify, but if you associate the VIF device during the VIF plugin
phase, this can communicate the key to the plugin and no plugin code
modification required.
4. Regarding the Network Update flow that you mention, I think that changing
VLAN tag for existing Network is quite a complicated case. Maybe this should be
handled by creating new Network with new tag, de-associating VM from old
network and associating with new one?
5. Just a naming suggestion for network_details message. The message can be
called vif_network_profile. Message content can be called a network_profile:
vif_network_porfile: input parameters ( device name)
output parameters ( network_profile
dictionary)
6. when you mention that Agent can poll statistical information, can you please
say few words how/by whom this information will be used? What interfaces the
Agent should provide?
Gary,
I will be glad to assist you with this blueprint.
Regards,
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: Thursday, May 17, 2012 4:10 PM
To: <netstack@lists.launchpad.net>; Russell Bryant
Subject: [Netstack] Scalable Agent Detailed Design
Hi,
Please see the link for a detailed design of the scalable agent solution. I
plan to start to work on the actual implementation beginnig of next week.
Please let me know if you have any comments and or suggestions. Please note
that I have used all of the comments and suggestions from over the last few
weeks.
https://docs.google.com/document/d/1MbcBA2Os4b98ybdgAw2qe_68R1NG6KMh8zdZKgOlpvg/edit
Any comments and suggestions will be greatly appreciated 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
