[
https://issues.apache.org/jira/browse/MESOS-2191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14493819#comment-14493819
]
Timothy Chen commented on MESOS-2191:
-------------------------------------
Hi Marcel,
Thanks for explaining the rationale for getting ContainerId. There are quite a
number of requests to ask for the Container name, and also different requests
asking for various Docker container related information to get sent back to the
scheduler for advanced use cases as you described.
What I'm currently considering doing is to actually send back the whole docker
inspect response back in TaskStatus, so in your scheduler when you see
TaskStatus with TASK_RUNNING, the optional data field will contain the Docker
inspect JSON output string serailized into a byte array. Then you can get any
information such as name, network settings, volumes, all in in one place.
Let me know what you think and if you foresee problems with this.
> Add ContainerId to the TaskStatus message
> -----------------------------------------
>
> Key: MESOS-2191
> URL: https://issues.apache.org/jira/browse/MESOS-2191
> Project: Mesos
> Issue Type: Wish
> Components: containerization
> Reporter: Marcel Neuhausler
> Assignee: Alexander Rojas
> Labels: mesosphere
>
> {{TaskStatus}} provides the frameworks with certain information
> ({{executorId}}, {{slaveId}}, etc.) which is useful when collecting
> statistics about cluster performance; however, it is difficult to associate
> tasks to the container it is executed since this information stays always
> within mesos itself. Therefore it would be good to provide the framework
> scheduler with this information, adding a new field in the {{TaskStatus}}
> message.
> See comments for a use case.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
