Describe how to get dakota application to work with slurm
and add contributor to the slurm team list

Improve how the cray srun/aprun wrapper handles the ntasks and nnodes
options to better distribute tasks over the allocated nodes. The
support for these options is imperfect for resource allocations in
which the number of tasks per node is not uniform, but that can not
be properly handled due to differences between srun and aprun.

Added Logic to make it so you can emulate a cray system and not have to enforce the things you do on a real one.

Transfer all of the node fields to reorder them by node_rank.
Old logic only transferred some fields, which caused problems
on heterogeneous clusters.

Fix some typos and improve technical content of the SLURM design
documents for job launch and gres support.

Added a web page to describe the job launch and termination process
and made a minor enhancement to the GRES design document.

Conflicts:
	src/slurmctld/node_mgr.c
	src/slurmctld/node_scheduler.c

Patch from Andriy Grytsenko (Massive Solutions Limited).

Synchronize power-save module better with scheduler.
Without this change, returning a node to service was typically
delayed longer than necessary.
Patch from Andriy Grytsenko (Massive Solutions Limited).

Report scontrol job job PreemptTime=None rather than PreemptTime=NO_VAL
if not set. Patch from Bill Brophy, Bull

This expands the description of how to build slurm using a git repository.

Modify job expansion logic to support licenses, generic resources, and
currently running job steps in the job which is expanding.

This improves the initial configuration code:
 a) Better handling of DownNodes lines
    The previous basil_geometry() would set the node Reason field on failure,
    irrespective of whether that node has been marked using a DownNode line.

 b) Check all cases of nodes being invisible to ALPS
    Up until now basil_geometry() had to be fixed each time a new source of
    discrepancy between ALPS and SDB state had been discovered (most recent
    case was NULL coordinates when taking out a blade). Depending on ALPS
    interface changes, there may be other possibilities. Instead of fixing the
    SLURM code for each new case, it is better to check whether SLURM and ALPS
    agree. The price is some tiny delay at SLURM initialisation time (since each
    node is first looked up in the ALPS inventory), but it pays well off as it
    eases system administration by pointing to the source of error.
    Any node that has suddenly disappeared from ALPS horizon will now show up in
    the logs, and also in marked down in sinfo.

 c) At initialisation time, give a summary as to how many ALPS nodes are online.

 d) Turn ALPS-node-invisibility error into warning message, since such nodes may
    already have been covered in a DownNodes statement.

By merging basil_get_initial_state() into basil_geometry(), the previously separate
knowledge about system state (database state, ALPS inventory) is combined, allowing
to more easily identify sources of failure.
Patch from Gerrit Renker, CSCS.

Logging message was misleading and incorrect pointer used in another.

Former logic failed to properly allocate resources to a job step
when specifying both a task count and a node count range on a
heterogeneous cluster.

BLUEGENE - Fixed print of geo portion of the select_jobinfo struct to work correctly with the regession tests.

Latest Cray-specific modifiations

The enum is only needed and referenced in basil_geometry() and has otherwise
no special meaning since it directly depends on the selected output columns.
Patch from Gerrit Renker, CSCS.

This case was observed after taking a blade out of a CLE 2.x system. ALPS does not
list the removed nodes, but they still appear in the XTAdmin.processor table, with
NULL coordinates. Hence set node down if at least one coordinate is NULL.

Also add a check to compare how many out of the nodes in slurm.conf are visible to
ALPS (the absence of this test masked the bug), always list DOWN nodes at startup,
and clarify that not failing due to ALPS errors during the initial SLURM
configuration is not an option.

On the system which is missing a blade, the log information now is
 [2011-05-16T16:09:54] error: ALPS sees only 12/16 slurm.conf nodes
 [2011-05-16T16:09:54] Recovered state of 16 nodes
 [2011-05-16T16:09:54] Recovered state of 2 front_end nodes
 [2011-05-16T16:09:54] Recovered information about 0 jobs
 [2011-05-16T16:09:54] error: nid00028: unknown coordinates - hardware failure?
 [2011-05-16T16:09:54] error: nid00029: unknown coordinates - hardware failure?
 [2011-05-16T16:09:54] error: nid00030: unknown coordinates - hardware failure?
 [2011-05-16T16:09:54] error: nid00031: unknown coordinates - hardware failure?
Patch from Gerrit Renker, CSCS.

This fixes some errors in the documentation of how memory is allocated, and adds missing bits.
Patch from Gerrit Renker, CSCS.