[
https://issues.apache.org/jira/browse/MESOS-4358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15114457#comment-15114457
]
Avinash Sridharan commented on MESOS-4358:
------------------------------------------
After talking Jie and Kapil, looks like we don't have any interface in the
`Containerizer` for the slave to retrieve container config information. Since
the slave cannot retrieve the configuration information from the isolator
(through the `Containerizer`), the lack of this interface prevents us from
exposing configurations applied by an isolator, to a container, in slaves
state.json. Therefore, before making progress on this ticket, we need to
enhance the `Containerizer` interface to expose the container config. Will be
creating new tickets to scope this work. We can make progress on this ticket
once the new interface has been introduce.
> Expose net_cls network handles in agent's state endpoint
> --------------------------------------------------------
>
> Key: MESOS-4358
> URL: https://issues.apache.org/jira/browse/MESOS-4358
> Project: Mesos
> Issue Type: Task
> Components: containerization
> Reporter: Avinash Sridharan
> Assignee: Avinash Sridharan
> Labels: container, containerizer, mesosphere
>
> We need to expose net_cls network handles, associated with containers, to
> operators and network utilities that would use these network handles to
> enforce network policy.
> In order to achieve the above we need to add a new field in the `NetworkInfo`
> protobuf (say NetHandles) and update this field when a container gets
> assigned to a net_cls cgroup. The `ContainerStatus` protobuf already has the
> `NetworkInfo` protobuf as a nested message, and the `ContainerStatus` itself
> is exposed to operators as part of TaskInfo (for tasks associated with the
> container) in an agent's state.json.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
