[jira] [Commented] (MESOS-3401) Add labels to Resources

["Adam B (JIRA)" <ji...@apache.org>]

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

Adam B commented on MESOS-3401:
-------------------------------

While not as explicitly tied to resources as labels would be, I agree that agent attributes are currently sufficient for expressing this metadata. It's a little clunkier for custom resources types, but manageable. As long as all resources on a node of the same type are fungible, we can defer this issue.

However, we'll need to revisit this question when we add external/cluster-wide resources as per MESOS-2728, since these resources are not associated with an agent whose attributes can be tied back to the resources. We could consider adding attributes to the "resource provider", but consider two separate volumes from the same provider. Besides interpreting the resource name/id, how is a framework supposed to know their different speeds/formats/permissions?

We'd probably also have to revisit this when we implement MESOS-191 to allow multiple types of disk resources on a single agent.

> Add labels to Resources
> -----------------------
>
>                 Key: MESOS-3401
>                 URL: https://issues.apache.org/jira/browse/MESOS-3401
>             Project: Mesos
>          Issue Type: Improvement
>          Components: slave
>            Reporter: Adam B
>            Assignee: Greg Mann
>              Labels: external-volumes, mesosphere, resources
>
> Similar to how we have added labels to tasks/executors (MESOS-2120), and even FrameworkInfo (MESOS-2841), we should extend Resource to allow arbitrary key/value pairs.
> This could be used to specify that a cpu resource has a certain speed, that a disk resource is SSD, or express any other metadata about a built-in or custom resource type. Only the scalar quantity will be used for determining fair share in the Mesos allocator. The rest will be passed onto frameworks as info they can use for scheduling decisions.
> This would require changes to how the slave specifies its `--resources` (probably as json), how the slave/master reports resources in its web/json API, and how resources are offered to frameworks.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)