You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Marcel Neuhausler (JIRA)" <ji...@apache.org> on 2015/04/10 19:57:12 UTC

[jira] [Commented] (MESOS-2191) Add ContainerId to the TaskStatus message

    [ https://issues.apache.org/jira/browse/MESOS-2191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14490003#comment-14490003 ] 

Marcel Neuhausler commented on MESOS-2191:
------------------------------------------

.. another use-case I came across. If you want to have a container use the network-stack of a previously started container you have to pass in the name of that container:
$ docker run --net=container:mesos-6b306796-454e-401e-8ccb-548b430279a6 ubuntu

By the way, that network-mode doesn't seem to be supported by Mesos yet. You have to pass that in using Mesos' dockerinfo parameters.

> 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)