Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
New dashboard in Singularity + other UI improvements #1636
@kwm4385 , this is the WIP PR we can build upon for creating user and group based views within Singularity. I have created a separate dropwizard resource with new pojos that will aggregate all data the UI needs for certain pages in a single call. We may need to do some extra bits around things like history paging and such, but we can at least get the basic details of active elements all in a single call, with some extra details like instance health included.
My goal with this would be to replace the current dashboard page with something smarter, generally eliminating the need for the requests page, as well as adding some needed details like instance health in the task detail page.
We should also try to eliminate some extraneous calls we tend to make on a number of pages like:
Feel free to comment on anything you might specifically want the backend to serve up all together. I'll add more detail here as I flush things out
@kwm4385 I put together a quick 15-minute version of a new dashboard, mostly so that the logic is all written out for you to see the new data the backend is providing for you (and because I got angry at auth and wanted to take a break from it...).
Ordering by default is based on requests that have most recently had something interesting happen, and the list of requests is filtered (by the backend) to ones that are relevant to the user.
As an additional note, the tasks piece is a bit more of an expensive api call when done across a large number of requests, so it won't be feasible to use for the normal requests page. Using it here for dashboard since the list by nature is slimmed down.
changed the title from
WIP - User/Group-based views in Singularity
WIP - User/Group-based dashboard in Singularity
Oct 24, 2017
Icons replace text for request types and statuses to save space:
Don't show full task ID on the request detail page to save space:
Some thoughts on the current iteration: