A different approach to handling the alias is needed for these systems,
this does not begin to cover all of the required function implementations.

With the change/refactoring in logics after the new XCC energy plugin we
are using the base_watts field as ave_watts. Change all variable names
for consistency.

Bug 6282

This adds the -b option to salloc, srun and sbatch
which is equal to --begin.

Bug 6356.

# Conflicts:
#	src/sbatch/opt.c

Bug 6356.

Fixed srun from double printing invalid option
msg twice. Also removed the unused -b flag from sbatch.

Bug 6356.

Corrected extra spacing between function and function arguments
in srun and sbatch.

Bug 6364.

It has been shown in a couple of ways these 2 apis are dependent
on each other, but both export similar symbols, so when you link
to both of them you get duplicate symbols.

Bug 1394

Note that FastSchedule=0 lets the GRES count used for scheduling
be based upon what the node reports (like memory or disk space).

This is needed so we can easily determine if we are running
in the slurmctld (rather than running in slurmd or in a test
program). When running with test7.3 and a configuration of
TopologyPlugin=topology/tree the test would generate a bunch of
"Invalid GRES configured on node ..."
errors and fail. This change means the GRES checking logic is
disabled for the test.

Just make some formatting changes

No change in logic

Bug 5670.

Bug 5670.

Bug 5670.

Update the documentation, and split "classic" fair share details
off to a separate page.

Bug 6036.

scontrol and sview won't report Consumed Joules and Lowest Joules anymore.
The reason is that these values were collected from slurmd start time which
made them not useful for the users.

Bug 6283

SchedMD has moved to Utah, so change the jurisdiction.

The test21.30/inc21.30.11 does not work if SelectTypeParameters
does not manage memory (not a commonly used configuration), but
this adds a check to prevent a failure that is due to the
configuration rather than slurm code bug.

These tests confirms correct CUDA percentages in an environment
where the gres/mps counts are not always 100 and can very from
device to device within a node.

Slurmd was generating errors of this sort for all GRES:
error: Ignoring gres.conf record, invalid name: mps
This was due to some GRES setup logic not being invoked
on the slurmd. In any case, the relevant checking now only
happens on the slurmctld.

This patch fixes the regression caused by 07483564 where only the
linux plugin was handling this scenario correctly.

Bug 6332

If a gres type was identified in the node's GRES field, but that
type was not listed in the slurm.conf GresTypes parameter then
those GRES would appear in the output of "scontrol show node".
This misleading/wrong information would cause a bunch of tests
to fail. This patch only moves valid node GRES into the node
record and deletes the rest.

This logic supports different MPS counts on each device, which
is possible on a heterogeneous system

This prints GRES configuration information and exits. For testing.

Needed for testing of gres/mps allocations

Fix formatting and typo in log message

Wrong variable name used

This works for heterogeneous systems, various Counts for each GPU
type, steps which use a subset of the job's gres/mps allocation,
etc.

Bug 4700.

Co-authored-by: Tim Wickberg <tim@schedmd.com>