[
https://issues.apache.org/jira/browse/MESOS-2221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14284698#comment-14284698
]
Timothy Chen commented on MESOS-2221:
-------------------------------------
It seems like the containerizer information is, for now, one more piece of
information that the frameworks can use for scheduling, which is similiar to
what attributes are.
I don't really like the overall idea munging into global attributes since it
contains user defined and mesos defined data, I wonder if instead of using
mesos_ prefix we should actually have a seperate attributes parameter that is
all the metadata mesos added.
I'm not yet sure what's the best approach, just throwing my 2cents for now.
> 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)
