we are running with associations.

If a burst buffer is found that was created outside of Slurm then
  add it to Slurm's data, including limits logic.
If a Slurm burst buffer was destroyted outside of Slurm, then
  remove it from Slurm's data, including limits logic.

Previous logic just logged a permission denied on request to delete
  a persistent buffer without properly handling the job (holding
  with good "reason" descriptor).
Improve persistent buffer creation failure better

Add Create/DestroyBuffer configuration parameters (for future use
   by burst_buffer/generic plugin
Add usage/limit information to the information returned for the
  "scontrol show burst" command

Conflicts:
	src/common/slurmdbd_defs.c
	src/slurmctld/job_mgr.c

Handle merge from 14.11. 14.11 added JOB_UPDATE_DB which overlapped JOB_STOPPED
in 15.08. Kept JOB_UPDATE_DB's number and reassigned JOB_STOPPED.

Conflicts:
	contribs/perlapi/libslurm/perl/Slurm.xs
	slurm/slurm.h.in
	src/slurmctld/job_mgr.c
	src/slurmctld/step_mgr.c
	src/srun/libsrun/launch.c
	src/srun/libsrun/opt.c

Remove redundant persist_rem field from job record
Fix logic for buffer state related to failure handling
Move pre_run logic into a separate thread for improved system performance
Disable changes to job burst buffer field
burst_buffer contents are validated at job submit time and
  data is possibly being staged at later times. It can not
   be changed.
Refactor bb_p_job_cancel() logic
Fix some job staging problems
Eliminate logging of unchanged pool information
Document that job arrays don't support burst buffers
Refactor job buffer allocation to eliminate race condition with
  stage out. Needs more work after prolog_running functionality
  is in place (merged from v14.11).
Improve cold-start state clean up

since you can share nodes.  Other TRES (as of writing this) aren't shared.

now nodes are TRES.

under TRES.

This can (hopefully) be used as an example when adding new TRES in the
future.