Continuation of 418e1c69

specify --with-pmix.

Bug 3597

This makes it so you can also specify %slurm_with_pmix in .rpmmacros to specify
a non-standard pmix installation.

ex. squeue -M<cluster> was talking to the local cluster instead of
<clsuter>.
Continuation of 418e1c69

Continuation of add1f9d3. Had calls to fed_mgr_is_active() in another
branch.

About "MCSParameters=ondemand,noselect:groupA|groupB|groupC",
you can separate ondemand,noselect and groupA|groupB|groupC into 2
parameters like you want. The first part is common for mcs plugin and
the second part is only for mcs/group, so it could be logical to put them
into 2 different parameters.

Bug 3428

END_TIMER was being called without a START_TIMER.
Coverity CID:165991

the slurmctld.

This reverts commit a662a226.

the slurmctld.

ACTIVE: accepts submissions and schedules
INACTIVE: doesn't accept submissions or schedules
DRAIN: schedules but doesn't accept submissions
DRAIN+REMOVE: like DRAIN but cluster removes itself from federation once
all federation jobs are gone.

Continuation of f9d132fc which just stopped the back_scheduler from
starting up. This patch allows the backfill scheduler to be stopped
after starting.

Clearing should make the job eligible on all clusters again.

cluster for it to handle the request.

for ClusterFeatures.

e.g.
scontrol update <jobid> clusters=fed1,fed2

Currently assumes that if the origin job updates successfully then it
can submit the job to the siblings. Will need to expand on this to
handle heterogenous setups.

with the correct node select plugin_id. The dbd stores the plugins
actual plugin id but the plugin_id doesn't index you into the
plugin_context array. So it needs to be translated to the index so that
the correct node_select plugin accessed properly.