scontrol: warn user that base node state can not be changed on Cray

The base node state (UP, DOWN, ALLOCATED, ...) is handled by ALPS and inferred
from reading the output of ALPS inventory requests.

To avoid inconsistencies, it is not possible for a user to alter this node state.
This patch adds a warning to scontrol if a user wants to change node state through
slurm:

palu> scontrol update NodeName=nid00171 State=DOWN
State=DOWN can not be changed through slurm: use native Cray tools such as e.g. xtprocadmin(8)

The 'meta' states such as DRAIN can still be changed.

This reverses some patches from Gerrit that were old, going to work
forward now from the start

    XT/XE systems, and build on native Cray XT/XE systems (auto-detected).
    Building on native Cray systems requires the cray-MySQL-devel-enterprise
    rpm and expat XML parser library/headers.

select/cray: update compile-time and runtime support for Cray build

These changes update build support for Cray XT/XE:
 1. renamed '--cray-xt' into '--cray' since also XE systems are supported;
 2. autoconf rules to cover the various possible build cases:
    a) --enable-cray=off: HAVE_CRAY/HAVE_NATIVE_CRAY undefined,
    b) --enable-cray=on:  HAVE_CRAY defined
       b1) local host is a native Cray system: HAVE_NATIVE_CRAY defined
           (requires installation of mysql-devel and libexpat-devel packages),
       b2) local host is not a native Cray system: the conditionally built
           parts (basil_interface.c, libalps.la) are not built;
 3. updated configure logic:
    - since Cray support depends on mySQL, reordered tests in configure.ac,
    - reordered logic with regard to changes in (2),
    - an AM_CONDITIONAL to build native-Cray parts conditionally,
    - updated configure messages (XT/XE);
 4. run-time read_conf test to ensure use of select/cray is properly supported,
 5. an update of the NEWS file due to the change in (1) ==> may have a conflict
    in case you have a locally-updated copy.

I have compile-tested the three possible scenarios in (2).

    03_Cray-BASIL-node-ranking.diff
select/cray: perform node ranking

This supplies the select function-pointer to request a reordering of nodes based
on the current Cray node ordering. 

The Cray node ordering is set internally via the ALPS_NIDORDER configuration 
variables that controls the way ALPS considers nodes.

This ordering in turn determines the order of nodes as the appear subsequently 
in the Inventory output. The present patch exploits this fact and uses an
auto-incrementing number to reflect the node ranking (counting is reversed 
since the parser returns the nodes in stack/LIFO order).

The node ranking is performed on slurmctld (re-)configuration, hence the tests
are more stringent: exit if Inventory fails (this condition is extremely rare)
and if no nodes are powered up (also a condition that can be cured by restarting
slurmctld only when the system is ready).

    03_node-reordering-NodeHostName.diff

    02_Cray-BASIL-node-attributes-and-coordinates.diff

    02_salloc-no-node-update.diff

    01_Cray-BASIL-basic-support.diff plus
    01_changes-from-first-revision-of-patch-01.diff

    eliminates some inappropriate error messages. 01_interactive-no-script.diff

    expected start time was too far in the future for the backfill scheduler
    to compute.

    values as "*" rather than 65534. Patch from Rod Schulz, BULL.

    the job's priority using scontrol's "update jobid=..." rather than its 
    "hold" or "holdu" commands.

Fixed issue when using a storage_accounting plugin directly without the slurmDBD updates weren't always sent correctly to the slurmctld, appears to OS dependent, reported by Fredrik Tegenfeldt.

    clusters over 1000 nodes. Users can enable this by selecting the "Name"
    tab. This change dramatically improves scalability of sview.

    it were removed from the job's allocation. Now only the tasks on those
    nodes are terminated.

Fix for checking QOS to override partition limits, previously if not using QOS some limits would be overlooked.

    running or suspended states). Patch from Martin Perry, BULL.

    SelectTypeParameters=CR_ONE_TASK_PER_CORE.

Infrastructure in place plus logic in select/linear.

    indicate job termination was due to preemption.

    "*** JOB 65547 CANCELLED AT 2011-01-21T12:59:33 DUE TO PREEMPTION ***".

Added flag "NoReserve" to a QOS to make it so all jobs are created equal within a QOS.  So if larger, higher priority jobs are unable to run they don't prevent smaller jobs from running even if running the smaller jobs delay the start of the larger, higher priority jobs.

BLUEGENE - fixed issue where jobs wouldn't wait log enough for blocks to free and wanted to use blocks that are being freed for other jobs

-- BLUEGENE - This fixes a race condition with dynamic mode to make it so we copy the booted and job list of blocks before trying to create.

    so the highest job priority becomes TOP_PRIORITY.

    at FirstJobId.

BLUEGENE - fixed race condition with preemption where if the wind blows the right way the slurmctld could lock up when preempting jobs to run others.

Fixed issue where QOS priority wasn't re-normalized until a slurmctld restart when a QOS priority was changed.

Made it so QOS with UsageFactor set to 0 would make it so jobs running under that QOS wouldn't add time to fairshare or association/qos limits.