[
https://issues.apache.org/jira/browse/AURORA-216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13904848#comment-13904848
]
brian wickman commented on AURORA-216:
--------------------------------------
There is no reason that the GC executor can't be restructured to act the same
way -- just implement an interface for cleanup hooks and allow them to be
specified on the command-line as well (this is probably how things should have
been done in the first place.) However, we need to estimate how long until the
registrar is available to determine if this work is worth it.
> allow aurora executor to be customized via the commandline
> ----------------------------------------------------------
>
> Key: AURORA-216
> URL: https://issues.apache.org/jira/browse/AURORA-216
> Project: Aurora
> Issue Type: Story
> Components: Executor
> Reporter: brian wickman
> Priority: Minor
>
> Right now the AuroraExecutor takes runner_provider, sandbox_provider and
> status_providers. These need to be the following:
> - runner_provider: TaskRunnerProvider (assigned_task -> TaskRunner)
> - status_providers: list(StatusCheckerProvider) (assigned_task ->
> StatusChecker)
> - sandbox_provider: SandboxProvider (assigned_task -> SandboxInterface)
> These are generic enough that we should allow these to be specified on the
> command line as entry points, for example, something like:
> {noformat}
> --runner_provider
> apache.aurora.executor.thermos_runner:ThermosTaskRunnerProvider
> --status_provider
> apache.aurora.executor.common.health_checker:HealthCheckerProvider
> --status_provider myorg.zookeeper:ZkAnnouncerProvider
> --sandbox_provider myorg.docker:DockerSandboxProvider
> {noformat}
> Then have these loaded up using pkg_resources.EntryPoint. These plugins can
> either be linked into the .pex or injected onto the PYTHONPATH of the
> executor.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
