[
https://issues.apache.org/jira/browse/MESOS-1810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14138270#comment-14138270
]
brian wickman commented on MESOS-1810:
--------------------------------------
The IP/port for the task container would not be known a priori because it's
possible for the task to be allocated numerous ports. If you want to be sure
that it does not escape the sandbox, you could have it be a (port, path) pair
-- and validate that the port is currently allocated to the executor, then just
assemble ip:port/path
> allow tasks to specify a link to an application-specific UI
> -----------------------------------------------------------
>
> Key: MESOS-1810
> URL: https://issues.apache.org/jira/browse/MESOS-1810
> Project: Mesos
> Issue Type: Improvement
> Components: slave
> Reporter: brian wickman
>
> Right now Aurora requires you to run special UIs (thermos observers) outside
> of Mesos e.g. via puppet/monit/systemd. A single observer manages the UI for
> all tasks on that machine.
> Instead, we'd like to move to a model where the observer UI is embedded
> directly within the executor, however we'd like to make that UI discoverable
> from the slave. What I'm proposing is plumbing into the TaskInfo an optional
> URL to expose via the mesos slave to the UI for that task. This way we don't
> need to reimplement things like sandbox browsing and resource monitoring and
> instead leave that functionality up to the slave, and delegate the
> application-specific information (e.g. "Processes" in the context of Thermos)
> to the application executor UI.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
