Open Stack

Thanks for the answer, but I mean the ordinary user who tries to create a
tenant network from, for example, Horizon without knowing the name of the
physical interfaces.

Similar to vlxan and gre, Can Neutron automatically manage the VLAN ID and
the relationship with physnet2 when a normal user create a "tenant" network?

El sáb., 5 mar. 2016 a las 22:32, Francisco J. Araya (<francisco at sentinel.la>)
escribió:

> Hi Sergio, which OpenStack Version are you deploying? Have you tried this
> guide?
>
>
> http://docs.openstack.org/liberty/networking-guide/scenario-provider-ovs.html
>
> Regards,
>
>
> FJA
>
> Sent from mobile device
>
> > On Mar 5, 2016, at 6:59 PM, Sergio Morales Acuña <semoac at gmail.com>
> wrote:
> >
> > Hi,
> >
> > After reading the documentation Neutron I failed to understand how to
> configure ML2 to use a particular interface when creating VLANs for
> projects.
> >
> > For example, in this configuration:
> > [mL2]
> > local type_drivers = loca, flat, vlan, gre, vxlan
> > tenant_network_types = vlan
> > [ml2_type_vlan]
> > network_vlan_ranges = physnet2: 1000: 1200, physnet1
> > [ovs]
> > bridge_mappings = physnet2: br-vlan, physnet1: br-ex
> >
> > How I can set "Neutron" to use the interface "physnet2" when a user
> creates an internal network?
> >
> > Am I forgetting another configuration? or the order is enough?
> >
> > Thanks
> > _______________________________________________
> > 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/20160306/ffc0693c/attachment.html>