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 https://github.com/apache/aurora/blob/master/docs/design-documents.md, 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 (http://mesos.apache.org/documentation/latest/app-framework-development-guide/). Thanks, Stephan ________________________________________ From: Zhitao Li <zhitaoli...@gmail.com> Sent: Monday, March 7, 2016 00:05 To: dev@aurora.apache.org Subject: Populate DiscoveryInfo in Mesos Hi, It seems like Aurora does not populate the "discovery" field in either TaskInfo or ExecutorInfo in mesos.proto <https://github.com/apache/mesos/blob/master/include/mesos/mesos.proto#L438> . 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
