Further cleanup (not finished yet).
Further cleanup.
Startup on different JVMs (not yet finished).
Startup on different JVMs (not yet finished).
Added missing files.
Splitted configuration files. Started with clean startup of cluster.
Config fiddling.
Config fiddling.
Config fiddling.
Controller introduction and setup.
Added missing files.
Cleanup of generics.
Controller setup for master, worker and frontend done.
Controllers separated.
Settings properly wired.
New ping master actor.
New ping master actor.
Remote Execution Context is now retrieving via Node Controller.
Config fiddling.
Config fiddling.
IT IS WORKING !!!!!!!!!!!!!!!!
run "multi-jvm:run org.remotefutures.core.MasterWorker" in sbt.
IT IS WORKING !!!!!!!!!!!!!!!!
run "multi-jvm:run org.remotefutures.core.MasterWorker" in sbt.

Test DistributedWorkerSpec commented out ..... will fix that soon.
Merge pull request #60 from MartinSenne/master

Incredible!!!!!

That was a rough journey, but well done.  

Your suggestions of using Docker / Chef / SSH instead is perfectly fine. 
I would suggest as next step to play around with this combo on AWS just to run some remote-future 
examples on tiny cluster.  While doing so, we will figure out if there is anything missing.  

Anyway, I am pulling right now to check the latest changes and to run some tests. 

Thank you for your hard work. I am sure the effort will pay off once we got some code samples
 running in a cluster.