[
https://issues.apache.org/jira/browse/MESOS-3366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14731419#comment-14731419
]
Niklas Quarfot Nielsen commented on MESOS-3366:
-----------------------------------------------
[[email protected]] IMHO this is a cleaner way of having multiple providers of
initial attributes/resources.
Instead of decorators, another integration surface could be the isolators and
extending the api to enable them to populate attributes and initial resources,
but this needs to be invoked prior to slave/agent start. I don't have a strong
preference for which one.
An example could be attributes and resources from a cpu set isolator module
(announcing the NUMA topology), a gpgpu isolator module (announcing it's
core/memory topology) and a device locality program (announcing rack, machine
id, PDU, etc).
We would really like to be able to do this programmatically, as we don't
necessarily control the wrapper scripts users have setup.
> 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)
