[jira] [Commented] (AURORA-1288) Design for supporting custom executor

["Bill Farner (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AURORA-1288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14505932#comment-14505932 ] 

Bill Farner commented on AURORA-1288:
-------------------------------------

Ultimately there are two major aspects of this:

a. support in the DSL to specify a different executor

b. support in the scheduler to pick a different executor.  The bottom of the stack is at MesosTaskFactory \[1\], which you can trace backwards to see what plumbing is required.

Note that (a) may not be strictly necessary if the command line client is not in play, but it would be a nice outcome.  I would strongly suggest a first cut to enable support for the mesos command executor.  This would prove the plumbing without getting bogged down implementing an executor, minimally deviate from the goal of an alternative executor, and provide good value for the community.

\[1\] https://github.com/apache/aurora/blob/218457b9815a83d1e84598ca1c5912d87720eb5a/src/main/java/org/apache/aurora/scheduler/mesos/MesosTaskFactory.java

> 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)