[
https://issues.apache.org/jira/browse/AURORA-1288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14600246#comment-14600246
]
brian wickman commented on AURORA-1288:
---------------------------------------
Any reason for the distinction between 'Thermos' and 'custom executor'? For
all intents and purposes, Thermos *is* a custom executor.
I'm reluctant to see an ExecutorType enumeration, because it means adding a new
executor type means updating the thrift API. If we bind an executor
implementation to a name, then it's easier to provide it dynamically as a
module on the classpath for example. And by executor implementation, I mean
something that can translate an ExecutorConfig to a specific mesos task to be
launched.
> 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)
