aurora-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Renan DelValle (JIRA)" <>
Subject [jira] [Commented] (AURORA-1376) Create support for custom executors in Scheduler
Date Thu, 09 Jul 2015 17:56:05 GMT


Renan DelValle commented on AURORA-1376:

[~jaybuff]], you make some great points.

The JSON schema comes from trying to simulate the ExecutorSettings data structure in the Aurora
Scheduler. As I've said previously, the schema is subject to change, so I appreciate your

Here are the reasons why ExecutorSettings, as it exists right now, is different from ExecutorInfo:

a. The ExecutorSettings data struct uses the CommandUtil (org/apache/aurora/scheduler/base/
wrapper to configure the CommandInfo to fetch and execute  given URIs for an executor.  [~wfarner],
is this feature considered part of Aurora or part of Thermos?

b. It also stores info about global container mounts. which it uses when creating docker containers.

If we create an interface, IMO, it should return a TaskInfo.Builder, as that would spare us
from having a special case for the mesos command executor. For what it's worth, an early version
of my code is here I've fixed all the errors that were
caused by my changes and will be putting up a new version up later on today.

As for having the client send in any info to configure the executor, we had a discussion a
short while ago and came to the conclusion, that amongst other things, it is considered a
security risk due to the fact that Aurora runs as root (
Thus, IMO, using a server-side config file is still the best option.

> 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