[
https://issues.apache.org/jira/browse/MESOS-3401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14909156#comment-14909156
]
Qian Zhang commented on MESOS-3401:
-----------------------------------
[~greggomann], I understand your point, and for the case you mentioned above, I
fully agree with you that it does not mean sense to have the different resource
names, like cpus2000, cpus2100, it should just be the "cpus". However, to
handle the heterogeneous cluster with CPUs of many different speeds, do we have
to specify the speed in the "cpus" resource as a label of it? My thinking is,
in this case, we can just specify the speed as an attribute of the agent
(slave). You know, usually in one agent, all its CPUs should have the same
speed/model :-) So basically, as [~nnielsen] mentioned, we need a valid use
case for this improvement.
> 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)
