You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Timothy Chen (JIRA)" <ji...@apache.org> on 2015/01/15 19:23:34 UTC

[jira] [Commented] (MESOS-2221) Include supported containerizers in resource offers

    [ https://issues.apache.org/jira/browse/MESOS-2221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14279055#comment-14279055 ] 

Timothy Chen commented on MESOS-2221:
-------------------------------------

I also wonder on the flip side if all the framework wants is to launch docker tasks, is to register and filter offers based on containerizer too.

We're increasingly putting more and more complexity on the framework in general with all the new capabilities, and it becomes a lot more to consider on the framework side.

Perhaps the right answer is to have framework libraries that just handles lots of things.

> 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)