[ovs-discuss] [ovn] Port bindings to network
Ben Pfaff
blp at nicira.com
Mon Oct 12 17:30:40 UTC 2015
On Mon, Oct 12, 2015 at 12:14:58PM -0500, Murali R wrote:
> In other words, where is local vlan id per network stored in southbound db?
> Apparently ovn-sb.xml says:
>
> <p>
> When <ref column="type"/> is set to <code>localnet</code>, this can be
> set to indicate that the port represents a connection to a specific
> VLAN on a locally accessible network. The VLAN ID is used to match
> incoming traffic and is also added to outgoing traffic.
> </p>
>
> And as seen in email above, the type field is left empty. I could not find
> the mapping in any other published sb-db schema. So not sure where it is.
This documentation was recently reorganized for clarity. The new
version says the following.
--8<--------------------------cut here-------------------------->8--
Localnet Options:
These options apply to logical ports with type of localnet.
options : network_name: optional string
Required. ovn-controller uses the configuration entry
ovn-bridge-mappings to determine how to connect to this network.
ovn-bridge-mappings is a list of network names mapped to a local
OVS bridge that provides access to that network. An example of
configuring ovn-bridge-mappings would be:
$ ovs-vsctl set open . external-ids:ovn-bridge-mappings=physnet1:br-eth0,physnet2:br-eth1
When a logical switch has a localnet port attached, every chas‐
sis that may have a local vif attached to that logical switch
must have a bridge mapping configured to reach that localnet.
Traffic that arrives on a localnet port is never forwarded over
a tunnel to another chassis.
tag: optional integer, in range 1 to 4,095
If set, indicates that the port represents a connection to a
specific VLAN on a locally accessible network. The VLAN ID is
used to match incoming traffic and is also added to outgoing
traffic.
More information about the discuss
mailing list