[
https://issues.apache.org/jira/browse/AURORA-1288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14601675#comment-14601675
]
Meghdoot Bhattacharya commented on AURORA-1288:
-----------------------------------------------
We can go back to mapping executor name and path on the scheduler/framework
side. Well if the hosts are compromised, then we have bigger issues. In the end
either client has to be aware or the scheduler has to be aware. One can make
the case that frameworks stays completely agnostic of types of workloads and
its executors and not have to update scheduler each time if a new executor is
introduced. But on the other hand, in practical situations there wont be new
executors popping each day.
> Design for supporting custom executor
> -------------------------------------
>
> Key: AURORA-1288
> URL: https://issues.apache.org/jira/browse/AURORA-1288
> Project: Aurora
> Issue Type: Task
> Reporter: Meghdoot Bhattacharya
>
> The goal is to capture the list of changes in the client and the scheduler
> required to support any executor other than thermos. This will help non
> thermos use cases to adopt aurora easily.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
