aurora-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jay Buffington (JIRA)" <>
Subject [jira] [Commented] (AURORA-1376) Create support for custom executors in Scheduler
Date Wed, 08 Jul 2015 04:55:05 GMT


Jay Buffington commented on AURORA-1376:

Glad to see there is progress on this!

IMHO, it's odd and confusing that your JSON here doesn't map more closely to the ExecutorInfo
that will go into the protobuf we send to the mesos master (see
 For example, executorFlags is something that is set in a CommandInfo which goes inside the

Also, the mesos-command executor is this odd duck because it's the executor you get when you
don't specify an ExecutorInfo.  

I think we're going to have a plugin model.  I would start by implementing an abstract class
which you would have to implement if you wanted to use a custom executor.  Initially, I would
just provide two implementations: one for thermos and one for the mesos executor.  We can
get fancy and do dynamic loading of alternative plugins in the second phase.

Which plugin to use would be driven by the thrift request the client sent.  I think your JSON
configuration is still necessary, but I each config is unique for the plugin.  The rest of
the schedule would treat that configuration opaquely.

We could have a couple of command line options to support this.

       "thermos": {
           // configuration only thermos plugin understand goes here
       "foo": {
           // config for foo executor

(the json for --executors-config needs to be properly escaped, but you get the idea)

> Create support for custom executors in Scheduler
> ------------------------------------------------
>                 Key: AURORA-1376
>                 URL:
>             Project: Aurora
>          Issue Type: Sub-task
>          Components: Scheduler
>            Reporter: Renan DelValle

This message was sent by Atlassian JIRA

View raw message