Thanks, sorry, needed to reply all, yes, that would work, but unfortunately, I am not able to deploy OvS into the VMs. For one of the VMs it is provided by a third-party and it is expecting VxLAN, and in the other VM, it runs a proprietary OS which works with qemu/KVM and no hope of getting OvS up and running in it. So, i need to entirely construct this on the Host, something like: NIC <-> OvS Bridge (encap) <-> VxLAN <-> VM <-> VxLAN <-> (decap) OvS Bridge <-> VM. Perhaps a custom vSwitch with DPDK would be more appropriate? Thanks!
On Thu, Jun 8, 2017 at 2:04 PM, Greg Rose <[email protected]> wrote: > On 06/08/2017 06:49 AM, Mark McConnaughay wrote: > >> Thanks Greg. I am working on an 'NFV' project which has a requirement to >> maintain the entire packet (L2 and up) on reception from the NIC, forward >> to an 'on-box' VM and then forward to either another on-box VM or another >> VM on another physical box. The only way I can think of doing this is to >> encapsulate the entire frame/packet in something like VxLAN. I know it's an >> odd use case but it is what it is. I'd prefer to get this working with OvS >> rather than craft our own vSwitch with DPDK. We are using OvS with DPDK. It >> looks like it should be possible with OvS but I haven't been able to figure >> it out so any guidance on how to do it or any indication that it isn't >> really possible without significant 'shimming' of OvS constructs would be >> greatly appreciated. >> Thanks, >> - Mark >> > > Please don't drop the list... > > Well Vxlan communicates across a standard IP based connection. So I would > create two VMs and deploy OVS bridges > in each VM and then set up the standard VXLAN connection between the two. > There's no reason you can't run Open > vSwitch in a VM. > > VM1 <---> ovs bridge <---> VXLAN (ip 10.0.0.1) <---> VXLAN (ip 10.0.0.2) > <---> ovs bridge <--->VM2 > > Something like this maybe? > > - Greg > > >> On Wed, Jun 7, 2017 at 7:26 PM, Greg Rose <[email protected] <mailto: >> [email protected]>> wrote: >> >> On 06/07/2017 08:01 AM, Mark McConnaughay wrote: >> >> Hi, we have a use case to use OvS with VxLAN tunneling to a VM on >> the same box. >> It seems like this should work but I'm not able to configure it >> in OvS. >> I've been able to construct VxLAN tunneling b/w two OvS instances >> on two different machines and have VMs ping each other as >> is the normal use case and for tunneling to an on-box VM I've >> tried using an internal/isolated bridge with no physical >> ports, but to no avail. Any suggestions on how to accomplish this >> or if it is even possible? Thanks. >> >> >> What is the use case for this? The purpose of vxlan and other >> tunneling protocols is to make >> physically distributed networks all appear to the user like they're >> on the same subnet. If both VMs >> are in the same 'box' (i.e. physical machine) then they can talk >> across a local bridge. Is it just >> for testing/development purposes? >> >> Thanks, >> >> - Greg >> >> >> >> _______________________________________________ >> discuss mailing list >> [email protected] <mailto:[email protected]> >> https://mail.openvswitch.org/mailman/listinfo/ovs-discuss < >> https://mail.openvswitch.org/mailman/listinfo/ovs-discuss> >> >> >> _______________________________________________ >> discuss mailing list >> [email protected] <mailto:[email protected]> >> https://mail.openvswitch.org/mailman/listinfo/ovs-discuss < >> https://mail.openvswitch.org/mailman/listinfo/ovs-discuss> >> >> >> >
_______________________________________________ discuss mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
