<html><head></head><body><div></div>
<div>Sorry for the resend, I am not sure how the pictures will render in the text doc, so am attaching the PDF too.</div><div><br></div><div>thanks,</div><div><br></div><div>-venu</div><div><br></div><div><br></div>
<div id="ydpc78516a1yahoo_quoted_4166893276" class="ydpc78516a1yahoo_quoted">
<div style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:13px;color:#26282a;">
<div>
On Thursday, November 29, 2018, 9:26:54 AM PST, venugopal iyer <iyervl@ymail.com> wrote:
</div>
<div><br></div>
<div><br></div>
<div><div class="ydpdf50a7beyahoo-style-wrap" style="font-family: Helvetica Neue, Helvetica, Arial, sans-serif; font-size: 13px;"><div></div>
<div>Thanks, Ben. <br></div><div><br></div><div>Sorry for the delay. Please find attached a draft design proposal and let me know your comments etc. I did some quick <br></div><div>prototyping to check for feasibility too; I can share that, if it helps.</div><div><br></div><div>Note, the document is a draft and, I admit, there might be things that I haven't thought about/through, or missed. I am <br></div><div>attaching a text doc, assuming it might be easier, but if you'd like it in a different format, please let me know.<br></div><div><br></div><div>thanks!</div><div><br></div><div>-venu<br></div><div><br></div>
</div><div id="ydp6790db3cyahoo_quoted_3638930920" class="ydp6790db3cyahoo_quoted">
<div style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:13px;color:#26282a;">
<div>
On Wednesday, October 31, 2018, 10:30:23 AM PDT, Ben Pfaff <blp@ovn.org> wrote:
</div>
<div><br></div>
<div><br></div>
<div>Honestly the best thing to do is probably to propose a design or, if<br clear="none">it's simple enough, to send a patch. That will probably be more<br clear="none">effective at sparking a discussion.<br clear="none"><div class="ydp6790db3cyqt5214898655" id="ydp6790db3cyqtfd25185"><br clear="none">On Wed, Oct 31, 2018 at 03:33:48PM +0000, venugopal iyer wrote:<br clear="none">> Hi:<br clear="none">> Just wanted to check if folks had any thoughts on the use case Girish outlined below. We do have<br clear="none">> a real use case for this and are interested in looking at options for supporting more than one VTEP IP.It is currently a limitation for us, wanted to know if there are similar use cases folks are looking at/interested in addressing.<br clear="none">> <br clear="none">> thanks,<br clear="none">> -venu<br clear="none">> <br clear="none">> On Thursday, September 6, 2018, 9:19:01 AM PDT, venugopal iyer via dev <<a shape="rect" href="mailto:ovs-dev@openvswitch.org" rel="nofollow" target="_blank">ovs-dev@openvswitch.org</a>> wrote: <br clear="none">> <br clear="none">> Would it be possible for the association <logical port|dst MAC, VTEP> to be made<br clear="none">> when the logical port is instantiated on a node? and relayed on to the SB by<br clear="none">> the controller, e.g. assuming a mechanism to specify/determine a physical port mapping for a<br clear="none">> logical port for a VM. The <physical port,encap-ip> mappings can be specified as<br clear="none">> configuration on the chassis. In the absence of physical port information for<br clear="none">> a logical port/VM, I suppose we could default to an encap-ip.<br clear="none">> <br clear="none">> <br clear="none">> just a thought,<br clear="none">> -venu<br clear="none">> On Wednesday, September 5, 2018, 2:03:35 PM PDT, Ben Pfaff <<a shape="rect" href="mailto:blp@ovn.org" rel="nofollow" target="_blank">blp@ovn.org</a>> wrote: <br clear="none">> <br clear="none">> How would OVN know which IP to use for a given logical port on a<br clear="none">> chassis?<br clear="none">> <br clear="none">> I think that the "multiple tunnel encapsulations" is meant to cover,<br clear="none">> say, Geneve vs. STT vs. VXLAN, not the case you have in mind.<br clear="none">> <br clear="none">> On Wed, Sep 05, 2018 at 09:50:32AM -0700, Girish Moodalbail wrote:<br clear="none">> > Hello all,<br clear="none">> > <br clear="none">> > I would like to add more context here. In the diagram below<br clear="none">> > <br clear="none">> > +----------------------------------+<br clear="none">> > |ovn-host |<br clear="none">> > | |<br clear="none">> > | |<br clear="none">> > | +-------------------------+|<br clear="none">> > | | br-int ||<br clear="none">> > | +----+-------------+------+|<br clear="none">> > | | | |<br clear="none">> > | +--v-----+ +---v----+ |<br clear="none">> > | | geneve | | geneve | |<br clear="none">> > | +--+-----+ +---+----+ |<br clear="none">> > | | | |<br clear="none">> > | +-v----+ +--v---+ |<br clear="none">> > | | IP0 | | IP1 | |<br clear="none">> > | +------+ +------+ |<br clear="none">> > +----------+ eth0 +-----+ eth1 +---+<br clear="none">> > +------+ +------+<br clear="none">> > <br clear="none">> > eth0 and eth are, say, in its own physical segments. The VMs that are<br clear="none">> > instantiated in the above ovn-host will have multiple interfaces and each<br clear="none">> > of those interface need to be on a different Geneve VTEP.<br clear="none">> > <br clear="none">> > I think the following entry in OVN TODOs (<br clear="none">> > <a shape="rect" href="https://github.com/openvswitch/ovs/blob/master/ovn/TODO.rst" rel="nofollow" target="_blank">https://github.com/openvswitch/ovs/blob/master/ovn/TODO.rst</a>)<br clear="none">> > <br clear="none">> > ---------------8<------------------8<---------------<br clear="none">> > Support multiple tunnel encapsulations in Chassis.<br clear="none">> > <br clear="none">> > So far, both ovn-controller and ovn-controller-vtep only allow chassis to<br clear="none">> > have one tunnel encapsulation entry. We should extend the implementation to<br clear="none">> > support multiple tunnel encapsulations<br clear="none">> > ---------------8<------------------8<---------------<br clear="none">> > <br clear="none">> > captures the above requirement. Is that the case?<br clear="none">> > <br clear="none">> > Thanks again.<br clear="none">> > <br clear="none">> > Regards,<br clear="none">> > ~Girish<br clear="none">> > <br clear="none">> > <br clear="none">> > <br clear="none">> > <br clear="none">> > On Tue, Sep 4, 2018 at 3:00 PM Girish Moodalbail <<a shape="rect" href="mailto:gmoodalbail@gmail.com" rel="nofollow" target="_blank">gmoodalbail@gmail.com</a>><br clear="none">> > wrote:<br clear="none">> > <br clear="none">> > > Hello all,<br clear="none">> > ><br clear="none">> > > Is it possible to configure remote_ip as a 'flow' instead of an IP address<br clear="none">> > > (i.e., setting ovn-encap-ip to a single IP address)?<br clear="none">> > ><br clear="none">> > > Today, we have one VTEP endpoint per OVN host and all the VMs that<br clear="none">> > > connects to br-int on that OVN host are reachable behind this VTEP<br clear="none">> > > endpoint. Is it possible to have multiple VTEP endpoints for a br-int<br clear="none">> > > bridge and use Open Flow flows to select one of the VTEP endpoint?<br clear="none">> > ><br clear="none">> > ><br clear="none">> > > +----------------------------------+<br clear="none">> > > |ovn-host |<br clear="none">> > > | |<br clear="none">> > > | |<br clear="none">> > > | +-------------------------+|<br clear="none">> > > | | br-int ||<br clear="none">> > > | +----+-------------+------+|<br clear="none">> > > | | | |<br clear="none">> > > | +--v-----+ +---v----+ |<br clear="none">> > > | | geneve | | geneve | |<br clear="none">> > > | +--+-----+ +---+----+ |<br clear="none">> > > | | | |<br clear="none">> > > | +-v----+ +--v---+ |<br clear="none">> > > | | IP0 | | IP1 | |<br clear="none">> > > | +------+ +------+ |<br clear="none">> > > +----------+ eth0 +-----+ eth1 +---+<br clear="none">> > > +------+ +------+<br clear="none">> > ><br clear="none">> > > Also, we don't want to bond eth0 and eth1 into a bond interface and then<br clear="none">> > > use bond's IP as VTEP endpoint.<br clear="none">> > ><br clear="none">> > > Thanks in advance,<br clear="none">> > > ~Girish<br clear="none">> > ><br clear="none">> > ><br clear="none">> > ><br clear="none">> > ><br clear="none">> <br clear="none">> > _______________________________________________<br clear="none">> > discuss mailing list<br clear="none">> > <a shape="rect" href="mailto:discuss@openvswitch.org" rel="nofollow" target="_blank">discuss@openvswitch.org</a><br clear="none">> > <a shape="rect" href="https://mail.openvswitch.org/mailman/listinfo/ovs-discuss" rel="nofollow" target="_blank">https://mail.openvswitch.org/mailman/listinfo/ovs-discuss</a><br clear="none">> <br clear="none">> _______________________________________________<br clear="none">> dev mailing list<br clear="none">> <a shape="rect" href="mailto:dev@openvswitch.org" rel="nofollow" target="_blank">dev@openvswitch.org</a><br clear="none">> <a shape="rect" href="https://mail.openvswitch.org/mailman/listinfo/ovs-dev" rel="nofollow" target="_blank">https://mail.openvswitch.org/mailman/listinfo/ovs-dev</a><br clear="none">> <br clear="none">> _______________________________________________<br clear="none">> dev mailing list<br clear="none">> <a shape="rect" href="mailto:dev@openvswitch.org" rel="nofollow" target="_blank">dev@openvswitch.org</a><br clear="none">> <a shape="rect" href="https://mail.openvswitch.org/mailman/listinfo/ovs-dev" rel="nofollow" target="_blank">https://mail.openvswitch.org/mailman/listinfo/ovs-dev</a><br clear="none">><span><div>too, I can share that if it helps.</div><div><br></div></span> <br clear="none"></div></div>
</div>
</div></div>
</div>
</div></body></html>