Allow ParallelEnvironment to be set with node number = 1
Original issue created by Youri Bonnaffe on 31, Jan 2014 at 11:21 AM - SCHEDULING-1973
When using ParallelEnvironment, if the node number is 1, the job cannot be submitted.
It would be nice to accept it as a valid value as sometimes you want to reuse a job.xml with parallel environment but only use 1 node.
My use case is as follow, I have a generic cmd.xml job that runs some user defined command where the user inputs the command and the number of nodes to use. For now I have to manage two different versions of cmd.xml job to handle the case where the number of nodes is 1.
PR: #2523
Solved by: #2523.
I reopened this issue as following #2523, the ParallelEnvironment with nb-nodes=1 does not behave as expected for SingleHostExclusive, MultipleHostExclusive and DifferentHostExclusive topologies. For example, where the whole machine should be selected with nb_nodes=1/SingleHostExclusive, only one node is selected. On the contrary, the setting nb_nodes=2/SingleHostExclusive behaves as expected