<html><body><div style="color:#000; background-color:#fff; font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:8pt"><div><span>Hi </span><span>Mathieu,</span></div><div style="color: rgb(0, 0, 0); font-size: 10.6667px; font-family: HelveticaNeue,Helvetica Neue,Helvetica,Arial,Lucida Grande,sans-serif; background-color: transparent; font-style: normal;"><span>Thanks for the link.</span> Some similarities for sure. I see Nova libvirt being used. I had looked at libvirt earlier.<br></div><div style="color: rgb(0, 0, 0); font-size: 10.6667px; font-family: HelveticaNeue,Helvetica Neue,Helvetica,Arial,Lucida Grande,sans-serif; background-color: transparent; font-style: normal;">Firstly, the libvirt support that Nova uses to communicate with LLDPAD doesn't have support for the latest 2.2 standard. The support is also only for the VEPA mode and not for VEB mode. It's also quite not clear as how the VLAN provided by
VDP is used by libvirt to communicate it back to Openstack.</div><div style="color: rgb(0, 0, 0); font-size: 10.6667px; font-family: HelveticaNeue,Helvetica Neue,Helvetica,Arial,Lucida Grande,sans-serif; background-color: transparent; font-style: normal;">There's already an existing blueprint where i can add more details (https://blueprints.launchpad.net/neutron/+spec/netron-ml2-mechnism-driver-for-cisco-dfa-support)</div><div style="color: rgb(0, 0, 0); font-size: 10.6667px; font-family: HelveticaNeue,Helvetica Neue,Helvetica,Arial,Lucida Grande,sans-serif; background-color: transparent; font-style: normal;"><br></div><div style="color: rgb(0, 0, 0); font-size: 10.6667px; font-family: HelveticaNeue,Helvetica Neue,Helvetica,Arial,Lucida Grande,sans-serif; background-color: transparent; font-style: normal;">Even for a single physical network, you need more parameters in the ini file. I was thinking of Host or Network Overlay with or w/o VDP for Tunnel
mode. I will add more to the blueprint.</div><div style="color: rgb(0, 0, 0); font-size: 10.6667px; font-family: HelveticaNeue,Helvetica Neue,Helvetica,Arial,Lucida Grande,sans-serif; background-color: transparent; font-style: normal;"><br></div><div style="color: rgb(0, 0, 0); font-size: 10.6667px; font-family: HelveticaNeue,Helvetica Neue,Helvetica,Arial,Lucida Grande,sans-serif; background-color: transparent; font-style: normal;">Thanks,</div><div style="color: rgb(0, 0, 0); font-size: 10.6667px; font-family: HelveticaNeue,Helvetica Neue,Helvetica,Arial,Lucida Grande,sans-serif; background-color: transparent; font-style: normal;">Paddu<br></div><div style="display: block;" class="yahoo_quoted"> <div style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 8pt;"> <div style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 12pt;"> <div dir="ltr"> <font
face="Arial" size="2"> On Friday, March 28, 2014 8:42 AM, Mathieu Rohon <mathieu.rohon@gmail.com> wrote:<br> </font> </div> <div class="y_msg_container">Hi,<br clear="none"><br clear="none"><br clear="none">the more I think about your use case, the more I think you should<br clear="none">create a BP to have tenant network based on interfaces created with<br clear="none">VDP protocol.<br clear="none">I'm not a VDP specialist, but if it creates some vlan back interfaces,<br clear="none">you might match those physical interfaces with the<br clear="none">physical_interface_mappings parameter in your ml2_conf.ini. Then you<br clear="none">could create flat networks backed on those interfaces.<br clear="none">SR-IOv use cases also talk about using vif_type 802.1qbg :<br clear="none"><a shape="rect" href="https://wiki.openstack.org/wiki/Nova-neutron-sriov" target="_blank">https://wiki.openstack.org/wiki/Nova-neutron-sriov</a><div class="yqt9158119945"
id="yqtfd30761"><br clear="none"><br clear="none"><br clear="none">Mathieu<br clear="none"></div><br><br></div> </div> </div> </div> </div></body></html>