Step GRES value changed from type "int" to "int64_t" to support larger
values.

Signed-off-by: Danny Auble <da@schedmd.com>

These changes apply to both the main scheduling logic and backfill
scheduler. If some SchedulerParameters value was configured, the
slurmctld started, then completely removed, and slurmctld reconfigured
the value would not be reset to it's default value but the originally
configured value would persist until slurmctld restarted.

Continuation of 31225a82

Harden code to not fail if node_bitmap passed to _update_node_gres()
has no bits set.

Bug 2430

This may be helpful for timing purposes. Added by Cray request.

Unless a job is running in --multi-prog mode, modify the logic to
resolve the job's path once rather than once for each task. This
may slightly improve performance (requested by Cray).

of it's very close version.

We want to introduce a new behavior in the way slurmd uses the
HealthCheckProgram. The idea is to avoid a race condition between the
first HealthCheckProgram run and the node accepting jobs. The slurmd
daemon will initialize and then loop on HealthCheckProgram execution
before registering with slurmctld. It will stay in this loop until
the HealthCheckProgram returns successfully (the node is still DOWN).

On our clusters we are using NHC as an HealthCheckProgram. NHC drains
the node if it fails and remove the drain if it is successfull, this
behavior fits well with our purpose. This behavior permits us to start
slurmd at boot without setting up a complex boot sequence in the init
system, slurmd just wait for the node to be ready before registering.

The HealthCheckProgram is not run during slurmd startup if
HealthCheckInteval is 0.

Bug 2507

Step GRES value changed from type "int" to "int64_t" to support larger
values. Previous logic could fail in step allocation values over 32-bits.
Other GRES values are 64-bit.

slurmstepd to close potential open ones.

It was pointed out the slurmd using acct_gather_energy/ipmi links to
freeipmi which could possibly open /dev/ipmi0 without the close on exec
flag set as root while launching a step leaving it open in the users app.

What this does is sets the flag on the first 256 to mitigate the concern.

Reported by Maksym Planeta.

Bug 2506

This enables the node_feature plugin to add GRES to nodes. Specifically
it is intended for the node_feature/knl_cray plugin to build a GRES
containing the MCDRAM size currently configured on the node. More
work is needed for full functionality.

Make sure that capmc_suspend and capmc_resume are properly packaged
  in an RPM if a non-standard sbin location is configured

bsub batch script or not.  If it isn't we will wrap the script to avoid
issues where $0 is used inside the script.

Conflicts:
	src/plugins/sched/backfill/backfill.c

Previous logic tested whatever the job's partition pointer indicated
rather than the partition we are trying to run the job in. This bug
was introduced in Slurm version 15.08.5, Nov 16, 2015, commit
94f0e948
bug 2499

patch 2d5066e7

Add a new function that can read power save configuration information
  before starting the power save thread. This lets us confirm
  that power save mode is configured to run earlier in the slurmctld
  start up logic and report an error at at earlier point if power
  save is not configured to run, but node_feature/knl_cray (which
  needs it) is configured.

Introduced in c97e08a0
Change default CgroupMountpoint (in cgroup.conf) from "/cgroup" to
    "/sys/fs/cgroup" to match current standard.
For details, see https://wiki.freedesktop.org/www/Software/systemd/PaxControlGroups/

Check that PowerSave mode configured for node_features/knl_cray plugin.
    It is required to reconfigure and reboot nodes. Fatal error if
    not configured.

understandable.