Conflicts:
	META
	NEWS

Bug 1446

Add SICP job hash table
Add logic to read SICP data from other clusters
Add state save/restore logic

don't insert a new row in the event table.

Bug 1321

Logic was logging a value before its value was set.
Bug found by CLANG.

The thread logic still needs to be fleshed out

There was a double lock (deadlock) in the power management plugin driver
The power and burst buffer plugins needed to be restarted whenever the primary slurmctld resumed control rather than once at daemon start time. Otherwise the backup and primary slurmctld could both try to manage power and burst buffer resources.

Add module for inter-cluster job development work

Was using "%d" rather than "%u" to print job ID. printing negative
job id value for inter-cluster jobs.

Conditionally restart daemons after RPM package upgrade.

uid's are 0 when associations are loaded.

The backfill scheduler build a queue of eligible job/partition
information and then proceeds to determine when and where those
jobs will start. The backfill scheduler can be configured to
periodically release locks in order to let other operations
take place. If the partition(s) associated with one of those
jobs changes during one of those periods, the job will still
be considered for scheduling in the old partition until the
backfill scheduler starts over with a new job/partition list.
This change to the backfill scheduler validates each job's
partition in from the list based upon current information
(considering any partition changes).
See bug 1436

If bitmap size is initially NO_VAL 0xfffffffe, then a tiny buffer
is allocated and accessing it can go off the end of the buffer.
This has not been observed in production, but only in the investigation
of another problem.

 Fix segfault in controller when deleting a user association of a user which had been previously removed from the system.

 Bug 1238

Fix slurmctld initialization problem which could cause requeue of the last
task in a job array to fail if executed prior to the slurmctld loading
the maximum size of a job array into a variable in the job_mgr.c module.

Fix slurmctld job recovery logic which could cause the last task in a job
array to be lost on restart.

Only supported with task/affinity plugin.

When CgroupMountpoint was not defined in cgroup.conf the mount point
got undefined. This resulted in cgroups not being released.

In order to support inter-cluster job dependencies, the MaxJobID
configuration parameter default value has been reduced from 4,294,901,760
to 2,147,418,112 and it's maximum value is now 2,147,463,647.
ANY JOBS WITH A JOB ID ABOVE 2,147,463,647 WILL BE PURGED WHEN SLURM IS
UPGRADED FROM AN OLDER VERSION!