Modify regression tests to work with select/serial
Merge branch 'slurm-2.4'

Conflicts:
	testsuite/expect/test21.21
Pass job submit host to moab

The purpose of this is so moab scripts and commands (such as 'checkjob')
have consistent access to the SUBMITHOST variable.
Merge branch 'slurm-2.4'
BGQ - Fix issue when running with AllowSubBlockAllocations=Yes without
compiling with --enable-debug
BGQ - caught 2 more related to last BGQ patch.

Signed-off-by: Danny Auble <da@schedmd.com>
Merge remote-tracking branch 'origin/slurm-2.4'
Remove vestigial slurm_signal_job_step() symbol from srun

The srun command formerly needed to call slurm_signal_job_step()
to load the symbol and have it accessible from the mpi plugins.
This is no longer the case due to changes in linking since 2007.
remove unneeded debug
Mods to get poe to launch more correctly.  Jobs still don't launch yet
but things are closer.
Merge branch 'master' of github.com:SchedMD/slurm
Modify tests for select/serial plugin
Add SHMEM test
Remove pointless check. The state_reason is set to WAIT_NO_REASON
so acct_policy_job_runnable will always return true.
Correction to switch/nrt logic
Modify scontrol show job to require -dd option to print batch script.

I have implemented the changes as you suggested:   using a "-dd" option to indicate that the display of the script is wanted, and setting both the "SHOW_DETAIL" and a new "SHOW_DETAIL2" flag.

Since "scontrol" can be run interactively as well,  I added a new "script" option to indicate that display of both the script and the details is wanted if the job is a batch job.

Here are the man page updates for "man scontrol".   For the "-d, --details" option:

       -d, --details
              Causes  the  show command to provide additional details where available.  Repeating the option more than
              once (e.g., "-dd") will cause the show job command to also list the batch script, if the job was a batch
              job.

For the interactive "details" option:

       details
              Causes  the  show  command  to provide additional details where available.  Job information will include
              CPUs and NUMA memory allocated on each node.  Note that on computers  with  hyperthreading  enabled  and
              SLURM  configured  to allocate cores, each listed CPU represents one physical core.  Each hyperthread on
              that core can be allocated a separate task, so a job's CPU count and task count  may  differ.   See  the
              --cpu_bind  and  --mem_bind  option  descriptions  in  srun man pages for more information.  The details
              option is currently only supported for the show job command. To also list the  batch  script  for  batch
              jobs, in addition to the details, use the script option described below instead of this option.

And for the new interactive "script" option:

       script Causes the show job command to list the batch script for batch jobs in addition to the  detail  informa-
              tion described under the details option above.

Attached are the patch file for the changes and a text file with the results of the tests I did to check out the changes.   The patches are against SLURM 2.4.0-rc1.

        -Don Albert-
Change SchedulerParamters option from "bf_res=" to "bf_resolution="

This change makes the code consistent with the documentation.
Note that "bf_res=" will continue to be recognized for now.
Patch from Rod Schultz, Bull.
Correct default NodeAddr

According to man slurm.conf, the default for NodeAddr is NodeName:

  "By  default, the NodeAddr will be identical in value to NodeName."

However, it seems the default is NodeHostname (when that differs from
NodeName): With the following in slurmnodes.conf:

Nodename=c0-0 NodeHostname=compute-0-0 ...

I get

NodeName=c0-0 Arch=x86_64 CoresPerSocket=2
   CPUAlloc=0 CPUErr=0 CPUTot=4 Features=intel,rack0,hugemem
   Gres=(null)
***
   NodeAddr=compute-0-0 NodeHostName=compute-0-0
***
   OS=Linux RealMemory=3949 Sockets=2
   State=IDLE ThreadsPerCore=1 TmpDisk=10000 Weight=1027
   BootTime=2012-05-08T15:07:08 SlurmdStartTime=2012-05-25T10:30:10

(This is with 2.4.0-0.pre4.)

(We are planning to use cx-y instead of compute-x-y (the rocks default)
on our next cluster, to save some typing.)

--
Regards,
Bjørn-Helge Mevik, dr. scient,
Research Computing Services, University of Oslo
Change switch/nrt node_id to be IPv4 address rather than sequence number

The node_number field is normally set to the 32-bit IPv4 address of the
local node's host name.  Bill LePera, IBM, 4/18/2012
Add node_number to switch/nrt IBM task un/pack logic