Previously only supported by SlurmUser and root.

Previously only reserved space for one task of pending job array.

Conflicts:
	NEWS

Support taking node out of FUTURE state with "scontrol reconfig" command.
Previous logic would keep node in FUTURE state if that was the original
configuration when slurmctld started. If job was running on the node,
it will stay running, but the node make not be visible.

Previous logic would create a environment and script file for each
  task of a job array (hard link to original actually). Due to
  file system limitations and clutter, this was less than ideal.
  This patch eliminates the redundant files, using only the original
  file created for the job array. This should also make support for
  burst buffers easier in the future for job arrays.

Make SLURM_ARRAY_TASK_MIN, SLURM_ARRAY_TASK_MAX, and SLURM_ARRAY_TASK_STEP
    environment variables available to PrologSlurmctld and EpilogSlurmctld.

We needed to send a finish from each node in the step whether it had
any activity or not.  This way the controller knew things were done
on the node and the data was sent to the database.

Bug 2097

to get the batch step, no real code change outside of using strcasecmp
instead of strcmp.

Burst_buffer/cray: Don't stall scheduling of other jobs while a stage-in
    is in progress.
bug 2114

Fix to purge terminated jobs with burst buffer errors.
bug 2123

The prolog_running counter can now exceed 1. New logic raises limit
from 1 to 4 before preventing job recovery on restart.

the error happened.

Correct preservation of job ID. This effects emulation mode only.
bug 2113

Added burst_buffer.conf flag parameter of "TeardownFailure" which will
    teardown and remove a burst buffer after failed stage-in or stage-out.
    By default, the buffer will be preserved for analysis and manual teardown.
bug 2116

Conflicts:
	doc/man/man5/slurm.conf.5

If a stage-out fails, Slurm leaves the burst buffer in place and
  logs something like
  "error: bb_set_use_time: job 98 with allocated burst buffers not found"
  every minute thereafer.
  This changes the logic to only log the event one time.
bug 2112

This is a revision to commit e21b666c
which did not fix the problem for all configurations.
bug 2086

Bug 2106

What was happening was the calculation wasn't happening for memory
or nodes, just cpus and gres.

bug 2086

Job needs exit code of zero for COMPLETED state.

bug 2093

Conflicts:
	META
	NEWS