Wrong author.

This reverts commit e1c10fea.

Bug 5836.

Bug 5836.

Bug 6162

much work still required

Required for gres/mps

Also internally sort GresTypes so that the gres/gpu plugin is processed
before gres/mps. gres/mps will leverage the gres/gpu plugin.

Bug 6163

Backups already run it when dropping to backup.

Bug 6098.

Backups already run it when dropping to backup.

Bug 6098.

Missed from 0d9b7d5d.

Remove the README and point to the web page.

Add details on the disable_x11 option.

Bug 5936.

Also throw an error message within stepd_available() if the nodename
is not set or cannot be inferred correctly.

Bug 5399.

Remove the configuration entry, and update docs to remove it.

There is no option to disable this, as I believe the amended behavior
is expected and safer for all systems.

Bug 5297.

Spelling, suggestions, trailing whitespace.

Bug 6044

No change in logic

Bug 6120

xstrcasestr() knows how to handle NULL on any argument, so these
are all redundant checks. Cleanup related handling code while here,
and convert a few missed strstr/strcasestr locations as well.

In job_submit_throttle plugin, use sched_params as the name for
consistency with the rest of the code base.

Update the newly added bf_ignore_newly_avail_nodes option to use
xstrcasestr() like the rest of these options.

Bug 5976.

Bug 6155

Bug 6155

When bf_continue is set, and locks are released during a backfill cycle,
other operations can make new resorces available while part way through
the queue. When backfill continues the cycle and evaluates new jobs, it
may allocate some of these newly available resources to lower priority jobs,
rather than to higher priority jobs that were already considered in this
backfill cycle.

This patch introduces bf_ignore_newly_avail_nodes to SchedulerParameters
to solve this issue. This option will ignore nodes made available when
the backfill scheduler yields when resuming the backfill cycle.

Bug 5279.

No new code, just a stubbed module

Bug 6018
Also see bug 5402

Previously the gres/gpu plugin was removing non-gpu records from
the gres list. Here is a specific example:
Sample gres.conf file
Name=mps Type=fake Count=1 File=/dev/tty0
Name=mps Type=fake Count=1 File=/dev/tty1
Name=gpu Type=fake Count=1 File=/dev/tty0
Name=gpu Type=fake Count=1 File=/dev/tty1

The gres/mps counts were being reported to slurmctld as having a zero
count.

slurmd yet delivering it's TRES list.

Bug 6122

Co-authored-by: Marshall Garey <marshall@schedmd.com>