[
https://issues.apache.org/jira/browse/AURORA-1288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14601470#comment-14601470
]
Bill Farner commented on AURORA-1288:
-------------------------------------
[~rdelvalle] sounds like you are rethinking things a bit anyhow, but i wanted
to call out one important detail:
{quote}
only the path is passed from the client side
{quote}
This approach raises security concerns, and otherwise couples the client to the
host configuration. IMHO it's very important that the client can only choose
_which_ of the allowable executors to use, and not reference an arbitrary
executor binary on the slave.
I don't think the existing {{ExecutorConfig}} struct needs augmenting for this
feature. We have a means to identify the executor to use, and provide
instructions for what it should do.
{code}
struct ExecutorConfig {
/** Name identifying the Executor. */
1: string name
/** Executor configuration data. */
2: string data
}
{code}
>From a quick read of {{MesosTaskFactory}}, it seems like we could effectively
>have {{Map<String, ExecutorSettings>}} instead of a global
>{{ExecutorSettings}} and be pretty close to done (mod some generalization from
>terms like 'thermos observer').
> 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)
