Changing jobmin to 1 for batch q on blues

[jayeshkrishna]

Setting jobmin to 1 for blues+batch queue so that longer jobs
that don't fit in the shared/debug queue fit the batch queue.

Fixes #1484
[BFB]

[jgfouca]

Might be better to make the shared queue the default. That way, the system will try to put the job in the faster queue first, and only use the slower one if it has to.

[jayeshkrishna]

The NERSC machines and titan take the alternative approach right now - use the larger queue as default

[jayeshkrishna]

The default queue should probably work (OOB) for all cases created by the user

[jgfouca]

@jayeshkrishna but we now have robust code to ensure that the larger queue will be used if needed. I'm worried about slow throughput if everything goes into the larger queue by default.

[jayeshkrishna]

The "regular" queue to submit the jobs on blues is the batch queue. If someone needs to debug their runs they need to submit to the "shared"/debug queue.
Let me see if the batch system pushes a small job by default to the "shared" queue (if so, making it the default should be ok).

[jayeshkrishna]

I just tried a simple job with 2 nodes on blues and it was by default submitted to the batch queue. I think we should leave the batch queue as the default and the user can explicitly choose the debug/shared queue if needed (./create_newcase ... --queue=shared).

[rljacob]

On blues, the logic is "submit directly to the shared queue if the job is small enough and I want it to start immediately and I don't care if its a little slow" else don't specify a queue at all and you'll get in the batch queue. It to hard to separate the tests between shared and batch so submit everything to batch.