Reviewed: https://review.openstack.org/333379 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=8a596f35bb70a2c8ab48f68327662310141bb518 Submitter: Jenkins Branch: master
commit 8a596f35bb70a2c8ab48f68327662310141bb518 Author: Jiri Kotlin <[email protected]> Date: Thu Jun 23 14:04:07 2016 +0000 VXLAN multicast groups in linuxbridge Enable creation of VXLANs with different multicast addresses allocated by VNI-address mappings. Dictionary of multicast addresses and corresponding VXLAN VNI IDs should be loaded from settings. Usable to not flood whole network when managing routers between more datacenters and can not use L2population because VXLAN points to external device. Co-Authored-By: Kevin Benton <[email protected]> DocImpact: VXLAN addresses used by linux bridge can be specified per VNI Closes-Bug: #1579068 Change-Id: I24f272ccd6d61d9fa7ea3b6f256fabd381f5434a ** Changed in: neutron Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1579068 Title: [RFE] VXLAN multicast groups distribution in linuxbridge Status in neutron: Fix Released Bug description: Enable creation of VXLANs with different multicast addresses allocated by VNI-address mappings. Dictionary of multicast addresses and corresponding VXLAN VNI IDs should be loaded from settings. Option vxlan_group supports multiple addrresses via CIDR, but our goal is to have the ability to control vni-multicast address distribution somehow, not randomly, not straightforward mapping. Usable to not flood whole network when managing routers between more datacenters and can not use L2population because VXLAN points to external device (outside OpenStack). Real example: 2 data centers connected with VLANs, both with Cisco ASR-9K on L3. Routers have its own vni-multicast group mappings: Router(config-if)# member vni 6010-6030 multicast-group 225.1.1.1 Router(config-if)# member vni 8000-9030 multicast-group 225.2.2.1 etc. So we can create network with vni i.e. 6011 and it will get right multicast address 225.1.1.1 or vni 8000 with vni 225.2.2.1 etc. We also need to create networks on demand and not configure routers at each change. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1579068/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
