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.

Conflicts:
	META
	NEWS

Conflicts:
	src/slurmctld/reservation.c

RESERVE_FLAGS_LIC_ONLY was changed to RESERVE_FLAGS_ANY_NODES

Start job allocation using lowest numbered sockets for block task
distribution for consistency with cyclic distribution.
bug 1540

Continuation of f34c6bbf

block is set up to it's original state.

Add the ability for a compute node to be allocated to multiple jobs, but
restricted to a single user. Added "--exclusive=user" option to salloc,
sbatch and srun commands. Added "owner" field to node record, visible using
the scontrol and sview commands. Added new partition configuration parameter
"ExclusiveUser=yes|no".  Add "Shared=user" job state information.

Bug 1533

Logic was bad in last commit

Fix bug that can permit someone to kill job array belonging to another user.

If a job is submitted with the option --mem=0, then once the job
is allocated resources, reset that value to the amount of memory
on the allocated node with the smallest amount of memory. This is
probably the best option for right now. The downside is that if
the job is requeued, its memory size will no longer be the total
memory on all nodes if the cluster is heterogeneous. On the upside,
some memory data is available for accounting purposes.
bug 1526

Fix support for --mem=0 (all memory of a node) with select/cons_res plugin.
Previously the job would not have it's memory constrained, but it would not
make that memory unavailable to other jobs either.
bug 1526

Conflicts:
	src/sbatch/opt.c

This was previously added to v14.11

export "all" if -V given to qsub wrapper

Added new SchedulerParameters value of bf_min_age_reserve. The backfill
scheduler will not reserve resources for pending jobs until they have
been pending for at least the specified number of seconds. This can be
valuable if jobs lack time limits or all time limits have the same value.

Increase maximum MaxArraySize configuration parameter value from 1,000,001
to 4,000,001.
bug 1535

Also fix a tests so that multiple nodes are not required.

The data could be purged after job completion

The json m4 script has a bad variable name.

The power consumption threasholds are percentages, so they needed
  to be divided by 100 for proper use.

Intervals below 10 seconds on a Cray system will occasionally
  result in making scheduling decisions based upon old power
  consumption data. May even require larger values for larger
  systems.