[
https://issues.apache.org/jira/browse/MESOS-3366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14731384#comment-14731384
]
Niklas Quarfot Nielsen commented on MESOS-3366:
-----------------------------------------------
I like the idea of having decorators for attributes and resources; I think
composability is the biggest issue. How to you have one vendor component add
it's attributes and combine with presets and other vendor attributes?
Secondly, distribution is an issue in terms of messing with existing script
wrappers (which varies between distribution/setup).
Imagine the scripts you would have to wrap to get cpu/NUMA topologies, gpu
topologies, device lists (see the device cgroup ticket).
> Allow resources/attributes discovery
> ------------------------------------
>
> Key: MESOS-3366
> URL: https://issues.apache.org/jira/browse/MESOS-3366
> Project: Mesos
> Issue Type: Improvement
> Components: slave
> Reporter: Felix Abecassis
>
> In heterogeneous clusters, tasks sometimes have strong constraints on the
> type of hardware they need to execute on. The current solution is to use
> custom resources and attributes on the agents. Detecting non-standard
> resources/attributes requires wrapping the "mesos-slave" binary behind a
> script and use custom code to probe the agent. Unfortunately, this approach
> doesn't allow composition. The solution would be to provide a hook/module
> mechanism to allow users to use custom code performing resources/attributes
> discovery.
> Please review the detailed document below:
> https://docs.google.com/document/d/15OkebDezFxzeyLsyQoU0upB0eoVECAlzEkeg0HQAX9w
> Feel free to express comments/concerns by annotating the document or by
> replying to this issue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
