[
https://issues.apache.org/jira/browse/AURORA-1288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14601731#comment-14601731
]
Bill Farner commented on AURORA-1288:
-------------------------------------
{quote}
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.
{quote}
There are two things preventing this:
- the executor is launched as root as default, allowing for privilege
escalation with a user-specified executor
- the executor is treated as a part of the infrastructure. Failure cases
around the executor itself should raise alarms for cluster operators, making
for a nightmarish support story with arbitrary custom executors.
Both are open for change, but that's the current state of affairs, which to me
suggests that cluster operators should have firm control.
> 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)
