Refactor the functions used to load state information.
  Reservation and BG block information will be local only.

Add --local option
Add %V/%cluster format option to print cluster name

If there were no clusters in the system then the dbd would insert a row
in the database and then on the next time the dbd would start (with no
clusters) it would attempt to insert the row again and fatal. Now it
always makes a query against the database and if there are no clusters
in the system, then it inserts the current db version into the table.

Without this test the macro _entity_update_kv_helper() will use a
  NULL value for oldvalue and abort
Coverity CID 44965

Treat the same as having the --local option and only get information
  from the identified cluster.
If sprio --cluster option is set, then implicitly set --local

Fix the sprio API so that jobs that are on remote federations only
  and in multiple partitions do not remove all but one partition's
  record. Use a hash function to turn the partition name into a
  number and insure that every unique job ID & partition name are
  reported by sprio.

See Coverity CID 56711

If sysconf() fails, it returns -1, which was not being handled
  properly.
  Coverity CID 59941

The sort list function was flawed and there was a bug in the job
priority API used by sprio

Add sprio --local and --sibling options for use in federation of clusters.

Move the function to get job priorities from src/sprio to src/api
  so that we can handle the threading required for federated clusters
  in a common location in the event this logic is used from other
  places in the future (e.g. sview). No fundamental change in logic.
  The logic and definitions were just moved.

Add sprio -p/--partition option to filter jobs by partition name.
Add partition name to job priority factor response message.

Modify backfill logic so that bf_max_job_user, bf_max_job_part and
    bf_max_job_user_part options can all be used independently of each other.

Add SchedulerParameters option of bf_max_job_user_part to specifiy the
    maximum number of jobs per user for any single partition. This differs from
    bf_max_job_user in that a separate counter is applied to each partition
    rather than having a single counter per user applied to all partitions.

The problem will be solved by using per-partition QOS and setting
MaxJobPer[User|Account] on that QOS.
bug 3668

This was a regression in commit 1967d512.

Bug 3650

This fixes test 7.17 to work with commit a152196f

And mark thread local variables static to limit scope.

Add SchedulerParameters option of bf_max_job_user_part to specifiy the
    maximum number of jobs per user for any single partition. This differs from
    bf_max_job_user in that a separate counter is applied to each partition
    rather than having a single counter per user applied to all partitions.

set min cpus based on tasks if we are overcommitting.  If we do then it
breaks how we overcommit.

# Conflicts:
#	src/plugins/accounting_storage/mysql/as_mysql_convert.c

to remove active sibling from federated job.

so that it can be accessible to new function slurm_kill_job_msg.

to be able to remove specific sibling jobs from a federated job's active
siblings.