Just a start for now

Conflicts:
	NEWS

Conflicts:
	META
	src/plugins/priority/multifactor/priority_multifactor.c

Avoid decrementing grp_used_cpu_run_secs if we are not enforcing
accounting limits. Without this change, the plugin will decrement
times from zero cpu used times (i.e decrement an uninitialized
variable).

Added -S/--core-spec option to salloc, sbatch and srun commands to reserve
    specialized cores for system use. Modify sview and scontrol to set/get
    core_spec
struct job_info / slurm_job_info_t: Added core_spec
struct job_descriptorjob_desc_msg_t: Added core_spec

Make HTML generator scripts Python 3 compatible

The system really can not handle larger job arrays without adding
a job array data structure, but this puts some of the infrastructure
in place now.

Disable test if FairShareDampeningFactor != 1

to offer a greater priority range based upon utilization.

Add argument to priority plugin's priority_p_reconfig function to note
when the association and QOS used_cpu_run_secs field has been reset.
Without this flag, we remove time on "scontrol setdebug" or
"scontrol setdebugflag" that can result in used_cpu_run_secs
going negative or otherwise get bad values.
Correction to logic added in commit 6d793189
bug 423

Add argument to priority plugin's priority_p_reconfig function to note
when the association and QOS used_cpu_run_secs field has been reset.
Without this flag, we remove time on "scontrol setdebug" or
"scontrol setdebugflag" that can result in used_cpu_run_secs
going negative or otherwise get bad values.
Correction to logic added in commit 6d793189
bug 423

Conflicts:
	NEWS
	contribs/torque/qsub.pl

Fix to work with change logic introduced in Slurm version 2.6.3
scheduling logic which prevented Maui/Moab from starting jobs.