Description
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.)
Attachments
Issue Links
- relates to
-
AURORA-1493 create ELB-friendly endpoint to detect leading scheduler
- Resolved
-
AURORA-97 Provide a web UI page to show history for a specific job instance
- Resolved