[
https://issues.apache.org/jira/browse/AURORA-1288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14600158#comment-14600158
]
Renan DelValle commented on AURORA-1288:
----------------------------------------
On the Thrift API side of things, we need to add a path type to the Executor
Config in order to use a custom executor. With this in mind, I'm also thinking
of adding another field to ExecutorConfig which will be an enum that will be
used to dictate which path to take:
Path 1: Use Thermos
Path 2: Use Mesos Executor
Path 3: Use a custom executor
Thus the new ExecutorConfig would look like this:
/** Identifier for Executor to be used. */
enum ExecutorType {
THERMOS = 0
MESOS_COMMAND = 1
CUSTOM = 2
}
struct ExecutorConfig {
/** Name identifying the Executor. */
1: string name
/** Executor configuration data. */
2: string data
/** Defines executor to be used. */
3: ExecutorType type = ExecutorType.THERMOS
/** Optional executor path for custom executors */
4: optional string path
}
The default value would be Thermos.
An alternative would be choosing the path based on the name of the executor
which would cause less breakage but would also be less clean.
It'd be great to get some opinions on the matter.
> 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)
