If scontrol is used to change a node's GRES and the input string
contains socket binding information (e.g. "gres=gpu:4(S:0),...")
then ignore the socket binding information input. Use the binding
as reported by slurmd in the node registration.

If a node's GRES has a count of zero (say after updating GRES counts)
then do not print the count. Just don't report anything for that
GRES type.

If a GRES was defined with Type information in gres.conf, but
lacked Type information in slurm.conf, this sets up the data
structures in slurmctld for resource allocations.

Convert node validate logic (on node registration) in gres.c
to use the same (new) function as is used for node gres update
operation.

Add new logic to set node's GRES string on reconfig.
Set node GRES sockets based upon real socket/core config info.
Validate GRES changes before making them.
    Specifically we want to make sure no requests to process changes
    in the count of a GRES associated with File specifications happens.
    For example, if we have 4 gres/gpu associated with /dev/nvidia[0-3]
    and "scontrol update NodeName=... Gres=gpu:2" is executed that
    request will return an error. This is because we have no idea which
    specific gres/gpu records should be removed. We can issue a request
    to keep the count unchanged or set the count to 0, but any other
    count will return an error. This restrictions is not placed on
    GRES without Files (e.g. gres/craynetwork).
Changed some variable names to better reflect their contents.

Give job longer time to be scheduled and started (depends on
scheduling parameters).

Declare as extern; the linker will find this in libc somewhere.

Bug 5561.

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

Bug 6242

This check really is there to test if we have dynamic(inactive) features.

Obviously this doesn't work on heterogeneous systems, but there is no
good way to check for this as this check is used long before nodes are
considered.

Bug 6242

Docs updated with details. 'node' is simply removed from the tres list;
the report will continue if other valid tres are specified.

Bug 5954

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