On 09/27/2015 06:50 AM, Kevin Benton wrote: > Assuming it implements the normal provider networks API, you just > specify the segmentation_id when you create the network. > > neutron net-create NET_NAME --provider:network_type vlan > --provider:physical_network physnet1 --provider:segmentation_id VLAN_TAG
Yes, the OVN plugin will implement the normal provider networks API. It's a WIP. My first goal was to just implement support for "--provider:network_type flat" end to end. I have the OVN side merged and now I'm working on the Neutron plugin piece. Once that's done, I'll go back add add VLAN support, which shouldn't be very difficult at that point. I'm aiming to have all of that done by the Tokyo summit (among other things). > On Sun, Sep 27, 2015 at 9:50 AM, WANG, Ming Hao (Tony T) > <tony.a.w...@alcatel-lucent.com <mailto:tony.a.w...@alcatel-lucent.com>> > wrote: > > Russell, > > Another question is about "localnet". It is a very useful feature. :-) > > Is it possible to assign which VLAN tag will be used for a specific > provider network? > In your example in > > https://github.com/openvswitch/ovs/commit/c02819293d52f7ea7b714242d871b2b01f57f905 > : "physnet1" is used as physical network, and br-eth1 is used as the > provider network OpenFlow switch. > If we can assign the VLAN tag of the provider network, is the VLAN > tag translation done by "br-int" or "br-eth1"? -- Russell Bryant __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
