You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Miguel Bernadin (JIRA)" <ji...@apache.org> on 2016/10/31 22:18:58 UTC
[jira] [Commented] (MESOS-6369) Add a column for FrameworkID when
displaying tasks in the WebUI
[ https://issues.apache.org/jira/browse/MESOS-6369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15623594#comment-15623594 ]
Miguel Bernadin commented on MESOS-6369:
----------------------------------------
[~kaysoky], Sumbitted for review https://reviews.apache.org/r/53324/ to this that changes that look like this with modified field names:
|| Framework ID || Task ID || Task Name || State || Started || Host || ||
| 179b5436-30ec-45e9-b324-fa5c5a1dd756-0000 | 1 | My ambiguously named task | RUNNING | 1 minute ago | 10.10.0.1 | Sandbox |
| 179b5436-30ec-45e9-b324-fa5c5a1dd756-0001 | 1 | My ambiguously named task | RUNNING | 1 minute ago | 10.10.0.1 | Sandbox |
| 179b5436-30ec-45e9-b324-fa5c5a1dd756-0001 | 2 | My ambiguously named task | RUNNING | 1 minute ago | 10.10.0.1 | Sandbox |
> Add a column for FrameworkID when displaying tasks in the WebUI
> ---------------------------------------------------------------
>
> Key: MESOS-6369
> URL: https://issues.apache.org/jira/browse/MESOS-6369
> Project: Mesos
> Issue Type: Improvement
> Components: webui
> Reporter: Joseph Wu
> Assignee: Miguel Bernadin
> Priority: Minor
> Labels: mesosphere, newbie
>
> The Mesos Web UI home page shows a list of active/completed/orphan tasks tasks like this:
> || ID || Name || State || Started || Host || ||
> | 1 | My ambiguously named task | RUNNING | 1 minute ago | 10.10.0.1 | Sandbox |
> | 1 | My ambiguously named task | RUNNING | 1 minute ago | 10.10.0.1 | Sandbox |
> | 2 | My ambiguously named task | RUNNING | 1 minute ago | 10.10.0.1 | Sandbox |
> When you start multiple frameworks, the task IDs and names show in the UI may be ambiguous, requiring extra clicks/investigation to disambiguate.
> In the above case, to disambiguate between the two tasks with ID {{1}}, the user would need to navigate to each sandbox and check the associated frameworkID in the {{/browse}} view.
> We could add a column showing the {{FrameworkID}} next to each task:
> || Framework || ID || Name || State || Started || Host || ||
> | 179b5436-30ec-45e9-b324-fa5c5a1dd756-0000 | 1 | My ambiguously named task | RUNNING | 1 minute ago | 10.10.0.1 | Sandbox |
> | 179b5436-30ec-45e9-b324-fa5c5a1dd756-0001 | 1 | My ambiguously named task | RUNNING | 1 minute ago | 10.10.0.1 | Sandbox |
> | 179b5436-30ec-45e9-b324-fa5c5a1dd756-0001 | 2 | My ambiguously named task | RUNNING | 1 minute ago | 10.10.0.1 | Sandbox |
> The {{FrameworkID}} s could be links to the associated framework
> {code}
> <a href="{{'#/frameworks/' + framework.id}}" title="{{framework.id}}">
> {{framework.id | truncateMesosID}}
> </a>
> {code}
> -----
> This involves additions to three tables:
> https://github.com/apache/mesos/blob/1.0.x/src/webui/master/static/home.html#L152-L157
> https://github.com/apache/mesos/blob/1.0.x/src/webui/master/static/home.html#L199-L205
> https://github.com/apache/mesos/blob/1.0.x/src/webui/master/static/home.html#L246-L252
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)