You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@mesos.apache.org by Zhitao Li <zh...@gmail.com> on 2016/03/22 06:24:34 UTC

State of DiscoveryInfo

Hi,

Does anyone have an example of using the DiscoveryInfo from Mesos 0.22? I'm
interested in understanding its current status and adoption situation,
whether any real service discovery system is using it, and what's the
blocker if not.

Thanks.

-- 
Cheers,

Zhitao Li

Re: State of DiscoveryInfo

Posted by Zhitao Li <zh...@gmail.com>.
Hi Sargun,

Thanks for the response. In fact I'm trying to add DiscoveryInfo to Aurora
and the minimal deliverable I wanted is make an Aurora job routable by
Mesos DNS.

A couple of questions/replies inlined:


On Mon, Mar 28, 2016 at 10:10 AM, Sargun Dhillon <sa...@sargun.me> wrote:

> So, we parse DiscoveryInfo in Mesos DNS, and we can use it to generate
> custom DNS records on behalf of a framework. Mesos-DNS publishes SRV,
> and A records in order to act as an service discovery mechanism for
> applications that are both "inside" and "outside" of a "Mesos
> cluster".
>

This doc <http://mesosphere.github.io/mesos-dns/docs/naming.html> seems to
suggest it's using a "task". Do you know the exact source of that? Mesos
task id/source/"name" field on DiscoveryInfo?

>
> The DiscoveryInfo field is also used to indicate other things. For
> example, if several ports are allocated to a task / Container, we may
> be unsure of which ports that container should expect ingress
> connectivity on. Although we can parse the resources, it becomes
> somewhat brittle as we begin to interface with other networks. In
> order to avoid this, the framework can tell us which ports are
> allocated to ingress traffic. In my opinion, any tasks that are
> planning on accepting traffic should expose this information via
> DiscoveryInfo. This information can then be taken to configure tools
> like IPTables, or other network filtering.
>
> Lastly, DiscoveryInfo has some free form fields (labels). These labels
> can be used to configure load balancing tools like HAProxy, etc. We
> have some internal standards we use that can auto-configure virtual
> IPs to map to the tasks that have the right port label format. This
> makes it incredibly easy to wire up tasks within the cluster.
>

Do you have such conventions documented? I can cross link that in Aurora's
doc.


>
> On Tue, Mar 22, 2016 at 1:42 AM, haosdent <ha...@gmail.com> wrote:
> > As I know, Mesos-DNS use discoveryInfo from Mesos.
> > https://github.com/mesosphere/mesos-dns
> >
> > I also found some links may be useful for you:
> >
> > https://open.mesosphere.com/tutorials/service-discovery/
> >
> https://mesosphere.github.io/marathon/docs/service-discovery-load-balancing.html
> >
> http://events.linuxfoundation.org/sites/events/files/slides/mesos-networking.mesoscon2015.pdf
> >
> > And the design doc of DiscoveryInfo also show "Example Uses" about it:
> >
> https://docs.google.com/document/d/1tpnjfHsa5Joka23CqgGppqnK0jODcElBvTFUBBO-A38/edit#heading=h.4wpt5efsi44n
> >
> > On Tue, Mar 22, 2016 at 4:31 PM, tommy xiao <xi...@gmail.com> wrote:
> >>
> >> need a related issue to tracking
> >>
> >> 2016-03-22 13:24 GMT+08:00 Zhitao Li <zh...@gmail.com>:
> >>>
> >>> Hi,
> >>>
> >>> Does anyone have an example of using the DiscoveryInfo from Mesos 0.22?
> >>> I'm interested in understanding its current status and adoption
> situation,
> >>> whether any real service discovery system is using it, and what's the
> >>> blocker if not.
> >>>
> >>> Thanks.
> >>>
> >>> --
> >>> Cheers,
> >>>
> >>> Zhitao Li
> >>
> >>
> >>
> >>
> >> --
> >> Deshi Xiao
> >> Twitter: xds2000
> >> E-mail: xiaods(AT)gmail.com
> >
> >
> >
> >
> > --
> > Best Regards,
> > Haosdent Huang
>



-- 
Cheers,

Zhitao Li

Re: State of DiscoveryInfo

Posted by Sargun Dhillon <sa...@sargun.me>.
So, we parse DiscoveryInfo in Mesos DNS, and we can use it to generate
custom DNS records on behalf of a framework. Mesos-DNS publishes SRV,
and A records in order to act as an service discovery mechanism for
applications that are both "inside" and "outside" of a "Mesos
cluster".

