Mailing-List: contact issues-help@aurora.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@aurora.incubator.apache.org
Date: Fri, 20 Mar 2015 04:41:38 +0000 (UTC)
From: "Bill Farner (JIRA)" <jira@apache.org>
To: issues@aurora.incubator.apache.org
Message-ID: <JIRA.12782741.1426642233000.152925.1426826498301@Atlassian.JIRA>
In-Reply-To: <JIRA.12782741.1426642233000@Atlassian.JIRA>
References: <JIRA.12782741.1426642233000@Atlassian.JIRA>
 <JIRA.12782741.1426642233970@arcas>
Subject: [jira] [Commented] (AURORA-1209) the aurora scheduler should proxy
 the executor UI
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ 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)