[
https://issues.apache.org/jira/browse/MESOS-2221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14284953#comment-14284953
]
Jie Yu commented on MESOS-2221:
-------------------------------
[~dhamon] I mentioned that because it's going to affect the API. For example,
if we only want to support Containerizer information, the API can just look
like this:
{noformat}
message Offer {
...
optional ContainerInfo.Type containerizer;
}
{noformat}
However, if we were to add isolation information, this interface is not
extensible. So a better interface could be:
{noformat}
message Container {
required Type type;
optional bool cpu_isolation;
optional bool mem_isolation;
optional bool disk_isolation;
...
}
message Offer {
optional Container container;
}
{noformat}
> Include supported containerizers in resource offers
> ---------------------------------------------------
>
> Key: MESOS-2221
> URL: https://issues.apache.org/jira/browse/MESOS-2221
> Project: Mesos
> Issue Type: Improvement
> Components: slave
> Reporter: Bill Farner
> Labels: twitter
>
> It would be nice if the slave could advertise to the scheduler which
> containerizers it supports. As it stands, the scheduler must count on
> external knowledge of whether a task is supported by a slave. For example, a
> scheduler cannot automatically notice that a slave does not have the docker
> containerizer enabled, and may fatefully try to launch docker tasks.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
