ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-10171) Widget layout on service summary page should be API driven
Date Mon, 23 Mar 2015 15:47:11 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-10171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14376079#comment-14376079
] 

Hadoop QA commented on AMBARI-10171:
------------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12706517/AMBARI-10171.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:green}+1 tests included{color}.  The patch appears to include 2 new or modified
test files.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of
javac compiler warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number
of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in .

Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/2111//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/2111//console

This message is automatically generated.

> Widget layout on service summary page should be API driven
> ----------------------------------------------------------
>
>                 Key: AMBARI-10171
>                 URL: https://issues.apache.org/jira/browse/AMBARI-10171
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-web
>    Affects Versions: 2.1.0
>            Reporter: Andrii Tkach
>            Assignee: Andrii Tkach
>             Fix For: 2.1.0
>
>         Attachments: AMBARI-10171.patch
>
>
> We can verify the work by using this mock data. As of now HBase service mock data has
line graph, multiline graph, stack graph and Number. These needs to be implemented for service
summary page under this ticket.
> *Scenario 1: widget_layout for a user does not have default_servicename_layout*
> On loading of a service summary page:
> * Get the widget_layout specific to that page and user. 
> {code}
> real url: http://c6401.ambari.apache.org:8080/api/v1/users/admin/widget_layouts?section_name=HBASE_SUMMARY&fields=widgetLayoutInfo/*
> mock url: /data/widget_layouts/HBASE/empty_user_layout.json
> {code}
> * On finding no layout for HBASE service, get the default stack data:
> {code}
> real url: http://c6401.ambari.apache.org:8080/api/v1/stacks/HDP/2.2/artifacts/services/HBASE/widget_descriptor
> mock_url: /data/widget_layouts/HBASE/stack_layout.json
> {code}
> Order of the widgets will also be perceived from the same API call.
> Do a lazy loading of the widgets on service summary page. 
> *Scenario 2: widget_layout for a user has default_servicename_layout*
> On loading of a service summary page:
> * Get the widget_layout specific to that page and user. 
> {code}
> real url: http://c6401.ambari.apache.org:8080/api/v1/users/admin/widget_layouts?section_name=HBASE_SUMMARY&fields=widgetLayoutInfo/*
> mock url: /data/widget_layouts/HBASE/filled_user_layout.json
> {code}
> On finding a layout for HBASE service, load all the widget and order them accordingly



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message