Re: Mesos (and Marathon) port mapping

Hello, sorry to insist, is the understanding below correct ? I'm really not sure. I understand that network/portmapping isolator is using disjoint port ranges to multiplex traffic into the same ports into containers but I'm not really sure if we're talking about ephemeral or non-ephemeral port

Re: Mesos (and Marathon) port mapping

On Fri, Apr 7, 2017 at 6:36 AM, Thomas HUMMEL wrote: > On 03/31/2017 07:51 PM, Jie Yu wrote: > >> Tomek and Olivier, >> >> The bridge network support (with port mapping) has been added to Mesos >> 1.2. See this doc for more details how to use it: >> https://github.com/apache/mesos/blob/master/doc

Re: Mesos (and Marathon) port mapping

On 03/31/2017 07:51 PM, Jie Yu wrote: Tomek and Olivier, The bridge network support (with port mapping) has been added to Mesos 1.2. See this doc for more details how to use it: https://github.com/apache/mesos/blob/master/docs/cni.md#a-port-mapper-plugin-for-cni-networks TL;DR: we developed a

Re: Mesos (and Marathon) port mapping

Ok, thanks. So if I wrap my head around all of this and try to answer my original question I come up with the following understanding : - servicePorts a a Marathon only concept - port mapping isolator is not compatible with docker containerizer - port mapping isolator is useful when you cann

Re: Mesos (and Marathon) port mapping

Thomas, - it is the hostports which are used to multiplex traffic into container. > My understanding is that, since each container is in it's network > namespace, it has its own full range of container ports and that you use a > direct mapping (hostport n <-> same container port n), is that correc

Re: Mesos (and Marathon) port mapping

Tomek and Olivier, The bridge network support (with port mapping) has been added to Mesos 1.2. See this doc for more details how to use it: https://github.com/apache/mesos/blob/master/docs/cni.md#a-port-mapper-plugin-for-cni-networks TL;DR: we developed a CNI port mapper plugin (DNAT) in Mesos re

Re: Mesos (and Marathon) port mapping

On 03/31/2017 10:23 AM, Tomek Janiszewski wrote: > I have a question that is related to this topic. In "docker support > and current limitations" section [1] there is a following statement: > > Only host network is supported. We will add bridge network support > soon using CNI support in Mesos (M

Re: Mesos (and Marathon) port mapping

Thanks for your answer, I've watched your talk. Very interesting. Let me check if I get everything staight : - it is the hostports which are used to multiplex traffic into container. My understanding is that, since each container is in it's network namespace, it has its own full range of cont

Re: Mesos (and Marathon) port mapping

I have a question that is related to this topic. In "docker support and current limitations" section [1] there is a following statement: > Only host network is supported. We will add bridge network support soon using CNI support in Mesos (MESOS-4641

Re: Mesos (and Marathon) port mapping

> > are you talking about the NAT feature of docker in BRIDGE m Yes - regarding the "port mapping isolator giving network namespace" : what > confuses me is that, given the previous answers, I thought that in that > case, the non-ephemeral port range was *shared* (as a ressource) between > cont

Re: Mesos (and Marathon) port mapping

On 03/29/2017 07:25 PM, Jie Yu wrote: Thomas, I think you are confused about the port mapping for NAT purpose, and the port mapping isolator . Those two very different thing. The port mapping isolator (unfortunate naming),

Re: Mesos (and Marathon) port mapping

Thomas, I think you are confused about the port mapping for NAT purpose, and the port mapping isolator . Those two very different thing. The port mapping isolator (unfortunate naming), as described in the doc, gives you network n

Re: Mesos (and Marathon) port mapping

On 03/29/2017 01:21 PM, Dick Davies wrote: I should say this was tested around mesos 1.0, they may have changed things - but yes this is vanilla networking, no CNI or anything like that. As a matter of fact, that's what I experience. But I'm guessing if you're using BRIDGE networking and sp

Re: Mesos (and Marathon) port mapping

I should say this was tested around mesos 1.0, they may have changed things - but yes this is vanilla networking, no CNI or anything like that. But I'm guessing if you're using BRIDGE networking and specifying a hostPort: you're causing work for yourself (unless you actually care what port the sla

Re: Mesos (and Marathon) port mapping

Also, does network/portmapping isolator makes sense if the containerizer is docker ?

Re: Mesos (and Marathon) port mapping

On 03/28/2017 06:53 PM, Tomek Janiszewski wrote: 1. Mentioned port range is the Mesos Agent resource setting, so if you don't explicitly define port range it would be used. https://github.com/apache/mesos/blob/1.2.0/src/slave/constants.hpp#L86 2. With ports mapping two or more applications c

Re: Mesos (and Marathon) port mapping

Try setting your hostPort to 0, to tell Mesos to select one (which it will allocate out of the pool the mesos slave is set to use). This works for me for redis: { "container": { "type": "DOCKER", "docker": { "image": "redis", "network": "BRIDGE", "portMappings": [

Re: Mesos (and Marathon) port mapping

1. Mentioned port range is the Mesos Agent resource setting, so if you don't explicitly define port range it would be used. https://github.com/apache/mesos/blob/1.2.0/src/slave/constants.hpp#L86 2. With ports mapping two or more applications could attach to same container port but will be exposed

Mesos (and Marathon) port mapping

Hello, [Sorry if this post may seem more Marathon-oriented. It still contains Mesos specific questions.] I'm in the process of discovering/testing/trying to understand Mesos and Marathon. After having read some books and docs, I set up a small environment (9 linux CentOS 7.3 VMs) consisting