[ovs-discuss] Geneve remote_ip as flow for OVN hosts

[Girish Moodalbail]

Hello all,

I would like to add more context here. In the diagram below

+----------------------------------+
|ovn-host                          |
|                                  |
|                                  |
|       +-------------------------+|
|       |         br-int          ||
|       +----+-------------+------+|
|            |             |       |
|         +--v-----+   +---v----+  |
|         | geneve |   | geneve |  |
|         +--+-----+   +---+----+  |
|            |             |       |
|          +-v----+     +--v---+   |
|          | IP0  |     | IP1  |   |
|          +------+     +------+   |
+----------+ eth0 +-----+ eth1 +---+
           +------+     +------+

eth0 and eth are, say, in its own physical segments. The VMs that are
instantiated in the above ovn-host will have multiple interfaces and each
of those interface need to be on a different Geneve VTEP.

I think the following entry in OVN TODOs (
https://github.com/openvswitch/ovs/blob/master/ovn/TODO.rst)

---------------8<------------------8<---------------
Support multiple tunnel encapsulations in Chassis.

So far, both ovn-controller and ovn-controller-vtep only allow chassis to
have one tunnel encapsulation entry. We should extend the implementation to
support multiple tunnel encapsulations
---------------8<------------------8<---------------

captures the above requirement. Is that the case?

Thanks again.

Regards,
~Girish




On Tue, Sep 4, 2018 at 3:00 PM Girish Moodalbail <gmoodalbail at gmail.com>
wrote:

> Hello all,
>
> Is it possible to configure remote_ip as a 'flow' instead of an IP address
> (i.e., setting ovn-encap-ip to a single IP address)?
>
> Today, we have one VTEP endpoint per OVN host and all the VMs that
> connects to br-int  on that OVN host are reachable behind this VTEP
> endpoint. Is it possible to have multiple VTEP endpoints for a br-int
> bridge and use Open Flow flows to select one of the VTEP endpoint?
>
>
> +----------------------------------+
> |ovn-host                          |
> |                                  |
> |                                  |
> |       +-------------------------+|
> |       |         br-int          ||
> |       +----+-------------+------+|
> |            |             |       |
> |         +--v-----+   +---v----+  |
> |         | geneve |   | geneve |  |
> |         +--+-----+   +---+----+  |
> |            |             |       |
> |          +-v----+     +--v---+   |
> |          | IP0  |     | IP1  |   |
> |          +------+     +------+   |
> +----------+ eth0 +-----+ eth1 +---+
>            +------+     +------+
>
> Also, we don't want to bond eth0 and eth1 into a bond interface and then
> use bond's IP as VTEP endpoint.
>
> Thanks in advance,
> ~Girish
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.openvswitch.org/pipermail/ovs-discuss/attachments/20180905/7b164293/attachment-0001.html>