OK, just to be clear, memif lets you pass L2 or L3 packets... but it does not provide a TCP stack (if you need a TCP stack, we have one of those too :) ).
Ed On Sun, May 27, 2018 at 2:02 AM Sara Gittlin <sara.gitt...@gmail.com> wrote: > Ed, > there are some use-cases , for example: > - 2 work loads under same tenant - need to exchange info > - CNF's implementing SFC > Thank you > -Sara > > > On Thu, May 24, 2018 at 7:12 PM, Ed Warnicke <hagb...@gmail.com> wrote: > >> Sara, >> >> A couple question: >> >> What are you wanting to connect via memif in your containers? Is it a >> CNF (Cloud-native Network Function... ie something meant to process >> packets) or a traditional app (think webserver, databace, etc)? >> >> Ed >> >> On Thu, May 24, 2018 at 3:37 AM Sara Gittlin <sara.gitt...@gmail.com> >> wrote: >> >>> Hello All, >>> I've followed the example as per >>> https://docs.fd.io/vpp/17.10/libmemif_doc.html . >>> everything works fine. >>> My question is how to connect 2 containers where the container image is >>> a common image [not necessarily libmemif-sample-service] ? >>> what to install ? how to create the memif interface ? connect ? >>> in the vpp example - we create the interface in vpp and connect in the >>> container daemon with the specific image 'conn' command. >>> i understand that memif is a feature under VPP although VPP is not >>> required for containers interconect >>> >>> Thank you >>> -Sara >>> >>> >>> >
