>>
>>
>> *From:* zhou weitao [mailto:zhouwtl...@gmail.com]
>> *Sent:* Monday, June 29, 2015 10:51 PM
>> *To:* user@mesos.apache.org
>> *Subject:* Re: service discovery in Mesos on CoreOS
>>
>>
>>
>>
>>
>>
>>
>> 2015
n in a
> separate container.
>
>
>
> *From:* zhou weitao [mailto:zhouwtl...@gmail.com]
> *Sent:* Monday, June 29, 2015 10:51 PM
> *To:* user@mesos.apache.org
> *Subject:* Re: service discovery in Mesos on CoreOS
>
>
>
>
>
>
>
> 2015-06-30 6:23 GMT+08:00 And
Subject: Re: service discovery in Mesos on CoreOS
Also have another service discovery tool. https://www.consul.io/
https://github.com/CiscoCloud/mesos-consul
On Tue, Jun 30, 2015 at 10:51 AM, zhou weitao wrote:
2015-06-30 6:23 GMT+08:00 Andras Kerekes :
Hi,
Is there a
: service discovery in Mesos on CoreOS
2015-06-30 6:23 GMT+08:00 Andras Kerekes :
Hi,
Is there a preferred way to do service discovery in Mesos via mesos-dns running
on CoreOS? I’m trying to implement a simple app which consists of two docker
containers and one of them (A) depends on the
inside the docker
container of the apps, but that would be a really bad practice I think.
From: James DeFelice [mailto:james.defel...@gmail.com]
Sent: Monday, June 29, 2015 10:06 PM
To: user@mesos.apache.org
Subject: Re: service discovery in Mesos on CoreOS
Can you go with option 1, using the
Toy go app that queries SRV records, generates environment variables and
injects them into an exec'd command line:
https://github.com/jdef/srv2env
If you wanted template support you could pair this with confd and use the
env var backend.
If you're running tasks on marathon, when they die there i
+1 for mesos-consul
We've been using it to great effect!
From: Dave Lester [d...@davelester.org]
Sent: 30 June 2015 06:38
To: user@mesos.apache.org
Subject: Re: service discovery in Mesos on CoreOS
It would be great to have a documentation page devot
It would be great to have a documentation page devoted to compiling
these different solutions to service discovery; if anyone wants create a
new markdown file in docs/ and submit a pull request or review on Review
Board, add me as a reviewer!
Dave
On Mon, Jun 29, 2015, at 08:19 PM, haosdent wrote
Also have another service discovery tool. https://www.consul.io/
https://github.com/CiscoCloud/mesos-consul
On Tue, Jun 30, 2015 at 10:51 AM, zhou weitao wrote:
>
>
> 2015-06-30 6:23 GMT+08:00 Andras Kerekes :
>
>> Hi,
>>
>>
>>
>> Is there a preferred way to do service discovery in Mesos via mes
2015-06-30 6:23 GMT+08:00 Andras Kerekes :
> Hi,
>
>
>
> Is there a preferred way to do service discovery in Mesos via mesos-dns
> running on CoreOS? I’m trying to implement a simple app which consists of
> two docker containers and one of them (A) depends on the other (B). What
> I’d like to do i
Hi,
I am also facing similar problems with service discovery and load balancing. It
would be great if mesos-dns could resolve _task._protocol.framework.domain
queries to round-robin IP:PORT combinations. I am not an expert in DNS
protocols and probably this functionality would breach it but eve
Can you go with option 1, using the http api of mesos-dns to pull a json
srv-ish record, parse it with jq, and configure your app accordingly?
On Jun 29, 2015 3:24 PM, "Andras Kerekes"
wrote:
> Hi,
>
>
>
> Is there a preferred way to do service discovery in Mesos via mesos-dns
> running on CoreOS
Hi,
Is there a preferred way to do service discovery in Mesos via mesos-dns
running on CoreOS? I'm trying to implement a simple app which consists of
two docker containers and one of them (A) depends on the other (B). What I'd
like to do is to tell container A to use a fix dns name
(containerB.
13 matches
Mail list logo
