[
https://issues.apache.org/jira/browse/MESOS-4064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Artem Harutyunyan updated MESOS-4064:
-------------------------------------
Description:
In what seems like an oversight, when ContainerInfo was added to TaskInfo, it
was not added to our internal Task protobuf.
Also, unlike the agent, it appears that the master does not use
protobuf::createTask. We should try remove the manual construction in the
master in favor of construction through protobuf::createTask.
Partial contents of ContainerInfo should be exposed through state endpoints on
the master and the agent.
was:
In what seems like an oversight, when ContainerInfo was added to TaskInfo, it
was not added to our internal Task protobuf.
Also, unlike the agent, it appears that the master does not use
protobuf::createTask. We should try remove the manual construction in the
master in favor of construction through protobuf::createTask.
> Add ContainerInfo to internal Task protobuf.
> --------------------------------------------
>
> Key: MESOS-4064
> URL: https://issues.apache.org/jira/browse/MESOS-4064
> Project: Mesos
> Issue Type: Task
> Reporter: Benjamin Mahler
> Assignee: Artem Harutyunyan
> Labels: mesosphere
>
> In what seems like an oversight, when ContainerInfo was added to TaskInfo, it
> was not added to our internal Task protobuf.
> Also, unlike the agent, it appears that the master does not use
> protobuf::createTask. We should try remove the manual construction in the
> master in favor of construction through protobuf::createTask.
> Partial contents of ContainerInfo should be exposed through state endpoints
> on the master and the agent.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
