[
https://issues.apache.org/jira/browse/MESOS-2221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14284922#comment-14284922
]
Jie Yu commented on MESOS-2221:
-------------------------------
[~wfarner] The reason I mentioned using attributes is because I think
containerization information serves the same purpose as attributes. But I agree
with you that using a global namespace and an implicit convention is not a good
API design.
A few more thoughts to generate discussion here: let's say we introduce first
class information about containerization in resource offers (e.g.,
mesos/docker). A natural followup question is: can we also include the
isolation information in resource offers? For example, a framework might wanna
know if a slave can isolate cpu/memory resources, and only put latency
sensitive jobs on those slaves that have cpu/memory isolation enabled. The
isolation information should be independent of whether mesos or docker
containerizer is used. What the API should be look like?
> 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)
