aurora-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "brian wickman (JIRA)" <>
Subject [jira] [Commented] (AURORA-1288) Design for supporting custom executor
Date Wed, 24 Jun 2015 22:04:05 GMT


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

This message was sent by Atlassian JIRA

View raw message