Based upon patch from Hongjia Cao
bug 2054

as it is the only TRES that can be given to another job while suspended.

sbatch --ntasks option to take precedence over --ntasks-per-node plus node
    count, as documented. Set SLURM_NTASKS/SLURM_NPROCS environment variables
    accordingly.
bug 2015

Avoid reporting more allocated CPUs than exist on a node. This can be
    triggered by resuming a previosly suspended job, resulting in
    oversubscription of CPUs.
bug 2021

Add scancel -f/--full option to signal all steps including batch script and
    all of its child processes.
bug 2031

Bug 1888

out.

Remove unneeded code that commit 8274ea54 fixed.

This code would 0 out all GRES/TRES on a reconfig which isn't what we want.

8274ea54 does the right thing by itself.

bug 2032

Add ValidateTimeout and OtherTimeout to "scontrol show burst" output.
These new configuration parameters were added to v15.08.2, but could
not be added to the display without changing the RPC (in v16.05).
Commit to add the parameters: 25fcc9db

Needed to change a couple of variables from 32- to 64-bit.

Add new burst_buffer.conf parameters: ValidateTimeout and OtherTimeout.
See man page for details.

previously take 2 restarts of the slurmdbd to make it stick correctly.

single-threaded cores.  A regression caused only 1 socket to be used on
this kind of node instead of all that were available.

If the backup dbd happened to be doing rollup at the time the primary resumed
both the primary and the backup would be doing rollups and causing contention on
the database tables. The backup would wait for the rollup handler to finish
before giving up control.

The fix is to cancel the rollup_handler and let the backup begin to shutdown so
that it will close an existing connections and then re-exec itself. The re-exec
helps because the rollup handler spawns a thread for each cluster to rollup and
just cancelling the rollup handler doesn't cancel the spawned threads from the
rollup handler. This cleans up the dbd and locks. The re-exec only happens in
the backup if the primary resumed and a rollup was happening.

Bug 1988

Fix case where if the backup slurmdbd has existing connections when it gives up control that the it would be killed.

If the backup had existing connections when giving up control, it would try to
signal the existing threads by using pthread_kill to send SIGKILL to the
threads. The problem is that SIGKILL doesn't go the thread but the main process
and the backup dbd would be killed.

when a cold-start (-c) happens to the slurmctld.

This was intended as a step toward managing jobs across mutliple
  clusters, but we will be pursuing a very different design.

from a user.

This would cause the slurmctld to cache the old default which wasn't valid
and cause the user to have to request the association always.

byg 2013

database but the start record hadn't made it yet.

Add acct_gather_energy/ibmaem plugin for systems with IBM Systems Director
    Active Energy Manager.

requirements.

Add acct_gather_energy/ibmaem plugin for systems with IBM Systems Director
    Active Energy Manager.

bug 2011