<div dir="ltr">Russel,<div><br></div><div>For instance if I have a nsh header embedded in vxlan in the incoming packet, I was wondering if I can transfer that to geneve options somehow. This is just as an example. I may have header other info either in vxlan or ip that needs to enter the ovn network and if we have generic ovs commands to handle that, it will be useful. If commands don't exist but extensible then I can do that as well.</div><div><br></div><div> </div><div><br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Sep 30, 2015 at 12:49 PM, Russell Bryant <span dir="ltr"><<a href="mailto:rbryant@redhat.com" target="_blank">rbryant@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 09/30/2015 03:29 PM, Murali R wrote:<br>
> Russell,<br>
><br>
> Are any additional options fields used in geneve between hypervisors at<br>
> this time? If so, how do they translate to vxlan when it hits gw? For<br>
> instance, I am interested to see if we can translate a custom header<br>
> info in vxlan to geneve headers and vice-versa.<br>
<br>
</span>Yes, geneve options are used. Specifically, there are three pieces of<br>
metadata sent: a logical datapath ID (the logical switch, or network),<br>
the source logical port, and the destination logical port.<br>
<br>
Geneve is only used between hypervisors. VxLAN is only used between<br>
hypervisors and a VTEP gateway. In that case, the additional metadata is<br>
not included. There's just a tunnel ID in that case, used to identify<br>
the source/destination logical switch on the VTEP gateway.<br>
<span class=""><br>
> And if there are flow<br>
> commands available to add conditional flows at this time or if it is<br>
> possible to extend if need be.<br>
<br>
</span>I'm not quite sure I understand this part. Could you expand on what you<br>
have in mind?<br>
<div class="HOEnZb"><div class="h5"><br>
--<br>
Russell Bryant<br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</div></div></blockquote></div><br></div>