Mehdi Dogguy
Mehdi Dogguy
It may happen that the filesystem become read-only (e.g. when many IO errors occur or a disk is detected faulty). In such cases, NHC tries to write its log file...
With #141, it became possible to click on a used wckey to use it as a filter in the jobs view. Another required method is to be able to enter...
Details about what should be shown are still to be defined.
If possible.
It should be possible to add the following columns: - def_mem_per_cpu - max_mem_per_cpu - deny_accounts - deny_qos - allow_qos - priority - default_time - allow_accounts - max_cpus_per_node - max_share -...
Such view should list known issues (drain reasons, down nodes, dates about issues, users, ...)
When a user lands on the dashboard (and even after connection), all configured clusters all shown. A user might have access to a subset only. So it doesn't seem relevant...
The interface only shows "available" and "reserved" states. Other states are not considered somehow.