[ https://issues.apache.org/jira/browse/MESOS-2841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14590805#comment-14590805 ]
Ben Whitehead commented on MESOS-2841: -------------------------------------- I think structured and unstructured can be useful and it probably makes sense to start with the latter. I do feel like it is odd to have the field on {{FrameworkInfo}}, since the only way to send framework info to mesos is to pass it when the scheduler driver is constructed. This info seems more dynamic than a registration time thing. For example if you have a framework that would like to list info based on tasks that are started in the cluster (kafka broker list for example). This is something that isn't known at constructions time, and can change over the life of the process. > 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)