Bug 5395

this logs the GPU configuration from the slurmd perspecitve.
while we don't have tools to load the information directly
from nvidia system configuration, i have confirmed where that
logic needs to go and the data structure contents.

# Conflicts:
#	doc/html/faq.shtml
#	src/slurmctld/job_mgr.c

Bug 5390

Continuation of 923c9b37.

There is a delay in the cgroup system when moving a PID from one cgroup
to another. It is usually short, but if we don't wait for the PID to
move before removing cgroup directories the PID previously belonged to,
we could leak cgroups. This was previously fixed in the cpuset and
devices subsystems. This uses the same logic to fix the freezer
subsystem.

Bug 5082.

cpuset and devices subsystems have duplicate code to cleanup the cgroup
and prevent leaking cgroups by moving the process to the root cgroup and
waiting for it to be moved.

Move this duplicate code to a common function so it can be used later by
the freezer subsystem.

Bug 5082.

Bug 5227

bug 5337

the database.

Bug 5247

Previous logic could trigger KNL node reboot when job did not
request any KNL MCDRAM or NUMA modes as features. For example:
srun -N3 -C "[foo*1&bar*2]" hostname
would trigger reboot of all KNL nodes even though no KNL-specific
features were requested. This bug only exists in v18.08 and was
introduced when expanding KNL node feature specification capabilities.

Invoke select_g_job_test() one time with all valid node rather than
multiple times when adding higher weight nodes. This results in
the job allocation always accumulating nodes from lower to higher
weights rather than possibly using mostly higher weight nodes.
It also streamlines the resource allocation process for most
configurations by eliminating some repeated logic as groups
of nodes are added for consideration by the select plugin.

bug4451

So that multiple nodes changes will be reported on one line rather than one
line per node. Otherwise this could lead to performance issues when reloading
slurmctld in big systems.

Bug4980

Cleaned up code that could've caused performance issues when reading config
and there was nodes with features defined.

bug4980

fix for commit 4a0a6a94
bug 4821

bug 4821

Add 64-bit sched_weight (scheduling weight) to node_set struct
Populate it with the node's weight (possibly reboot weight)
plus high-order bits for FLEX-reservation and rebooting.
No longer are node weights of INFINITE or (INFINITE-1) used
to flag FLEX or reboot requirements so we don't need to
worry about overlapping node weight values. It also will
cleanly allow the cons_tres plugin to be passed ALL usable
nodes at one time to accumulate resources from the lowest
weight first and only use individual higher weight nodes
as needed (rather than possibly using mostly higher
weight nodes).
bug 4821

breaks out node sets by in/out flex reservation and need to reboot
bug 4821

Slurm numbers the cores using an abstract index, starting from CPU 0
on the first socket, core, thread, and continuing until N on the last socket,
last core, last thread. Explain that in the documentation.

bug 5189

The node weight of a node requiring reboot is not a fixed value
in v18.08, but configurable
bug 4821

bug 5337

bug 5337

Currently, no caller checks the return code.

Bug 5164

bug 5337

This test change addresses gres api changes introduced in commit
6e0469b5

Can't have # character in the password since it is treated as a comment.

Bug 5294

Implicitly set node count, task count, ntasks_per_* as appropriate