[
https://issues.apache.org/jira/browse/MESOS-1828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14150175#comment-14150175
]
Adam B commented on MESOS-1828:
-------------------------------
Love it. Of course, if it's in FrameworkInfo, we'll have to support updating
FrameworkInfo on reregistration (MESOS-703, MESOS-1784). Otherwise, the
original API/UI URL will be invalid on framework failover to a new machine.
Interesting to consider if this should be an explicit protobuf or generic
framework label/attribute.
> The Mesos UI should link to framework UIs
> -----------------------------------------
>
> Key: MESOS-1828
> URL: https://issues.apache.org/jira/browse/MESOS-1828
> Project: Mesos
> Issue Type: Wish
> Reporter: Tobi Knaup
>
> Most frameworks have a web UI or HTTP API. It would be nice to show a direct
> link from the Mesos web UI so it's easy to navigate there. Currently a user
> needs to know where schedulers are running, Mesos doesn't have that knowledge.
> A framework should provide a URL to its API/UI when it connects, as part of
> FrameworkInfo. This could be explicit proto fields (e.g. gui_url, api_url),
> or more generic key/value pairs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
