[
https://issues.apache.org/jira/browse/MESOS-3401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14909310#comment-14909310
]
Greg Mann commented on MESOS-3401:
----------------------------------
Ah right, good point [~qianzhang] :-) So, one possible use case is that of
external volumes, where a given agent may have access to "disk" resources of
multiple types, and the availability of those types may change over time. In
this case, it would be beneficial to have labels associated with specific
resources in order for the agent to advertise their availability properly, i.e.
if the agent in general has access to two types of external volumes, but one of
them is currently unavailable, the label could be used to offer just one type
of external volume on that agent. What do you think about this feature in
relation to that use case?
Looking back on [~nnielsen]'s comment, it does seem that the "set" type could
be used to accomplish this, but this would mean that for a given external
volume, all of its attributes would be represented as strings, which isn't
ideal for the communication of disk size. It would also mean that the framework
would have to rely on a specific ordering of the members of the set in order to
identify its contents.
> 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: 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)
