[
https://issues.apache.org/jira/browse/MESOS-4487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Avinash Sridharan updated MESOS-4487:
-------------------------------------
Summary: Introduce status() interface in `Containerizer` (was: Introduce
getContainerConfig interface in `Containerizer`)
> Introduce status() interface in `Containerizer`
> -----------------------------------------------
>
> Key: MESOS-4487
> URL: https://issues.apache.org/jira/browse/MESOS-4487
> Project: Mesos
> Issue Type: Improvement
> Components: containerization
> Reporter: Avinash Sridharan
> Assignee: Avinash Sridharan
> Labels: containerizer, mesosphere
>
> In the Containerizer, during container isolation, the isolators end up
> modifying the configuration of the containers in the prepare or the isolate
> phase of launching the container. Examples would be IP address allocation to
> a container by the 'network isolator, or net_cls handle allocation by the
> cgroup/net_cls isolator.
> Often times the configuration, applied to the container by the isolator,
> needs to be exposed to operators through the state.json end-point. For e.g.
> operators or frameworks might want to know the IP-address configured on a
> particular container, or the net_cls handle associated with a container to
> configure the right TC rules. However, at present, there is no clean
> interface for the slave to retrieve the container config information from the
> Containerizer for any of the launched containers. Thus, we need to introduce
> a `getContainerConfig` interface in the `Containerizer` base class, in order
> for the slave to expose container config information in its state.json.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)