[Openstack] [openstack][neutron] multiple vlan provider and tenant networks?

Kevin Benton kevin at benton.pub
Fri May 26 10:18:27 UTC 2017


Yep!

On May 26, 2017 3:17 AM, <vladislav.belogrudov at oracle.com> wrote:

> Thanks Kevin!
>
> so I can mix and match tenant and provider vlans now.
>
> Vladislav
>
> On 05/26/2017 11:48 AM, Kevin Benton wrote:
>
> assuming 'vlan' is in tenant_network_types, it will go through the
> network_vlan_ranges you have defined. Since you haven't provided a range
> for provider0 or provider1, it will not automatically allocate from those.
>
> It will only automatically allocate from the two you have provided ranges
> for (tenant-vlan2 and tenant-vlan3).
>
> On Wed, May 10, 2017 at 2:22 AM, <vladislav.belogrudov at oracle.com> wrote:
>
>> Hi,
>>
>> I wonder if it is possible to use multiple network interfaces / bridge
>> mappings for VLAN tenants and providers at the same time.  E.g. in case of
>> 1 VLAN network for tenant and 1 external VLAN how does neutron bridge
>> mapping work? User interface does not allow to specify the mapping.
>>
>> Example: 2 external VLAN interfaces and 2 tenant ones. In this case
>> neutron configuration would be:
>>
>> [ml2_type_vlan]
>> network_vlan_ranges = provider0,provider1,tenant-vlan2:200:299,tenant-
>> vlan3:300:399
>>
>> [ovs]
>> bridge_mappings = provider0:br-ext0,provider1:br-ext1,tenant-vlan2:br-
>> vlan2,tenant-vlan3:br-vlan3
>>
>> How can neutron decide on choosing correct vlan mapping for tenant? Will
>> it pick provider0 if normal user creates a tenant network?
>>
>> Thanks,
>> Vladislav
>>
>> _______________________________________________
>> Mailing list: http://lists.openstack.org/cgi
>> -bin/mailman/listinfo/openstack
>> Post to     : openstack at lists.openstack.org
>> Unsubscribe : http://lists.openstack.org/cgi
>> -bin/mailman/listinfo/openstack
>>
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20170526/76a22bc1/attachment.html>


More information about the Openstack mailing list