Hi Salvatore,
Thanks for starting this. A few comments/questions - * You mention - "This model however implies that the Quantum plugin will be doing not just the 'logical' plugging of the VIF/vNIC, but also the 'physical' plugging, which is not what happens today." May be I am not reading this correctly, but the underlying plugin implementation today does perform the physical plugging, right? So how would that be different in the "basic plugin". Just want to make sure that I understand you correctly. * You mention - "Compute Manager invokes Network manager for allocating networks for instance (compute.manager._make_network_info)". This step would result in the creation on a Quantum network (with the allocation of a VLAN), right? * Per steps 2 to 6 in the workflow, I gather that the proposal is to logically associate a VIF with a port first (but what is the trigger for doing this; create_port()? invoked from where?), and the physical plugging happens via the VIF driver. Is that correct? If so how will the VIF ID be available to Quantum (since the VM is not up at that point)? * You mention - "Given this workflow, it turns out that the operations that the Basic VLAN plugin would performs are exactly the same as the ones performed by the VIF driver." Per my understanding, the VIF driver only creates the VIF configuration (including populating any information on where the VIF would be connected to when it comes up). So I am a little confused by the earlier statement that the operations are "exactly the same". * You mention - "Therefore a first potentially extremely simple implementation of this plugin would consist of a simple 'VLAN ID' tracker, as it will just provide the VIF driver the appropriate VLAN ID to configure on each compute host." How will the plugin make the VLAN ID available to the driver? * You mention - "The ideal destination point would be ending up in a situation in which we would not need anymore a VIF driver at all." I am not sure I agree with this (unless of course my understanding for the need of the VIF driver is incorrect). Isn't the VIF owned by compute (nova)? * I am not clear as to how the plug/unplug operations on a port are going to be realized in the above proposal. Could you kindly elaborate? Thanks, ~Sumit. From: netstack-bounces+snaiksat=cisco....@lists.launchpad.net [mailto:netstack-bounces+snaiksat=cisco....@lists.launchpad.net] On Behalf Of Salvatore Orlando Sent: Monday, October 17, 2011 6:55 AM To: netstack@lists.launchpad.net Subject: [Netstack] 'Basic VLAN' plugin - some thoughts Hi all, I put some thoughts regarding the design and the implementation of this plugin on a wiki page: http://wiki.openstack.org/Quantum-BasicVlanPlugin Please let me have your feedback. If everything goes according to plan, I plan to start implementing this plugin in two weeks' time. Regards, Salvatore
-- Mailing list: https://launchpad.net/~netstack Post to : netstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~netstack More help : https://help.launchpad.net/ListHelp
