VMonG5K: physical machine allocation is not deterministic
Virtual machines don't always end up on the same physical machine. This is especially bad when re-running the same Enoslib script, because the same VM will be started a second time on a different physical machine!
Here is an example allocation I got:
virtual-132-0-2 10.132.0.2 dahu-2.grenoble.grid5000.fr
virtual-132-0-3 10.132.0.3 dahu-7.grenoble.grid5000.fr
virtual-132-0-4 10.132.0.4 dahu-6.grenoble.grid5000.fr
virtual-132-0-5 10.132.0.5 dahu-30.grenoble.grid5000.fr
virtual-132-0-6 10.132.0.6 dahu-2.grenoble.grid5000.fr
virtual-132-0-7 10.132.0.7 dahu-7.grenoble.grid5000.fr
virtual-132-0-8 10.132.0.8 dahu-6.grenoble.grid5000.fr
virtual-132-0-9 10.132.0.9 dahu-30.grenoble.grid5000.fr
Running the same experiment while reloading the G5K jobs, I got a different allocation:
virtual-132-0-2 10.132.0.2 dahu-2.grenoble.grid5000.fr
virtual-132-0-3 10.132.0.3 dahu-7.grenoble.grid5000.fr
virtual-132-0-4 10.132.0.4 dahu-30.grenoble.grid5000.fr
virtual-132-0-5 10.132.0.5 dahu-6.grenoble.grid5000.fr
virtual-132-0-6 10.132.0.6 dahu-2.grenoble.grid5000.fr
virtual-132-0-7 10.132.0.7 dahu-7.grenoble.grid5000.fr
virtual-132-0-8 10.132.0.8 dahu-30.grenoble.grid5000.fr
virtual-132-0-9 10.132.0.9 dahu-6.grenoble.grid5000.fr