The blueprint is updated with more information on the requirements and
interaction with VDP
https://blueprints.launchpad.net/neutron/+spec/netron-ml2-mechnism-driver-for-cisco-dfa-support
On Monday, March 31, 2014 12:50 PM, Padmanabhan Krishnan <kpr...@yahoo.com>
wrote:
Hi Mathieu,
Thanks for the link. Some similarities for sure. I see Nova libvirt being used.
I had looked at libvirt earlier.
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.
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)
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.
Thanks,
Paddu
On Friday, March 28, 2014 8:42 AM, Mathieu Rohon <mathieu.ro...@gmail.com>
wrote:
Hi,
the more I think about your use case, the more I think you should
create a BP to have tenant network based on interfaces created with
VDP protocol.
I'm not a VDP specialist, but if it creates some vlan back interfaces,
you might match those physical interfaces with the
physical_interface_mappings parameter in your ml2_conf.ini. Then you
could create flat networks backed on those interfaces.
SR-IOv use cases also talk about using vif_type 802.1qbg :
https://wiki.openstack.org/wiki/Nova-neutron-sriov
Mathieu
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
