[
https://issues.apache.org/jira/browse/AURORA-1209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14370711#comment-14370711
]
Bill Farner commented on AURORA-1209:
-------------------------------------
I think the scheduler has information it can and should display for an instance
(see AURORA-97). However, proxying still has merit and should be considered.
> 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
> 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)
