date:20171211

Re: Dedicated ip to task

2017-12-11 Thread Avinash Sridharan

Hi Marc,
 In that demo since we new that those were the only containers that were
getting launched, and the containers are getting launched on a bridge
network using a `host-local` IPAM the ip-addresses were predictable.

However, in a real setup you would probably need to rely on something like
`mesos-dns` to peg your backend to a DNS name rather than an IP address.
The DNS name will be predictable and DNS resolution would end up resolving
to the right backend.

If you are looking at Marathon + Mesos, the same can be achieved by
`marathon-lb` (https://github.com/mesosphere/marathon-lb). The limitation
here being that `marathon-lb` will peg against Marathon tasks rather than
Mesos tasks. So if you want use your own Mesos frameworks to launch tasks
that need to be load-balanced you won't be able to use `marathon-lb`.

On Mon, Dec 11, 2017 at 3:37 PM, Jie Yu  wrote:

> + Avinash
>
> On Mon, Dec 11, 2017 at 2:21 PM, Marc Roos 
> wrote:
>
>>
>>
>> In this https://youtu.be/0UMCoojACOs?t=1737 cni video of Avinash
>> Sridharan, he has a haproxy setup with two webservers on different
>> networks. But how does he know what these ip adresses will be, so he can
>> configure them in the proxy?
>>
>>
>>
>>
>>
>

-- 
Avinash Sridharan, Mesosphere
+1 (323) 702 5245

Re: cni macvlan config

2017-12-11 Thread Avinash Sridharan

On Mon, Dec 11, 2017 at 1:31 PM, Marc Roos  wrote:

>
> I think I have maybe a syntax error or so. On the other hand I also
> don’t see anything significant in the slave WARN, INFO and ERROR log.
>
>
> This one is not working. I can create a manually a macvlan interface at
> the host on eth0. And dhcp is running on this network.
> [@m01 ~]# cat  /etc/mesos-cni/15-cni-storagelan.conf
> {
>   "name": "cni-storagelan",
>   "type": "macvlan",
>   "master": "eth0",
>   "ipam": {
> "type": "host-local",
> "subnet": "192.168.10.0/24"
>   }
> }
>
> You need to provide communication between your container and the agent.
The executor within the container and the agent need to be able to register
with each other. This is done over IP. With a MacVLAN interface if you run
the agent on the master and the container on a slave, a master can never
talk to the slave ( the kernel won't allow it) hence the container launch
will fail due to a lack of registration. To use Macvlan make sure that the
agent is also listening on a slave interface having the same master as the
containers launched on that node.



> This one is working and giving the app an ip
> [@m01 ~]# cat  /etc/mesos-cni/30-cni-bridge-test.conf
> {
> "name": "cni-bridge-test",
> "type": "bridge",
> "bridge": "mesos-cni0",
> "isGateway": true,
> "ipam": {
> "type": "host-local",
> "subnet": "192.168.0.0/16",
> "routes": [
> { "dst":
>   "0.0.0.0/0" }
> ]
>   }
> }
>
> {
>   "id": "hello-play",
>   "cmd": "./Hello-*/bin/hello -Dhttp.port=80",
>   "cpus": 0.1,
>   "mem": 32,
>   "disk": 0,
>   "instances": 1,
>   "acceptedResourceRoles": [
> "*"
>   ],
>   "ipAddress": {"networkName": "cni-bridge-test"},
>   "uris": [
> "http://192.168.10.2/cobbler/PlayHello.zip";
>   ]
> }
>
>


-- 
Avinash Sridharan, Mesosphere
+1 (323) 702 5245

Re: Dedicated ip to task

2017-12-11 Thread Jie Yu

+ Avinash

On Mon, Dec 11, 2017 at 2:21 PM, Marc Roos  wrote:

>
>
> In this https://youtu.be/0UMCoojACOs?t=1737 cni video of Avinash
> Sridharan, he has a haproxy setup with two webservers on different
> networks. But how does he know what these ip adresses will be, so he can
> configure them in the proxy?
>
>
>
>
>

Dedicated ip to task

2017-12-11 Thread Marc Roos



In this https://youtu.be/0UMCoojACOs?t=1737 cni video of Avinash 
Sridharan, he has a haproxy setup with two webservers on different 
networks. But how does he know what these ip adresses will be, so he can 
configure them in the proxy?

December Performance Working Group Report

2017-12-11 Thread Benjamin Mahler

The December performance working group report is published on the website
here:
http://mesos.apache.org/blog/performance-working-group-progress-report/

This report highlights the progress we've made recently in the performance
of master failover. Special thanks to Dmitry Zhuk, Michael Park and Yan Xu
for the work in this area.

I didn't get time to write up something for the libprocess improvements, so
I decided to split that out into its own blog post.

I tweeted the above link here if you'd like to help us share it:
https://twitter.com/bmahler/status/940325681312940033

Ben

cni macvlan config

2017-12-11 Thread Marc Roos


I think I have maybe a syntax error or so. On the other hand I also 
don’t see anything significant in the slave WARN, INFO and ERROR log. 


This one is not working. I can create a manually a macvlan interface at 
the host on eth0. And dhcp is running on this network.
[@m01 ~]# cat  /etc/mesos-cni/15-cni-storagelan.conf
{
  "name": "cni-storagelan",
  "type": "macvlan",
  "master": "eth0",
  "ipam": {
"type": "host-local",
"subnet": "192.168.10.0/24"
  }
}

This one is working and giving the app an ip
[@m01 ~]# cat  /etc/mesos-cni/30-cni-bridge-test.conf
{
"name": "cni-bridge-test",
"type": "bridge",
"bridge": "mesos-cni0",
"isGateway": true,
"ipam": {
"type": "host-local",
"subnet": "192.168.0.0/16",
"routes": [
{ "dst":
  "0.0.0.0/0" }
]
  }
}

{
  "id": "hello-play",
  "cmd": "./Hello-*/bin/hello -Dhttp.port=80",
  "cpus": 0.1,
  "mem": 32,
  "disk": 0,
  "instances": 1,
  "acceptedResourceRoles": [
"*"
  ],
  "ipAddress": {"networkName": "cni-bridge-test"},
  "uris": [
"http://192.168.10.2/cobbler/PlayHello.zip";
  ]
}

Re: Enabling marathon for cni networks

2017-12-11 Thread Tomek Janiszewski

Take a look here
https://mesosphere.github.io/marathon/docs/networking.html#enabling-container-mode
Or if you are running older version of Marathon here
https://mesosphere.github.io/marathon/docs/ip-per-task.html

pon., 11 gru 2017 o 13:29 użytkownik Marc Roos 
napisał:

>
> I have a default marathon setup that attaches containers to the host
> network.
>
> Where should I put this configuration of NetworkInfo? In
> /etc/marathon/conf?
>
>
> http://mesos.apache.org/documentation/cni/#attaching-containers-to-cni-networks
>

Enabling marathon for cni networks

2017-12-11 Thread Marc Roos


I have a default marathon setup that attaches containers to the host 
network. 

Where should I put this configuration of NetworkInfo? In 
/etc/marathon/conf?

http://mesos.apache.org/documentation/cni/#attaching-containers-to-cni-networks

RE: How to add static ip to application

2017-12-11 Thread Marc Roos

 
I got it. I had the "ns" option in the mesos-dns config, when I 
commented it out, I started being able to resolve

[marc@m01 mesos]# dig +short @192.168.10.151 influxdb.marathon.mesos
192.168.10.153
[marc@m01 mesos]# dig +short @192.168.10.151 mesos-dns.marathon.mesos
192.168.10.151




-Original Message-
From: Tomek Janiszewski [mailto:jani...@gmail.com] 
Sent: maandag 11 december 2017 11:57
To: user@mesos.apache.org
Subject: Re: How to add static ip to application

You can achieve it with Mesos-DNS. Here is a small overview how to do it 
https://stackoverflow.com/a/37822870/1387612

pon., 11 gru 2017 o 11:48 użytkownik Marc Roos 
 napisał:



Ok should this be available in mesos/marathon also, because I did 
not
install dcos yet?




-Original Message-
From: Alvaro Brandon [mailto:alvarobran...@gmail.com]
Sent: maandag 11 december 2017 11:46
To: user@mesos.apache.org
Subject: Re: How to add static ip to application

You can consider influxdb.marathon.agentip.dcos.thisdcos.directory 
as
the static IP. This will allow you to do exactly what you are 
saying.


If for any reason a DNS name is not enough and you want an IP for 
the
service like 10.158.79.241, I'm pretty sure that there is no way of
doing so.


2017-12-11 11:39 GMT+01:00 Marc Roos :




Is it possible to configure just a static ip for now, just 
for the
purpose of my education? I want to see if I can access the 
task on
this
ip when I am starting it on different hosts.





-Original Message-
From: Alvaro Brandon [mailto:alvarobran...@gmail.com
 ]
Sent: maandag 11 december 2017 11:20
To: user@mesos.apache.org
Subject: Re: How to add static ip to application

I think its DNS what you need. The DNS name for your task 
can be
used as
an static reference to the influxdb instance, independently 
of the
host.


https://docs.mesosphere.com/1.10/networking/dns-overview/



Take a look at the link, but I think you can use
influxdb.marathon.agentip.dcos.thisdcos.directory as the 
task's
address

2017-12-11 11:11 GMT+01:00 Marc Roos 
:



For now I would like to have the ip bound to the
application/task/container, no matter on what host 
the
application
will
be started. And in this case I would like to be 
able to
access the
influxdb server as if I would have been created a 
dedicated
vm for
it.

Is there some page explaining the syntax of 
ipAddress? This
are not
working, I tried also with removing the 
portDefinitions
section.


{
  "id": "/influxdb",
  "cmd": null,
  "cpus": 0.5,
  "mem": 128,
  "disk": 0,
  "instances": 1,
  "acceptedResourceRoles": [],
  "container": {
"type": "MESOS",
"volumes": [],
"docker": {
  "image": "influxdb",
  "credential": null,
  "forcePullImage": false
}
  },
"ipAddress": {},
  "portDefinitions": [
{
  "port": 10001,
  "protocol": "tcp",
  "labels": {}
}
  ]
}


-Original Message-
From: Tomek Janiszewski [mailto:jani...@gmail.com]
Sent: maandag 11 december 2017 10:41
To: user@mesos.apache.org
Subject: Re: How to add static ip to application

What do you

Re: How to add static ip to application

2017-12-11 Thread Tomek Janiszewski

You can achieve it with Mesos-DNS. Here is a small overview how to do it
https://stackoverflow.com/a/37822870/1387612

pon., 11 gru 2017 o 11:48 użytkownik Marc Roos 
napisał:

>
> Ok should this be available in mesos/marathon also, because I did not
> install dcos yet?
>
>
>
>
> -Original Message-
> From: Alvaro Brandon [mailto:alvarobran...@gmail.com]
> Sent: maandag 11 december 2017 11:46
> To: user@mesos.apache.org
> Subject: Re: How to add static ip to application
>
> You can consider influxdb.marathon.agentip.dcos.thisdcos.directory as
> the static IP. This will allow you to do exactly what you are saying.
>
>
> If for any reason a DNS name is not enough and you want an IP for the
> service like 10.158.79.241, I'm pretty sure that there is no way of
> doing so.
>
>
> 2017-12-11 11:39 GMT+01:00 Marc Roos :
>
>
>
>
> Is it possible to configure just a static ip for now, just for the
> purpose of my education? I want to see if I can access the task on
> this
> ip when I am starting it on different hosts.
>
>
>
>
>
> -Original Message-
> From: Alvaro Brandon [mailto:alvarobran...@gmail.com
>  ]
> Sent: maandag 11 december 2017 11:20
> To: user@mesos.apache.org
> Subject: Re: How to add static ip to application
>
> I think its DNS what you need. The DNS name for your task can be
> used as
> an static reference to the influxdb instance, independently of the
> host.
>
>
> https://docs.mesosphere.com/1.10/networking/dns-overview/
> 
>
>
> Take a look at the link, but I think you can use
> influxdb.marathon.agentip.dcos.thisdcos.directory as the task's
> address
>
> 2017-12-11 11:11 GMT+01:00 Marc Roos :
>
>
>
> For now I would like to have the ip bound to the
> application/task/container, no matter on what host the
> application
> will
> be started. And in this case I would like to be able to
> access the
> influxdb server as if I would have been created a dedicated
> vm for
> it.
>
> Is there some page explaining the syntax of ipAddress? This
> are not
> working, I tried also with removing the portDefinitions
> section.
>
>
> {
>   "id": "/influxdb",
>   "cmd": null,
>   "cpus": 0.5,
>   "mem": 128,
>   "disk": 0,
>   "instances": 1,
>   "acceptedResourceRoles": [],
>   "container": {
> "type": "MESOS",
> "volumes": [],
> "docker": {
>   "image": "influxdb",
>   "credential": null,
>   "forcePullImage": false
> }
>   },
> "ipAddress": {},
>   "portDefinitions": [
> {
>   "port": 10001,
>   "protocol": "tcp",
>   "labels": {}
> }
>   ]
> }
>
>
> -Original Message-
> From: Tomek Janiszewski [mailto:jani...@gmail.com]
> Sent: maandag 11 december 2017 10:41
> To: user@mesos.apache.org
> Subject: Re: How to add static ip to application
>
> What do you mean by "bind to a static IP"?
>
> 1.  IP Per Container?
>
> https://mesosphere.github.io/marathon/docs/ip-per-task.html
> 
>   >
> 2.  IP of one dedicated host?
>
> https://mesosphere.github.io/marathon/docs/constraints.html
> 
>   >
> 3.  Layer 3/4 loadbalancer that will create Virtual IP
> (VIP)?
>
>
>
> niedz., 10 gru 2017 o 23:33 użytkownik Marc Roos
>  napisał:
>
>
>
>
> I downloaded the influxdb docker image and am
> running it
> from
> Marathon,
> I would like to bind it to a static ip. What would
> be the
> 'best'
> way to
> do this? Sorry for if this is a very basic
> question. Link
>

RE: How to add static ip to application

2017-12-11 Thread Marc Roos

 
Ok should this be available in mesos/marathon also, because I did not 
install dcos yet?




-Original Message-
From: Alvaro Brandon [mailto:alvarobran...@gmail.com] 
Sent: maandag 11 december 2017 11:46
To: user@mesos.apache.org
Subject: Re: How to add static ip to application

You can consider influxdb.marathon.agentip.dcos.thisdcos.directory as 
the static IP. This will allow you to do exactly what you are saying.


If for any reason a DNS name is not enough and you want an IP for the 
service like 10.158.79.241, I'm pretty sure that there is no way of 
doing so.


2017-12-11 11:39 GMT+01:00 Marc Roos :




Is it possible to configure just a static ip for now, just for the
purpose of my education? I want to see if I can access the task on 
this
ip when I am starting it on different hosts.





-Original Message-
From: Alvaro Brandon [mailto:alvarobran...@gmail.com 
 ]
Sent: maandag 11 december 2017 11:20
To: user@mesos.apache.org
Subject: Re: How to add static ip to application

I think its DNS what you need. The DNS name for your task can be 
used as
an static reference to the influxdb instance, independently of the 
host.


https://docs.mesosphere.com/1.10/networking/dns-overview/ 
 


Take a look at the link, but I think you can use
influxdb.marathon.agentip.dcos.thisdcos.directory as the task's 
address

2017-12-11 11:11 GMT+01:00 Marc Roos :



For now I would like to have the ip bound to the
application/task/container, no matter on what host the 
application
will
be started. And in this case I would like to be able to 
access the
influxdb server as if I would have been created a dedicated 
vm for
it.

Is there some page explaining the syntax of ipAddress? This 
are not
working, I tried also with removing the portDefinitions 
section.


{
  "id": "/influxdb",
  "cmd": null,
  "cpus": 0.5,
  "mem": 128,
  "disk": 0,
  "instances": 1,
  "acceptedResourceRoles": [],
  "container": {
"type": "MESOS",
"volumes": [],
"docker": {
  "image": "influxdb",
  "credential": null,
  "forcePullImage": false
}
  },
"ipAddress": {},
  "portDefinitions": [
{
  "port": 10001,
  "protocol": "tcp",
  "labels": {}
}
  ]
}


-Original Message-
From: Tomek Janiszewski [mailto:jani...@gmail.com]
Sent: maandag 11 december 2017 10:41
To: user@mesos.apache.org
Subject: Re: How to add static ip to application

What do you mean by "bind to a static IP"?

1.  IP Per Container?
https://mesosphere.github.io/marathon/docs/ip-per-task.html 
 
 >
2.  IP of one dedicated host?
https://mesosphere.github.io/marathon/docs/constraints.html 
 
 >
3.  Layer 3/4 loadbalancer that will create Virtual IP 
(VIP)?



niedz., 10 gru 2017 o 23:33 użytkownik Marc Roos
 napisał:




I downloaded the influxdb docker image and am 
running it
from
Marathon,
I would like to bind it to a static ip. What would 
be the
'best'
way to
do this? Sorry for if this is a very basic 
question. Link
to an
appropriate howto is also welcome.



{
  "id": "/influxdb",

Re: How to add static ip to application

2017-12-11 Thread Alvaro Brandon

You can consider influxdb.marathon.agentip.dcos.thisdcos.directory as the
static IP. This will allow you to do exactly what you are saying.

If for any reason a DNS name is not enough and you want an IP for the
service like 10.158.79.241, I'm pretty sure that there is no way of doing
so.


2017-12-11 11:39 GMT+01:00 Marc Roos :

>
>
> Is it possible to configure just a static ip for now, just for the
> purpose of my education? I want to see if I can access the task on this
> ip when I am starting it on different hosts.
>
>
>
>
> -Original Message-
> From: Alvaro Brandon [mailto:alvarobran...@gmail.com]
> Sent: maandag 11 december 2017 11:20
> To: user@mesos.apache.org
> Subject: Re: How to add static ip to application
>
> I think its DNS what you need. The DNS name for your task can be used as
> an static reference to the influxdb instance, independently of the host.
>
>
> https://docs.mesosphere.com/1.10/networking/dns-overview/
>
>
> Take a look at the link, but I think you can use
> influxdb.marathon.agentip.dcos.thisdcos.directory as the task's address
>
> 2017-12-11 11:11 GMT+01:00 Marc Roos :
>
>
>
> For now I would like to have the ip bound to the
> application/task/container, no matter on what host the application
> will
> be started. And in this case I would like to be able to access the
> influxdb server as if I would have been created a dedicated vm for
> it.
>
> Is there some page explaining the syntax of ipAddress? This are not
> working, I tried also with removing the portDefinitions section.
>
>
> {
>   "id": "/influxdb",
>   "cmd": null,
>   "cpus": 0.5,
>   "mem": 128,
>   "disk": 0,
>   "instances": 1,
>   "acceptedResourceRoles": [],
>   "container": {
> "type": "MESOS",
> "volumes": [],
> "docker": {
>   "image": "influxdb",
>   "credential": null,
>   "forcePullImage": false
> }
>   },
> "ipAddress": {},
>   "portDefinitions": [
> {
>   "port": 10001,
>   "protocol": "tcp",
>   "labels": {}
> }
>   ]
> }
>
>
> -Original Message-
> From: Tomek Janiszewski [mailto:jani...@gmail.com]
> Sent: maandag 11 december 2017 10:41
> To: user@mesos.apache.org
> Subject: Re: How to add static ip to application
>
> What do you mean by "bind to a static IP"?
>
> 1.  IP Per Container?
> https://mesosphere.github.io/marathon/docs/ip-per-task.html
> 
> 2.  IP of one dedicated host?
> https://mesosphere.github.io/marathon/docs/constraints.html
> 
> 3.  Layer 3/4 loadbalancer that will create Virtual IP (VIP)?
>
>
>
> niedz., 10 gru 2017 o 23:33 użytkownik Marc Roos
>  napisał:
>
>
>
>
> I downloaded the influxdb docker image and am running it
> from
> Marathon,
> I would like to bind it to a static ip. What would be the
> 'best'
> way to
> do this? Sorry for if this is a very basic question. Link
> to an
> appropriate howto is also welcome.
>
>
>
> {
>   "id": "/influxdb",
>   "cmd": null,
>   "cpus": 0.5,
>   "mem": 128,
>   "disk": 0,
>   "instances": 1,
>   "acceptedResourceRoles": [],
>   "container": {
> "type": "MESOS",
> "volumes": [],
> "docker": {
>   "image": "influxdb",
>   "credential": null,
>   "forcePullImage": false
> }
>   },
>   "portDefinitions": [
> {
>   "port": 10001,
>   "protocol": "tcp",
>   "labels": {}
> }
>   ]
> }
>
>
>
> I have a default setup on centos7:
> marathon-1.4.8-1.0.660.el7.x86_64
>
> mesosphere-zookeeper-3.4.6-0.1.20141204175332.centos7.x86_64
> chronos-2.5.0-0.1.20170816233446.el7.x86_64
> mesos-1.4.0-2.0.1.x86_64
>
> Running mesos-dns in Marathon
>
>
>
>
>
> 
>
>
>
>
>
>
>
>
>
>
>
>

RE: How to add static ip to application

2017-12-11 Thread Marc Roos

 

Is it possible to configure just a static ip for now, just for the 
purpose of my education? I want to see if I can access the task on this 
ip when I am starting it on different hosts.




-Original Message-
From: Alvaro Brandon [mailto:alvarobran...@gmail.com] 
Sent: maandag 11 december 2017 11:20
To: user@mesos.apache.org
Subject: Re: How to add static ip to application

I think its DNS what you need. The DNS name for your task can be used as 
an static reference to the influxdb instance, independently of the host.


https://docs.mesosphere.com/1.10/networking/dns-overview/


Take a look at the link, but I think you can use 
influxdb.marathon.agentip.dcos.thisdcos.directory as the task's address

2017-12-11 11:11 GMT+01:00 Marc Roos :



For now I would like to have the ip bound to the
application/task/container, no matter on what host the application 
will
be started. And in this case I would like to be able to access the
influxdb server as if I would have been created a dedicated vm for 
it.

Is there some page explaining the syntax of ipAddress? This are not
working, I tried also with removing the portDefinitions section.


{
  "id": "/influxdb",
  "cmd": null,
  "cpus": 0.5,
  "mem": 128,
  "disk": 0,
  "instances": 1,
  "acceptedResourceRoles": [],
  "container": {
"type": "MESOS",
"volumes": [],
"docker": {
  "image": "influxdb",
  "credential": null,
  "forcePullImage": false
}
  },
"ipAddress": {},
  "portDefinitions": [
{
  "port": 10001,
  "protocol": "tcp",
  "labels": {}
}
  ]
}


-Original Message-
From: Tomek Janiszewski [mailto:jani...@gmail.com]
Sent: maandag 11 december 2017 10:41
To: user@mesos.apache.org
Subject: Re: How to add static ip to application

What do you mean by "bind to a static IP"?

1.  IP Per Container?
https://mesosphere.github.io/marathon/docs/ip-per-task.html 
 
2.  IP of one dedicated host?
https://mesosphere.github.io/marathon/docs/constraints.html 
 
3.  Layer 3/4 loadbalancer that will create Virtual IP (VIP)?



niedz., 10 gru 2017 o 23:33 użytkownik Marc Roos
 napisał:




I downloaded the influxdb docker image and am running it 
from
Marathon,
I would like to bind it to a static ip. What would be the 
'best'
way to
do this? Sorry for if this is a very basic question. Link 
to an
appropriate howto is also welcome.



{
  "id": "/influxdb",
  "cmd": null,
  "cpus": 0.5,
  "mem": 128,
  "disk": 0,
  "instances": 1,
  "acceptedResourceRoles": [],
  "container": {
"type": "MESOS",
"volumes": [],
"docker": {
  "image": "influxdb",
  "credential": null,
  "forcePullImage": false
}
  },
  "portDefinitions": [
{
  "port": 10001,
  "protocol": "tcp",
  "labels": {}
}
  ]
}



I have a default setup on centos7:
marathon-1.4.8-1.0.660.el7.x86_64

mesosphere-zookeeper-3.4.6-0.1.20141204175332.centos7.x86_64
chronos-2.5.0-0.1.20170816233446.el7.x86_64
mesos-1.4.0-2.0.1.x86_64

Running mesos-dns in Marathon

Re: How to add static ip to application

2017-12-11 Thread Alvaro Brandon

I think its DNS what you need. The DNS name for your task can be used as an
static reference to the influxdb instance, independently of the host.


https://docs.mesosphere.com/1.10/networking/dns-overview/

Take a look at the link, but I think you can use
influxdb.marathon.agentip.dcos.thisdcos.directory
as the task's address

2017-12-11 11:11 GMT+01:00 Marc Roos :

>
> For now I would like to have the ip bound to the
> application/task/container, no matter on what host the application will
> be started. And in this case I would like to be able to access the
> influxdb server as if I would have been created a dedicated vm for it.
>
> Is there some page explaining the syntax of ipAddress? This are not
> working, I tried also with removing the portDefinitions section.
>
>
> {
>   "id": "/influxdb",
>   "cmd": null,
>   "cpus": 0.5,
>   "mem": 128,
>   "disk": 0,
>   "instances": 1,
>   "acceptedResourceRoles": [],
>   "container": {
> "type": "MESOS",
> "volumes": [],
> "docker": {
>   "image": "influxdb",
>   "credential": null,
>   "forcePullImage": false
> }
>   },
> "ipAddress": {},
>   "portDefinitions": [
> {
>   "port": 10001,
>   "protocol": "tcp",
>   "labels": {}
> }
>   ]
> }
>
>
> -Original Message-
> From: Tomek Janiszewski [mailto:jani...@gmail.com]
> Sent: maandag 11 december 2017 10:41
> To: user@mesos.apache.org
> Subject: Re: How to add static ip to application
>
> What do you mean by "bind to a static IP"?
>
> 1.  IP Per Container?
> https://mesosphere.github.io/marathon/docs/ip-per-task.html
> 2.  IP of one dedicated host?
> https://mesosphere.github.io/marathon/docs/constraints.html
> 3.  Layer 3/4 loadbalancer that will create Virtual IP (VIP)?
>
>
> niedz., 10 gru 2017 o 23:33 użytkownik Marc Roos
>  napisał:
>
>
>
>
> I downloaded the influxdb docker image and am running it from
> Marathon,
> I would like to bind it to a static ip. What would be the 'best'
> way to
> do this? Sorry for if this is a very basic question. Link to an
> appropriate howto is also welcome.
>
>
>
> {
>   "id": "/influxdb",
>   "cmd": null,
>   "cpus": 0.5,
>   "mem": 128,
>   "disk": 0,
>   "instances": 1,
>   "acceptedResourceRoles": [],
>   "container": {
> "type": "MESOS",
> "volumes": [],
> "docker": {
>   "image": "influxdb",
>   "credential": null,
>   "forcePullImage": false
> }
>   },
>   "portDefinitions": [
> {
>   "port": 10001,
>   "protocol": "tcp",
>   "labels": {}
> }
>   ]
> }
>
>
>
> I have a default setup on centos7:
> marathon-1.4.8-1.0.660.el7.x86_64
> mesosphere-zookeeper-3.4.6-0.1.20141204175332.centos7.x86_64
> chronos-2.5.0-0.1.20170816233446.el7.x86_64
> mesos-1.4.0-2.0.1.x86_64
>
> Running mesos-dns in Marathon
>
>
>
>
>
> 
>
>
>
>
>
>
>
>

RE: How to add static ip to application

2017-12-11 Thread Marc Roos

 
For now I would like to have the ip bound to the 
application/task/container, no matter on what host the application will 
be started. And in this case I would like to be able to access the 
influxdb server as if I would have been created a dedicated vm for it. 

Is there some page explaining the syntax of ipAddress? This are not 
working, I tried also with removing the portDefinitions section.


{
  "id": "/influxdb",
  "cmd": null,
  "cpus": 0.5,
  "mem": 128,
  "disk": 0,
  "instances": 1,
  "acceptedResourceRoles": [],
  "container": {
"type": "MESOS",
"volumes": [],
"docker": {
  "image": "influxdb",
  "credential": null,
  "forcePullImage": false
}
  },
"ipAddress": {},
  "portDefinitions": [
{
  "port": 10001,
  "protocol": "tcp",
  "labels": {}
}
  ]
}


-Original Message-
From: Tomek Janiszewski [mailto:jani...@gmail.com] 
Sent: maandag 11 december 2017 10:41
To: user@mesos.apache.org
Subject: Re: How to add static ip to application

What do you mean by "bind to a static IP"?

1.  IP Per Container? 
https://mesosphere.github.io/marathon/docs/ip-per-task.html
2.  IP of one dedicated host? 
https://mesosphere.github.io/marathon/docs/constraints.html
3.  Layer 3/4 loadbalancer that will create Virtual IP (VIP)? 


niedz., 10 gru 2017 o 23:33 użytkownik Marc Roos 
 napisał:




I downloaded the influxdb docker image and am running it from 
Marathon,
I would like to bind it to a static ip. What would be the 'best' 
way to
do this? Sorry for if this is a very basic question. Link to an
appropriate howto is also welcome.



{
  "id": "/influxdb",
  "cmd": null,
  "cpus": 0.5,
  "mem": 128,
  "disk": 0,
  "instances": 1,
  "acceptedResourceRoles": [],
  "container": {
"type": "MESOS",
"volumes": [],
"docker": {
  "image": "influxdb",
  "credential": null,
  "forcePullImage": false
}
  },
  "portDefinitions": [
{
  "port": 10001,
  "protocol": "tcp",
  "labels": {}
}
  ]
}



I have a default setup on centos7:
marathon-1.4.8-1.0.660.el7.x86_64
mesosphere-zookeeper-3.4.6-0.1.20141204175332.centos7.x86_64
chronos-2.5.0-0.1.20170816233446.el7.x86_64
mesos-1.4.0-2.0.1.x86_64

Running mesos-dns in Marathon

Re: How to add static ip to application

2017-12-11 Thread Tomek Janiszewski

What do you mean by "bind to a static IP"?

   1. IP Per Container?
   https://mesosphere.github.io/marathon/docs/ip-per-task.html
   2. IP of one dedicated host?
   https://mesosphere.github.io/marathon/docs/constraints.html
   3. Layer 3/4 loadbalancer that will create Virtual IP (VIP)?


niedz., 10 gru 2017 o 23:33 użytkownik Marc Roos 
napisał:

>
>
> I downloaded the influxdb docker image and am running it from Marathon,
> I would like to bind it to a static ip. What would be the 'best' way to
> do this? Sorry for if this is a very basic question. Link to an
> appropriate howto is also welcome.
>
>
>
> {
>   "id": "/influxdb",
>   "cmd": null,
>   "cpus": 0.5,
>   "mem": 128,
>   "disk": 0,
>   "instances": 1,
>   "acceptedResourceRoles": [],
>   "container": {
> "type": "MESOS",
> "volumes": [],
> "docker": {
>   "image": "influxdb",
>   "credential": null,
>   "forcePullImage": false
> }
>   },
>   "portDefinitions": [
> {
>   "port": 10001,
>   "protocol": "tcp",
>   "labels": {}
> }
>   ]
> }
>
>
>
> I have a default setup on centos7:
> marathon-1.4.8-1.0.660.el7.x86_64
> mesosphere-zookeeper-3.4.6-0.1.20141204175332.centos7.x86_64
> chronos-2.5.0-0.1.20170816233446.el7.x86_64
> mesos-1.4.0-2.0.1.x86_64
>
> Running mesos-dns in Marathon
>
>
>
>
>
> 
>
>
>
>
>

Re: Dedicated ip to task

Re: cni macvlan config

Re: Dedicated ip to task

Dedicated ip to task

December Performance Working Group Report

cni macvlan config

Re: Enabling marathon for cni networks

Enabling marathon for cni networks

RE: How to add static ip to application

Re: How to add static ip to application

RE: How to add static ip to application

Re: How to add static ip to application

RE: How to add static ip to application

Re: How to add static ip to application

RE: How to add static ip to application

Re: How to add static ip to application

16 matches

Site Navigation

Mail list logo

Footer information