Mailing-List: contact issues-help@mesos.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@mesos.apache.org
Date: Thu, 13 Aug 2015 20:02:45 +0000 (UTC)
From: "Neil Conway (JIRA)" <jira@apache.org>
To: issues@mesos.apache.org
Message-ID: <JIRA.12836849.1433948283000.60169.1439496165823@Atlassian.JIRA>
In-Reply-To: <JIRA.12836849.1433948283000@Atlassian.JIRA>
References: <JIRA.12836849.1433948283000@Atlassian.JIRA>
 <JIRA.12836849.1433948283776@arcas>
Subject: [jira] [Commented] (MESOS-2841) FrameworkInfo should include a
 Labels field to support arbitrary, lightweight metadata
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Neil Conway commented on MESOS-2841:
------------------------------------

[~jdef] Thanks for finishing this off! My apologies for being flaky (vacation/travel, etc.). I'm back now, in case any more work is needed here.

> FrameworkInfo should include a Labels field to support arbitrary, lightweight metadata
> --------------------------------------------------------------------------------------
>
>                 Key: MESOS-2841
>                 URL: https://issues.apache.org/jira/browse/MESOS-2841
>             Project: Mesos
>          Issue Type: Improvement
>            Reporter: James DeFelice
>            Assignee: Neil Conway
>              Labels: mesosphere
>
> A framework instance may offer specific capabilities to the cluster: storage, smartly-balanced request handling across deployed tasks, access to 3rd party services outside of the cluster, etc. These capabilities may or may not be utilized by all, or even most mesos clusters. However, it should be possible for processes running in the cluster to discover capabilities or features of frameworks in order to achieve a higher level of functionality and a more seamless integration experience across the cluster.
> A rich discovery API attached to the FrameworkInfo could result in some form of early lock-in: there are probably many ways to realize cross-framework integration and external services integration that we haven't considered yet. Rather than over-specify a discovery info message type at the framework level I think FrameworkInfo should expose a **very generic** way to supply metadata for interested consumers (other processes, tasks, etc).
> Adding a Labels field to FrameworkInfo reuses an existing message type and seems to fit well with the overall intent: attaching generic metadata to a framework instance. These labels should be visible when querying a mesos master's state.json endpoint.


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