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.

Bug 1469
Return values from void functions are unknown and were causing
list_for_each to short ciruit processing of the job list.

Fix for misleading job submit failure errors sent to users. Previous error
could indicate why specific nodes could not be used (e.g. too small memory)
when other nodes could be used, but were not for another reason.
bug 1537

Modify the command names per latest Cray documentation.
Add Cray API calls, which will replace the Cray command line
  interfaces when available. More work will be required for
  this conversion to the APIs.
Update documentation.

Correct the job array specification parser to accept brackets in job array
expression (e.g. "123_[4,7-9]").
This patch superseeds patch 8d811201
bug 1552

The logic fails if there are commas in the brackets:
slurmctld: job_str_signal: 3 invalid job id 1593_[2,5-6]
Updated patch in next commit
bug 1552

RequeueExit and RequeueExitHold configuration parameters modified to accept
numeric ranges. For example "RequeueExit=1,2,3,4" and "RequeueExit=1-4" are
equivalent.
bug 1549

If SchedulerParameters value of bf_min_age_reserve is configured, then
a newly submitted job can start immediately even if there is a higher
priority non-runnable job which has been waiting for less time than
bf_min_age_reserve.

If SchedulerParameters value of bf_min_age_reserve is configured, then
a newly submitted job can start immediately even if there is a higher
priority non-runnable job which has been waiting for less time than
bf_min_age_reserve.