aurora-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Erb, Stephan" <>
Subject Re: Populate DiscoveryInfo in Mesos
Date Fri, 25 Mar 2016 20:42:00 GMT
I had a closer look at the Mesos documentation, and a design document might be unnecessary.
Most of the values are optional. We can therefore leave them out until we have a proper usecase
for them.

I left a couple of comments in the review request. 
From: Zhitao Li <>
Sent: Tuesday, March 22, 2016 21:15
Subject: Re: Populate DiscoveryInfo in Mesos

Hi Stephan,

Sorry for the delay on follow up on this. I took a quick look at Aurora
code, and it's actually quite easy to pipe this information to Mesos (see for quick prototype).

I'll take a stab to see how I can get Mesos-DNS to work with this prototype.

IMO, if this is something the community is interested, the main questions
would be 1) how various fields would be mapped in different Aurora usages,
and 2) to which level should opt-in/opt-out configured for populating such

I actually don't have too much insights on how these usage conventions
would be set (through command line of scheduler or job configuration?)

Do you think a design doc is the best action here, or a more involved
questionnaire about which fields would be useful for community, or what
value they should take?

On Mon, Mar 7, 2016 at 1:00 AM, Erb, Stephan <>

> That sounds like a good idea! Great.
> If you go ahead with this, please be so kind and start by posting a short
> design document here on mailinglist (similar to those here
> but probably shorter).
> This will allow us to split the discussion of the design from discussing
> the actual implementation. I believe this is necessary, as the
> DiscoveryInfo protocol is quite flexible (
> ).
> Thanks,
> Stephan
> ________________________________________
> From: Zhitao Li <>
> Sent: Monday, March 7, 2016 00:05
> To:
> Subject: Populate DiscoveryInfo in Mesos
> Hi,
> It seems like Aurora does not populate the "discovery" field in either
> TaskInfo or ExecutorInfo in mesos.proto
> <
> >
> .
> I'm considering adding this to support retrieving port map in Mesos
> directly. This would enable us to discovery this information directly from
> Mesos side, and also enables us to build one universal service discovery
> solution for multiple frameworks including Aurora.
> If no objection, I'll create a JIRA ticket for this task.
> Thanks.
> --
> Cheers,
> Zhitao Li


Zhitao Li

View raw message