mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Neil Conway (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MESOS-5675) Add support for master capabilities
Date Tue, 10 Jan 2017 18:55:58 GMT

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

Neil Conway commented on MESOS-5675:
------------------------------------

Not AFAIK -- makes sense to consider adding that as well. I'll create a JIRA.

> Add support for master capabilities
> -----------------------------------
>
>                 Key: MESOS-5675
>                 URL: https://issues.apache.org/jira/browse/MESOS-5675
>             Project: Mesos
>          Issue Type: Improvement
>          Components: master
>            Reporter: Neil Conway
>              Labels: mesosphere
>
> Right now, frameworks can advertise their capabilities to the master via the {{FrameworkInfo}}
they use for registration/re-registration. This allows masters to provide backward compatibility
for old frameworks that don't support new functionality.
> To allow new frameworks to support backward compatibility with old masters, the inverse
concept would be useful: masters would tell frameworks which capabilities are supported by
the master, which the frameworks could then use to decide whether to use features only supported
by more recent versions of the master.
> For now, frameworks can workaround this by looking at the master's version number, but
that seems a bit fragile and hacky.



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

Mime
View raw message