I am unfortunately not very up-to-date with Mesos, but I reckon it is fair to assume that in the current status N/S connectivity to containers should be handled outside of mesos infrastructure, ie: OVN can define a topology that enables external users to reach the LSPs in the LS specified in the CNI network Mesos uses.
On another note, it might also worth trying to understand whether we can have a single CNI plugin for all the frameworks that use CNI. We have another CNI plugin in openvswitch/ovn-kubernetes, and there's quite a bit of duplication with this one already. Salvatore On 6 December 2016 at 17:43, Ben Pfaff <[email protected]> wrote: > On Tue, Dec 06, 2016 at 07:55:36AM -0800, Guru Shetty wrote: > > On 5 December 2016 at 13:59, Ben Pfaff <[email protected]> wrote: > > > > > Guru, did you ever have a look at this? It's always nice to integrate > > > with more systems. > > > > > > > Right. I did work with Nimay to get this patch sent to the mailing list > as > > a RFC. The main reason it was a RFC was because of the following: > > > > > +Note on North-South traffic > > > +=========================== > > > + > > > +As of now, Mesos does not support port-mapping. As a result, we > cannot > > direct > > > +North-South traffic to the correct container. In the future, one > could > > imagine > > > +Mesos providing some sort of API to allow access to container-host > port > > > +mappings. These port mappings could be used to create load balancing > > rules to > > > +direct North-South traffic to the appopriate containers. > > > > I did check to see whether anything has changed in Mesos upstream and it > > did not look like they still provide any way to configure north-south > > traffic yet. > > Thanks, that makes sense. > _______________________________________________ > dev mailing list > [email protected] > https://mail.openvswitch.org/mailman/listinfo/ovs-dev > _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