The DiscoveryInfo field is also used to indicate other things. For
example, if several ports are allocated to a task / Container, we may
be unsure of which ports that container should expect ingress
connectivity on. Although we can parse the resources, it becomes
somewhat brittle as we begin to interface with other networks. In
order to avoid this, the framework can tell us which ports are
allocated to ingress traffic. In my opinion, any tasks that are
planning on accepting traffic should expose this information via
DiscoveryInfo. This information can then be taken to configure tools
like IPTables, or other network filtering.

Lastly, DiscoveryInfo has some free form fields (labels). These labels
can be used to configure load balancing tools like HAProxy, etc. We
have some internal standards we use that can auto-configure virtual
IPs to map to the tasks that have the right port label format. This
makes it incredibly easy to wire up tasks within the cluster.

On Tue, Mar 22, 2016 at 1:42 AM, haosdent <ha...@gmail.com> wrote:
> As I know, Mesos-DNS use discoveryInfo from Mesos.
> https://github.com/mesosphere/mesos-dns
>
> I also found some links may be useful for you:
>
> https://open.mesosphere.com/tutorials/service-discovery/
> https://mesosphere.github.io/marathon/docs/service-discovery-load-balancing.html
> http://events.linuxfoundation.org/sites/events/files/slides/mesos-networking.mesoscon2015.pdf
>
> And the design doc of DiscoveryInfo also show "Example Uses" about it:
> https://docs.google.com/document/d/1tpnjfHsa5Joka23CqgGppqnK0jODcElBvTFUBBO-A38/edit#heading=h.4wpt5efsi44n
>
> On Tue, Mar 22, 2016 at 4:31 PM, tommy xiao <xi...@gmail.com> wrote:
>>
>> need a related issue to tracking
>>
>> 2016-03-22 13:24 GMT+08:00 Zhitao Li <zh...@gmail.com>:
>>>
>>> Hi,
>>>
>>> Does anyone have an example of using the DiscoveryInfo from Mesos 0.22?
>>> I'm interested in understanding its current status and adoption situation,
>>> whether any real service discovery system is using it, and what's the
>>> blocker if not.
>>>
>>> Thanks.
>>>
>>> --
>>> Cheers,
>>>
>>> Zhitao Li
>>
>>
>>
>>
>> --
>> Deshi Xiao
>> Twitter: xds2000
>> E-mail: xiaods(AT)gmail.com
>
>
>
>
> --
> Best Regards,
> Haosdent Huang

Re: State of DiscoveryInfo

Posted by haosdent <ha...@gmail.com>.
As I know, Mesos-DNS use discoveryInfo from Mesos.
https://github.com/mesosphere/mesos-dns

I also found some links may be useful for you:

https://open.mesosphere.com/tutorials/service-discovery/
https://mesosphere.github.io/marathon/docs/service-discovery-load-balancing.html
http://events.linuxfoundation.org/sites/events/files/slides/mesos-networking.mesoscon2015.pdf

And the design doc of DiscoveryInfo also show "Example Uses" about it:
https://docs.google.com/document/d/1tpnjfHsa5Joka23CqgGppqnK0jODcElBvTFUBBO-A38/edit#heading=h.4wpt5efsi44n

On Tue, Mar 22, 2016 at 4:31 PM, tommy xiao <xi...@gmail.com> wrote:

> need a related issue to tracking
>
> 2016-03-22 13:24 GMT+08:00 Zhitao Li <zh...@gmail.com>:
>
>> Hi,
>>
>> Does anyone have an example of using the DiscoveryInfo from Mesos 0.22?
>> I'm interested in understanding its current status and adoption situation,
>> whether any real service discovery system is using it, and what's the
>> blocker if not.
>>
>> Thanks.
>>
>> --
>> Cheers,
>>
>> Zhitao Li
>>
>
>
>
> --
> Deshi Xiao
> Twitter: xds2000
> E-mail: xiaods(AT)gmail.com
>



-- 
Best Regards,
Haosdent Huang

Re: State of DiscoveryInfo

Posted by tommy xiao <xi...@gmail.com>.
need a related issue to tracking

2016-03-22 13:24 GMT+08:00 Zhitao Li <zh...@gmail.com>:

> Hi,
>
> Does anyone have an example of using the DiscoveryInfo from Mesos 0.22?
> I'm interested in understanding its current status and adoption situation,
> whether any real service discovery system is using it, and what's the
> blocker if not.
>
> Thanks.
>
> --
> Cheers,
>
> Zhitao Li
>



-- 
Deshi Xiao
Twitter: xds2000
E-mail: xiaods(AT)gmail.com