[
https://issues.apache.org/jira/browse/MESOS-2221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14730752#comment-14730752
]
Klaus Ma commented on MESOS-2221:
---------------------------------
It seems master/slave just pass the container's information from slave to
framework; if so, suggest to provide a general way for customer to pass such
kind of information; If framework want to only accept resources with docker,
suggest to add framework level filters (it'll also avoid lots of filters in
allocator: reject one slave by one filter). There's a draft idea about the
filter & user defined resources/attributes at
[here|https://docs.google.com/document/d/1amdq08UyV4pR2dt9xTUCYNFXhRmXKZNzO7qG6k7JCF4/edit?usp=sharing];
I drafted it few weeks ago, some assumption/definition maybe inaccurate.
Regarding DiskInfo, i think it's a little different:
- master/slave take action based on volume/persistence in DiskInfo
- master/slave do not care about container info, just pass it to framework
> 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)
