-
Notifications
You must be signed in to change notification settings - Fork 2
Description
If I understood this correctly, it configures(great!) and launch(even better) the experiment. This can be very useful, but i also need to copy/install custom policies on that node, and these are intermediate steps between the experiment configuration and the ipcm launching.
As for now i have to launch the experiment(so it creates everything i need) and then reboot the nodes or kill every ipcm in all systems(so it's cleaner to reboot them). Then copy and make + make_install(at least one time, then no more problem) of the policies and one last configurator run to relaunch the ipcm again.
This is of course a problem if:
- configure the experiment the first time.
- adjust the policy somehow and have to update the instances on the experiment nodes(this can happen often!!!).
A nice improvement can be to allow the experiment setup without the ipcm start, and leave this only if needed(like having a --launch-ipcm option).