mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Niklas Quarfot Nielsen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MESOS-2841) FrameworkInfo should include a Labels field to support arbitrary, lightweight metadata
Date Wed, 17 Jun 2015 20:43:00 GMT

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

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

Labels are trading off structure for generality. I think both key/value pairs _and_ structured
capabilities could be useful.

I have a hard time reasoning that these are resources though and the resource math becomes
complicated.

It is small change to enable the framework info to set these key value pairs until we have
widespread use-cases for structured 'capabilities' (for example; messages describing 'I am
a storage framework and can be accessed this way, etc.')

Wrapping Labels in a envelope message would give us freedom to do that.

> 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: Epic
>            Reporter: James DeFelice
>              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)

Mime
View raw message