Prevent slurmdbd error if cluster added or removed while rollup in progress.
Removing a cluster can cause slurmdbd to abort. Adding a cluster can cause
the slurmdbd rollup to hang.

Specialized memory (a node's MemSpecLimit configuration parameter) is not
available for allocation to jobs.
Select/linear, cons_res, and serial plugins fixed.
bug 1548

When allocating resources with resolution of sockets, charge the job for a
CPUs on allocated sockets rather than just the CPUs on used cores.

bug 1595

job_submit/lua: Enable reading and writing job environment variables.
For example: if (job_desc.environment.LANGUAGE == "en_US") then ...

The error was being triggered by logic to collect accounting
information starting and not being completed when testing to
start a node ping RPC. In other words, the logic wasn't testing
for the completion of one RPC against the start of that same
RPC, but against the start of a different RPC. This change
moves all of the timeout logic into the ping_nodes.c module
where we can make sure that the timing of different RPCs do
not get confused with each other.
bug 1190

slurmd was logging:
"Error reading step 2031886.0 memory limits" (with various job/step IDs)
because it was treating SLURM_SUCCESS as an error rather than SLURM_ERROR
bug 1589

Disable changes to GRES count while jobs are running on the node.
Previous logic could clear GRES count data and generate counter
underflow then when attemtping to deallocate the job's resources
(including future job terminations when computing when and where
pending jobs will start as part of backfill scheduling logic).
bug 1589

if many steps/jobs finish at once.

* Add "--thread-spec" option to salloc, sbatch and srun commands. This is
  the count of threads reserved for system use per node.
* Add ability for scontrol to get/set job ThreadSpec
* sivew: Add job ThreadSpec field to get/set
* Modify select/cons_res to manage job allocations while leaving specialized
  threads for system use.
* core_spec plugins: Fix system task binding logic and logging
* Modify squeue output for thread_spec values
* task/affinity and cgroup: Enhanced task binding logic

Bug 1587

switch/cray: If CR_PACK_NODES is configured, then set the environment
    variable "PMI_CRAY_NO_SMP_ENV=1"
bug 1585

gating rpcs.

Signed-off-by: Danny Auble <da@schedmd.com>

added back into the system.

* Add "TopologyParam" configuration parameter. Optional value of "dragonfly"
  is supported.
* select/linear: Add dragonfly topology support
* select/cons_res: Add dragonfly topology support

Bug 1578

Bug 1550

their own jobs.

Bug 1469

SPANK naming changes: For environment variables set using the
    spank_job_control_setenv() function, the values were available in the
    slurm_spank_job_prolog() and slurm_spank_job_epilog() functions using
    getenv where the name was given a prefix of "SPANK_". That prefix has
    been removed for consistency with the environment variables available in
    the Prolog and Epilog scripts.
bug 1570

Requests by normal user to reset a job priority (even to lower it) will
result in an error saying to change the job's nice value instead.

A non-administrator change to job priority will not be persistent except
for holding the job. User's wanting to change a job priority on a persistent
basis should reset it's "nice" value.
Without this change a user might lower a job's priority, but Slurm will
not lower it more based upon fair-share changes.

Increase the MAX_PACK_MEM_LEN define to avoid PMI2 failure when fencing
with large amount of ranks (to 1GB).

Verify that all plugin version numbers are identical to the component
attempting to load them. Without this verification, the plugin can reference
Slurm functions in the caller which differ (e.g. the underlying function's
arguments could have changed between Slurm versions).
NOTE: All plugins (except SPANK) must be built against the identical
version of Slurm in order to be used by any Slurm command or daemon. This
should eliminate some very difficult to diagnose problems due to use of old
plugins.