to become effective.

and use them to sync node state info on slurmctld restart.

add logic to save/restore a job's gres info and sync it (more work needed to save/restore node state for proper data sync)

disable this test if dedicated nodes is not supported by virtue of Shared=FORCE configuration on the default partition

ok, sbatch now works here.  scontrol, smap and sview are the only non bluegene-linux cross that don't work

It prevents overallocation of gres resources
including a map of specific allocated resources.

Still need to add save/restore of that information,
propagate detains to slurmd, consider topology, etc.

    MinJobAge configuration parameter. Small values for MinJobAge should improve
    responsiveness for high job throughput.

   Hongjia Cao.

better support for new cross-cluster support.  Works from all types of clusters for most commands.  The actual commands need to change now to make it better.

the test for how many resources are available for pending jobs. changes to the select 
plugins still in progress

    sockets_per_node, min_cores to cores_per_socket, and min_threads to
    threads_per_core (the values are not minimum, but represent the target
    values).

    and GETJOBS commands. Add GRES field to GETNODES command.

mods made to make the select_bluegene.so be put in the plugins rpm instead of the bluegene rpm.  This is needed for cross cluster communications

SLURM commands (squeue, sinfo, etc...) can now go cross-cluster on like linux systems.  Cross-cluster for bluegene to linux and such does not currently work.  You can submit jobs with sbatch.  Salloc and srun are not cross-cluster compatible, and given thier nature to talk to actual compute: nodes these will likely never be.