[
https://issues.apache.org/jira/browse/MESOS-5735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15355322#comment-15355322
]
zhou xing commented on MESOS-5735:
----------------------------------
[~vinodkone], I did a primary investigation on WebUI today, here I listed the
WebUI related http api calls:
1. call to */master/state*:
most of the pages in WebUI relies on this request to get FRAMEWORK, AGENT,
OFFER, TASK and EXECUTOR objects. Our newly proposed GetState message can
satisfy almost all the requirements from these pages, except for the following
fields:
• {{state.leader}} and {{state.pid}}: these fields are used to decide
whether current master is leading master, if not, ui will redirect
• {{clustername}}, {{version}}, {{build_time}}, {{start_time}},
{{elected_time}}: these fields will be shown on WebUI.
• {{log_dir}} && {{external_log_dir}}: these fields will be used when user
clicks the LOG link on the home page.
2. call to */slave/state*:
when browsing a single agent information on WebUI(select to open one single
Agent on Agents page), WebUI will call */slave/state* endpoint to get the
detail information of that slave, I think we still need to work out how slave's
{{GetState}} message look like. There should be differences between master's
{{GetState}} message and slave's {{GetState}} message. e.g. the executor
information returned by slave's */state* endpoint now will return three more
fields: {{queued_tasks}}, {{active_tasks}} and {{completed_tasks}}, these three
fields are not in master's executor message.
3. call to */files/browse* and */files/read*
The new two operator v1 files API should have the same functionality with the
previous http api.
4. call to */metrics/snapshot* for both master and agent
The metrics api should have same set of metrics.
5. call to slave's */monitor/statistics* endpoint
I happened to see this endpoint in current WebUI's code, but when I tried to
visit WebUI by launching master, agent and long-lived-framework, I can not see
this endpoint call in HTTP call history. Also, operator V1 API epic does not
contain a ticket for this endpoint, are we still using this API now?
> Update WebUI to use v1 operator API
> -----------------------------------
>
> Key: MESOS-5735
> URL: https://issues.apache.org/jira/browse/MESOS-5735
> Project: Mesos
> Issue Type: Bug
> Reporter: Vinod Kone
> Assignee: zhou xing
>
> Having the WebUI use the v1 API would be a good validation of it's usefulness
> and correctness.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
