[
https://issues.apache.org/jira/browse/MESOS-3366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14737366#comment-14737366
]
Niklas Quarfot Nielsen commented on MESOS-3366:
-----------------------------------------------
Folks; I think this discussion has drifted a bit. Whether or not modules are
stable because they are executed in the context of the master and slave is
outside the scope of this thread.
[~klaus1982] - nothing prevent you from continue using scripts to set
attributes. We need a programmatic way of this this and if you don't have
modules that needs this, you don't have to use this.
The focus of this ticket is module development and extensibility. Making a
decision so we can move forward; we are discussing _how_ we want this interface
to look like. Either through an extension to the isolator or another decorator.
Let's start exploring how these would look like.
Having a one-flag-per-extension sound very scalable to me, compared to have one
interaction point which lets isolators or hooks extend the initial resources
and attributes for the slave.
> 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)
