[Openstack-Ansible] br-vlan configuration and intended usage?

Jonathan Rosser jonathan.rosser at rd.bbc.co.uk
Mon Jul 11 07:34:19 UTC 2022

If you choose to use vxlan for your tenant networks (the default in OSA) 
you would probably be using a vlan for the external provider network.

This would default to br-vlan, but alternatively can be any interface of 
your choice. With the default configuration br-vlan would need to be 
present on all of your controller (or dedicated network) nodes and carry 
the tagged external vlan from your upstream switches.


On 10/07/2022 07:57, Dmitriy Rabotyagov wrote:
> Hi Dave,
> Intended use-case for br-vlan is when you want or need to provide vlan 
> networks in the environment.
> As example, we use vlan networks to bring in customers owned public 
> networks, as we need to pass vlan from the gateway to the compute 
> nodes, and we are not able to set vxlan on the gateway due to hardware 
> that is used there.
> At the same time in many environments you might not need using vlans 
> at all, as vxlan is what will be used by default to provide tenant 
> networks.
> сб, 9 июл. 2022 г., 23:44 Dave Hall <kdhall at binghamton.edu>:
>     Hello.
>     I'm preparing to do my first deployment (of Yoga) on
>     real hardware.  The documentation regarding br-vlan was hard for
>     me to understand.   Could I get a clarification on what to do with
>     this?
>     Note:  my intended use case is as an academic/instructional
>     environment.  I'm thinking along the lines of treating each
>     student as a separate tenant that would be preconfigured with
>     templated set of VMs appropriate to the course content.
>     Any other thoughts regarding this scenario would also be greatly
>     appreciated.
>     Thanks.
>     -Dave
>     --
>     Dave Hall
>     Binghamton University
>     kdhall at binghamton.edu
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.openstack.org/pipermail/openstack-discuss/attachments/20220711/96ce49a7/attachment.htm>

More information about the openstack-discuss mailing list