You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@aurora.apache.org by "Simon poortman (Jira)" <ji...@apache.org> on 2019/11/20 01:07:00 UTC
[jira] [Updated] (AURORA-216) allow aurora executor to be
customized via the commandline
[ https://issues.apache.org/jira/browse/AURORA-216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Simon poortman updated AURORA-216:
----------------------------------
Attachment: 868B572E-EEAF-4F80-9818-910F84292289.jpeg
> 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
> Attachments: 868B572E-EEAF-4F80-9818-910F84292289.jpeg
>
>
> 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
(v8.3.4#803005)