if job tries to reset gpu frequency and nvml is not supported then
log "GpuFreq=control_disabled". Test of this function recognizes
this and exits.

Contiuation of 9a243a1a

Bug 6592

Also mention FIXME's that need to be fixed with this code.

Generated by autoreconf, should never be checked in.

This portion of the code is only for removing the Submit limits from
the partitions the job wasn't going to run on.  Since the job
isn't running on these partitions the node bitmap does not need to be
touched.

Test was relying on seeing future jobs which is no longer the way it
works.

Use SUBDIRS one level above to control build instead of conditionalizing
the build inside of src/plugins/gpu/nvml/Makefile.am.

Just wait for the node to register with Slurm. If it doesn't register
within ResumeTimeout, the node will be marked down.

Continuation of d42889fb

Bug 6587

What was happening in a maintenance reservation was every 5 seconds
the slurmctld was sending a message to the slurmdbd telling it the
node's down/drain state was in a maintenance state as well.  We really
only needed to know about this once.

Bug 6487

(DRAIN+MAINT+IDLE) Before it would just print MAINT
Bug 6487

Bug 6487

Bug 4296

This will be used in future commits.

Bug 4296

GrpTRES behavior was changed with commits 7d69a43a and 158b88de so
that each job allocation is no longer counted separately towards the
GrpTRES limit. This is important for the GrpNodes.

Bug 5303.

to avoid having to send alias list for cloud nodes that exist in DNS.
This is especially important for large cloud environments (e.g.
thousands of nodes) as the alias list environment will be too large for
execve().

Bug 6589

Fix some logic committed in 6705b63c that caused test7.17 to fail

Bug 6587

This is useful in a cloud environment where the nodes come and go out of
DNS.

Bug 6592

bug 6445

Bug 6519.

Continuation of 324404de

Bug 6433

Continuation of c2cdde85

Bug 6433

If a GrpNodes limit is configurated in an association, partition QOS or
job QOS then favor use of nodes already allocated to that entity. This
will result in the configured node "Weight" being incremented by one for
nodes which are not prefered. Consider adjusting configured node "Weight"
values to achieve the desired node preferences.
bug 5303

Same as salloc/sbatch --gres option.

Bug 6582.