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.

fix for small window where a job is being killed because an account is being removed, but the job hasn't been started in accounting.

    The default MaxJobCount was changed from 5,000 to 10,000.

framework for handling cross-cluster communication.  Nothing works yet, more most cases all that needs to be added is talking to the database to get where the other clusters are.

    initiation will be delayed until all allocated nodes have booted. Salloc
    will log the delay with the messages "Waiting for nodes to boot" and "Nodes
    are ready for use". 

Accounting - When removing associations if jobs are running, those jobs must be killed before proceeding.  Before the jobs were killed automatically thus causing user confusion on what is most likely an admin's mistake.

Patch for adding CR_CORE_DEFAULT_DIST_BLOCK as a select option to layout jobs using block layout across cores within each node instead of cyclic which was previously the default.

    (currrently in the contribs directory, but plan to distribute through
    http://code.google.com/p/slurm-spank-plugins/).

The Priority/mulitfactor plugin now takes into consideration size of job in cpus as well as size in nodes when looking at the job size factor.  Previously only nodes were considered.

    Useful for batch jobs (in Prolog or the script) if powering down idle nodes.

    wait for all allocated nodes to power up before proceeding. Salloc will
    log the delay with the messages "Waiting for nodes to boot" and "Nodes are
    ready for use". Srun will generate the same messages only if the --verbose
    option is used.