[jira] [Commented] (MESOS-2841) FrameworkInfo should include a Labels field to support arbitrary, lightweight metadata

["Niklas Quarfot Nielsen (JIRA)" <ji...@apache.org>]

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

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

Great idea [~jdef]! Let us take a look at how this would look like.

Changing those during reregistration may need a special path and we need to make sure they are accessible through the state endpoints.

We introduce the notion of webui_url - maybe they should both be encapsulated in a SharedFrameworkInfo message (without any ties to the name - feel free to come up with another über message to encapsulate this in).

We also have a 'framework capability' message now (introduced during the oversubscription work). Would it make sense to put in there perhaps?

I have no strong preference at this point, but just exploring different approaches :)

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