Conflicts:
	src/slurmctld/job_mgr.c

If some tasks of a job array are runnable and the meta-job array
record is not runable (e.g. held), the old logic could start a
runable task then try to start the non-runable meta-job, discover
it can not run, and set its reason to "BadConstraints".

Test case:
Make it so no jobs can start (partition stopped, slurmd down, etc.)
submit a job array
hold the job array
release the first two tasks of the job array
Make it so jobs can start

This backports some logic already added to v15.08

Conflicts:
	src/squeue/print.c

Squeue modified to not merge tasks of a job array if their wait reasons
differ.
bug 1388

Bad copy/paste, needed to change name offset

No functions currently exist, only the plugin wrapper and stubbed functions.

New configuration parameters: PowerParameters, PowerPlugin
New power management web page

--export sbatch/srun command line option, propagate the users'
environ to the execution side. #1367

a Cray being that of a normal Linux system.

Interpret a partition configuration of "Nodes=ALL" in slurm.conf as
including all nodes defined in the cluster.
but 1382

bug 1379

bug 1375

Prior logic would only process data from one plugin.
That's probably fine for now, but most other logic can
support multple simultaneous burst buffer plugins.

Also discovered a data structure that was being allocated based
   upon a different data structure of the wrong size.
Also discovered a list_sort function that was using a bad pointer
   type, resulting in invalid memory references.

based upon email from Taras to slurm mailing list

This implements advanced reservation support for burst buffer space.
It does NOT include support for Cray burst buffer generic resources.

What this does is use the core level binding after each task is laid out
to skip all the extra threads in the core so it doesn't give them to
another task.

It probably isn't perfect, but does solve all the scenarios I found.

Fix for GRES scheduling in which there is CPU topology defined or
GRES types defined and there is more than 1 GPU per topology record
in slurmctld. Without this fix, only one GRES could be allocated
from each defined topology.
bug 1369

The slurmctld could abort with a gres configuration having
Type= configured, but no CPU binding configured.

Revert a changed definition used only in the debugging work from commit
ac9436bc

Add support for multiple burst buffer plugins.
Add support for BB GRES.