You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Niklas Quarfot Nielsen (JIRA)" <ji...@apache.org> on 2015/12/04 22:31:11 UTC

[jira] [Commented] (MESOS-3362) Allow Isolators to advertise "capabilities" via SlaveInfo

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

Niklas Quarfot Nielsen commented on MESOS-3362:
-----------------------------------------------

[~vinodkone] They probably overlap. Think these were higher level capabilities. One isolator (say, through sitting within a module with a user/vendor selected name), that one may provide one or more capabilities.
Maybe @mesos-2221 is enough for now. [~karya] what do you think?

> Allow Isolators to advertise "capabilities" via SlaveInfo
> ---------------------------------------------------------
>
>                 Key: MESOS-3362
>                 URL: https://issues.apache.org/jira/browse/MESOS-3362
>             Project: Mesos
>          Issue Type: Task
>            Reporter: Kapil Arya
>            Assignee: Kapil Arya
>              Labels: mesosphere
>
> A network-isolator module can thus advertise that it can assign per-container IP and can provide network-isolation.
> The SlaveInfo protobuf will be extended to include "Capabilities" similar to FrameworkInfo::Capabilities.
> The isolator interface needs to be extended to create `info()` that return a `IsolatorInfo` message. The `IsolatorInfo` message can include "Capabilities" to be sent to Frameworks as part of SlaveInfo.
> The Isolator::info() interface will be used by Slave during initialization to compile SlaveInfo::Capabilities.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)