[
https://issues.apache.org/jira/browse/MESOS-3366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14745769#comment-14745769
]
Felix Abecassis commented on MESOS-3366:
----------------------------------------
[~cdoyle] [~nnielsen] Thank you for the reviews on my initial patch.
Before I add proper comments and tests, are you fine with this API proposal in
the first place?
For instance, how should we also tackle attributes decoration? Should we add a
second hook or have one hook for both attributes and resources? I would say we
should have 2 different hooks, but it might be at the cost of some code/tests
duplication.
> 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)
