[
https://issues.apache.org/jira/browse/MESOS-2841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14590482#comment-14590482
]
James DeFelice commented on MESOS-2841:
---------------------------------------
My initial goal was to get a simple message/structure into Framework that we
could use for discovery purposes. Understand your concerns about long term
affects. The DiscoveryInfo message has Ports -- doesn't really make sense for
frameworks. With respect to the other fields, it's arguable whether they're all
valuable for framework discovery. But I do like the Labels :)
Perhaps I misunderstand how the term Resource is used within mesos -- has this
changed recently? My understanding was that Resources are allocatable/freeable
things that are advertised to other frameworks within resource offers. In the
above examples, the "resources" you've listed look more like advertisements for
*usable* things that don't have any specific capacity constraints.
> 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)
