[
https://issues.apache.org/jira/browse/MESOS-2191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14254960#comment-14254960
]
Marcel Neuhausler commented on MESOS-2191:
------------------------------------------
Currently building a lab environment for resource-schedulers/optimizers. In
that context I'm using cAdvisor to collect metrics of running Docker containers
managed by Mesos. Unfortunately the containers get named by Mesos with a random
UUID which makes it very hard/impossible? to correlate "TaskId" set by the
Framework with that "ContainerId" in cAdvisor.
A Framework already gets all the other Mesos-related Ids (Framework, Executor,
Slave) via the StatusUpdate message, so it would feel natural that that message
would return the ContainerId also. And with that it would be very easy for the
Framework to correlate a ContainerId with its internal TaskId.
> Add ContainerId into StatusMessage
> ----------------------------------
>
> Key: MESOS-2191
> URL: https://issues.apache.org/jira/browse/MESOS-2191
> Project: Mesos
> Issue Type: Wish
> Components: containerization
> Reporter: Marcel Neuhausler
>
> ContainerId should be returned to the Framework as part of the StatusMessage
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
