Open Stack

Hi,

if you use a VLAN type driver, TOR switches should be configured in
trunk mode to allow VLAN specified in vlan_type section of
ml2_conf.ini.
vlan id range is defined in this section. Any tenant network will use
an id from this range, and it is totally independent from tenant id.
Some mechanism drivers should allow you to automatically configure the
TOR switch with the correct vlan ID in the trunk port connected to
compute nodes.

when you create a port, traffic from this port will use the vlan tag
from the network which owns this port.

Hope this help

On Wed, Oct 15, 2014 at 7:18 PM, Ettore zugliani
<ettorezugliani at gmail.com> wrote:
> Hi, I've got a few questions that have been left unanswered on Ask.Openstack
> and on the IRC channel.
>
> How the topology may be affected by the ML2 API calls? In other words, how
> would a "Create Network" call affect the actual topology? How is it
> controlled?
>
> An example: Once we receive a "Create Network" ML2 API call we don't know
> how exactly it reflects on ANY switch configuration. Supposing that we
> received a create_network with the tenant_id = tid and we are using the
> TypeDriver VLAN, should we create a VLAN on the swtich with vid = tid?
>
> On a create_port API call should we add a specifc port -manually- to this
> vlan? Another thing that comes to mind is that if is there a default port or
> do we get the correct port from Neutron context?
>
> Thank you
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>