[jira] [Comment Edited] (AURORA-1209) the aurora scheduler should proxy the executor UI

["brian wickman (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AURORA-1209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14744432#comment-14744432 ] 

brian wickman edited comment on AURORA-1209 at 9/14/15 10:54 PM:
-----------------------------------------------------------------

Linking these two tickets together as I feel they're important for AWS deployments.  It would also be more secure as we can centralize authorization rules behind a kerberized scheduler.


was (Author: wickman):
Linking these two tickets together as I feel they're important for AWS deployments.

> the aurora scheduler should proxy the executor UI
> -------------------------------------------------
>
>                 Key: AURORA-1209
>                 URL: https://issues.apache.org/jira/browse/AURORA-1209
>             Project: Aurora
>          Issue Type: Story
>          Components: Scheduler, Usability
>            Reporter: brian wickman
>
> Right now there are meaningful endpoints for:
>   /scheduler
>   /scheduler/role
>   /scheduler/role/env
>   /scheduler/role/env/jobname
> But no meaningful endpoint for
>   /scheduler/role/env/jobname/instanceid
> It would be a much better user experience if the scheduler had a simple HTTP proxy to proxy the executor UI (if defined by the ExecutorConfig.)  This will simplify migrating the thermos observer into the executor and provide a much better story for deploying Aurora (one less required moving part.)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)