[
https://issues.apache.org/jira/browse/MESOS-3366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14738261#comment-14738261
]
Klaus Ma commented on MESOS-3366:
---------------------------------
I'm OK to use module.
Let me summary this discussion, there're two options to collect for
"resources/attributes discovery":
- Option 1: use module/hook (C++) to collect resources/attributes info
> cons: it's hard for NO C++ developer to collect info
> pros: ??
- Option 2: use script to collect those info, like MESOS-2902 did
> cons: ??
> pros: it's easy to collect info by script, such as CLI by 3rd part
device/driver/tools
Both #1 & #2 need to cover the following cases:
1. How to merge the info from different vendors?
2. How to resolve the conflict with default resources (cpu, mem ...)?
3. How to keep the backward compatibility?
4. any others?
Anyway, my understanding is to adopt #1 for this requirement, and provide an
default module for script. If so, let's continue for the interface of module.
> 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)
