[
https://issues.apache.org/jira/browse/AURORA-1376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14622929#comment-14622929
]
Meghdoot Bhattacharya commented on AURORA-1376:
-----------------------------------------------
I would want to keep the design simple at this point for first iteration. If
you look at Marathon, everything is specified from client end for custom
executors. One does not need to decorate tasks for custom executors in
scheduler side. Now if you look at the original discussion with Bill in
Aurora-1288, Bill favored for security reasons (for now) and also to avoid
changing the thrift interface, to just map the executor name passed from client
to a server side configuration. So, that is how its progressing. And I think we
should not require plugin classes (not even optional) based on executors to
construct the mesos task. We should keep the goal at one point we may pass in a
detailed executor config object from client itself and have zero configuration
in scheduler and keep the scheduler agnostic.
The data blob currently from client side gives the opportunity to pass in any
custom payload for the executor through Mesos task and Thermos uses it and any
custom executor should use it.
> Create support for custom executors in Scheduler
> ------------------------------------------------
>
> Key: AURORA-1376
> URL: https://issues.apache.org/jira/browse/AURORA-1376
> Project: Aurora
> Issue Type: Sub-task
> Components: Scheduler
> Reporter: Renan DelValle
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
