[ovs-discuss] What is the best way to map a VTEP flow to an internal port?

[Ben Pfaff]

On Tue, Sep 18, 2018 at 11:29:52AM -0600, Grant Taylor via discuss wrote:
> On 09/17/2018 10:29 PM, Ben Pfaff wrote:
> >Something like this?  I have not tested it.
> >
> >ovs-vsctl add-port br0 port0 -- set interface port0 type=internal -- set port port0 tag=100
> >ovs-vsctl add-port br0 port1 -- set interface port1 type=internal -- set port port1 tag=101
> >ovs-vsctl add-port br0 vtep0 -- set interface vtep0 type=vxlan options:remote_ip=192.0.2.1 options:key=100 tag=100
> >ovs-vsctl add-port br0 vtep1 -- set interface vtep1 type=vxlan options:remote_ip=192.0.2.1 options:key=101 tag=101
> 
> If I'm reading this correctly, it looks like you're assigning VLANs to
> (internal) ports and VTEPs.  Thus you are relying on VLANs.
> 
> Is there no way to assign a VNI directly to the (internal) port?

No.  A port can be an internal port or a vxlan port.  It can't be both.

> I don't foresee running out of VIDs per vSwitch.  But I'm being lazy and
> applying parsimony and would like to avoid VLANs if they aren't necessary.
> 
> I'd ideally like to apply options:key=123 to the (internal) port.  But I
> think that failed when I tried it.

Maybe you should use flows instead of OVSDB configuration.  Flows can
also direct packets from one port to another.  I guess that this would
be easy for a controller to set up.