[2.2b4] Implement paging for all node logs and results

Bug #1677940 reported by Ante Karamatić on 2017-03-31
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

In new design XML and YAML are expanded by default. Sometimes XML can be few MBs big and this means that on slower connections it will take some time before the machine page loads. Rendering that kind of page is also challenging for some browsers.

Tabs look nice, but collapsing Machine outputs yaml/xml by default would make machine page even better.

Andres Rodriguez (andreserl) wrote :

fwiw, it is the same case in the old design. XML/YAML output has always been expanded by default and has always been available.

Changed in maas:
importance: Undecided → Medium
tags: added: performance
Changed in maas:
milestone: none → 2.2.0
status: New → Triaged
Mike Pontillo (mpontillo) wrote :

I think it's strange that deployment output appears on the Commissioning tab; it seems like the current "Machine output" is a detail of commissioning, and deployment output should be called out separately somehow, either on a separate tab or collapsed by default as suggested.

tags: added: ux
Changed in maas:
milestone: 2.2.0 → 2.2.0rc2
Changed in maas:
milestone: 2.2.0rc2 → 2.2.0rc3
Changed in maas:
milestone: 2.2.0rc3 → 2.2.1
Changed in maas:
milestone: 2.2.1 → 2.2.x
Changed in maas:
milestone: 2.2.x → 2.4.x
Lee Trager (ltrager) wrote :

In 2.4 logs are only sent over the websocket when on the logs tab. This should help with the performance on all other pages. We could improve upon it some more by implementing paging with text files and caching results on the client. This effects commissioning and testing results as well.

summary: - [2.2b4] XML/YAML output is huge and increases machine page load time
+ [2.2b4] Implement paging for all node logs and results
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers