Add cluster-specific filters by default

[nickjer]

A suggestion by Martin Cuma was adding to the current "My Jobs" and "All Jobs" filtering the ability to further break it down to cluster-specific views as well.

Maybe buttons are not the ideal way of going about this, so if we add this feature a design proposal may be necessary.

Original text:

In either case, for the multi-cluster environment like ours, it's be good if the "Jobs" menu in the Dashboard showed each cluster separately, perhaps both for All Jobs and My Jobs. Or, even better, for My Jobs scan all the clusters.

I figure we can do this ourselves with the Custom Filter as you describe here: https://github.com/OSC/ood-activejobs but, not knowing anything about the OOD internal data structures, I don't know how to modify the example for something like that.

[nickjer]

Two other reasons for cluster-only views:

• there is a cluster named "ash" but a lot of users have job names called "bash"
• if there are a lot of clusters, calling qstat on all of them can be time consuming making the "All Jobs" load time unacceptable

[brianmcmichael]

The difficulty here is that the Job objects don't have any reference to the host that they are derived from. One option would be to add a second button row that allows for sorting by cluster. This would require an additional parameter on each request but wouldn't be all that difficult to implement. I would then filter in the controller prior to the adapter request, instead of relying on the current method of querying all hosts and filtering based on that.

[ericfranz]

A wrinkle in that is if there is only one cluster we wouldn't show this second list of filter options.

Also for clusters, maybe we consider a button dropdown (or just a normal dropdown):

[nickjer]

You could also replicate @ericfranz's dropdown idea for the "My Jobs" and "All Jobs" buttons as well as any filter buttons.

• My Jobs
• Filter1

• Filter2

• All Jobs