Details
-
Task
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
2.1.0
-
None
Description
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.
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
- On finding no layout for HBASE service, get the default stack data:
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
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.
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
On finding a layout for HBASE service, load all the widget and order them accordingly