Options `--max-vms` and `--cluster-size` should be independent

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Run `simul.py` with `--max-vms 10` and `--cluster-size 100`
2. Watch the log show that no more than 10 jobs are running.

What is the expected output? What do you see instead?

The fact that the code treats the (simulated) physical nodes as a
special kind of VMs, is an internal implementation detail: the meaning
of the two options is different and the two numbers have to be
independent, in order to simulate a real cloudbursting cluster:

* `--max-vms` should set the number of *additional* elastic/cloud nodes,
* `--cluster-size` sets the number of (simulated) physical nodes (i.e., 
non-elastic ones).

Original issue reported on code.google.com by riccardo.murri@gmail.com on 17 Feb 2012 at 5:44

[GoogleCodeExporter]

The easiest and "harmless" way of solving this issue is by simply passing the 
(max_vms + cluster_size) when initializing the Orchestrator, otherwise changes 
should be done also in the logic of some methods of the superclass. Is it Ok as 
solution?

Original comment by tyanko.a...@gmail.com on 21 Feb 2012 at 9:55

• Changed state: Started

[GoogleCodeExporter]

| The easiest and "harmless" way of solving this issue is by simply passing
| the (max_vms + cluster_size) when initializing the Orchestrator, otherwise
| changes should be done also in the logic of some methods of the superclass.
| Is it Ok as solution?

I guess so, yes.

Original comment by riccardo.murri@gmail.com on 21 Feb 2012 at 10:04

[GoogleCodeExporter]

Done

Original comment by tyanko.a...@gmail.com on 21 Feb 2012 at 10:14

• Changed state: Fixed