[
https://issues.apache.org/jira/browse/MESOS-2841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14580916#comment-14580916
]
James DeFelice commented on MESOS-2841:
---------------------------------------
I think I like the idea of a "shared info" type that, perhaps, contains a
Labels field (generic :) ). It feels more explicit: this is information that
will be shared with mesos and/or mesos clients/frameworks/consumers/etc.
I'm not certain about the visibility/scope of the Capability message - who is
meant to consume this? It appears to be intended for mesos itself, not the
wider cluster. I'm not so sure that stuffing Labels into Capability fits
foreseeable use cases: I can imagine scenario(s) where an admin may want to
label frameworks with metadata that has nothing to do with capabilities.
As you mentioned, webui_url also seems like a good candidate for inclusion in a
"shared info" field.
> 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
> 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)
