if an job step's network value is set by poe, either by directly
executing poe or srun launching poe, that value was not being
propagated to the job step creation RPC and the network was not
being set up for the proper protocol (e.g. mpi, lapi, pami, etc.).
The previous logic would only work if the srun execute line
explicitly set the protocol using the --network option.

Prevent preemption of jobs in partition where PreemptMode=off

Define hwloc_const_bitmap_t as typdef hwloc_const_cpuset_t
Build fails in task_cgroup_cpuset.c when using an older hwloc (v1.0.2)
due to missing definition of hwloc_const_bitmap_t.

This reverts commit 084787c0.

Conflicts:

	NEWS
	contribs/pmi2/pmi2_api.c
	src/plugins/mpi/pmi2/mpi_pmi2.c

Add support for job std_in, std_out and std_err fields in Perl API.

processes.

Modify hostlist expressions to accept more than two numeric ranges
(e.g. "row[1-3]rack[0-8]slot[0-63]")

Previous logic would typically do list search to find job array elements.
This commit adds two hash tables for job arrays. The first is based upon
the "base" job ID which is common to all tasks. The second hash table
is based upon the sum of the "base" job ID plus the task ID in the array.
This will substantially improve performance for handling dependencies
with job arrays.

When slurmctld restarted, it would not recover dependencies on
job array elements and would just discard the depenency. This
corrects the parsing problem to recover the dependency. The old code
would print a mesage like this and discard it:
slurmctld: error: Invalid dependencies discarded for job 51: afterany:47_*

When adding or removing columns to most data types (jobs, partitions,
nodes, etc.) on some system types an abort is generated. This appears
to be because when columns displayed change, on some systems that
changes the address of "model", while on others the address does not
change (like my laptops). This fix explicitly sets the last_model to
NULL when the columns are changed rather than relying upon the data
structure's address to change.

be setup for 1 node jobs.  Here are some of the reasons from IBM...

1. PE expects it.
2. For failover, if there was some challenge or difficulty with the
   shared-memory method of data transfer, the protocol stack might
   want to go through the adapter instead.
3. For flexibility, the protocol stack might want to be able to transfer
   data using some variable combination of shared memory and adapter-based
   communication, and
4. Possibly most important, for overall performance, it might be that
   bandwidth or efficiency (BW per CPU cycles) might be better using the
   adapter resources.  (An obvious case is for large messages, it might
   require a lot fewer CPU cycles to program the DMA engines on the
   adapter to move data between tasks, rather than depend on the CPU
   to move the data with loads and stores, or page re-mapping -- and
   a DMA engine might actually move the data more quickly, if it's well
   integrated with the memory system, as it is in the P775 case.)

If srun invoked with the --multi-prog option, but no task count, then use
the task count provided in the MPMD configuration file.

performance.

than you really have.

doesn't get chopped off.

    a minus sign for options was intended.

Some of these were resulting in the state of a job not being updated
correctly to tools like sview.

in waiting reason ReqNodeNotAvail.

protocol version to be SLURM_2_5_PROTOCOL_VERSION which is the minimum
supported version.

Previously if the sbatch --export=NONE option was used then several
Slurm environment variables were not propagated from the sbatch
command (SLURM_SUBMIT_DIR, SLURM_SUBMIT_HOST, SLURM_JOB_NAME, etc.)

Scheduler enhancements for reservations: When a job needs to run in
reservation, but can not due to busy resources, then do not block all jobs
in that partition from being scheduled, but only the jobs in that
reservation.

Reset a node's CpuLoad value at least once each SlurmdTimeout seconds.
Previously the value would not be reset unless communications with the
slurmd did not happen for at least 1/3 of the SlurmdTimeout value.
That means nodes that were actively running and terminating jobs would
not get the CpuLoad value reset in a timely fashion. Added a CpuLoad
reset timer to prevent this.

Add logic to sleep and retry if slurm.conf can't be read.
Without this, the slurmd daemons may die and when the SlurmdTimeout
is reached, the nodes will be marked DOWN and their jobs will be
killed.
In the long term, it would be good to exit only if the read files
on program startup, and the daemons keep running with old configuration
on reconfiguration, but I don't have time to do that work now.