Current problem
As we are using basedir for all files, we have some race condition between the stop script wantring to remove files and the scheduler (marvind) wanto to read update files.
Furhtermore, as we add more config files we must keep track of these hidden dependencys in all scripts that use the files
Idea :
Split the different responsibilities between the different scripts so the responsibility is more straight forward.
basedir/schedid/ == user results, "cleaned" by monroe-user-experiments (that also syncs the results to the server)
statusdir/schedid.X where X == status, counters and traffic (more files?), these files are written to by the -deploy -start and -stop scripts but are not removed by them (or select files maybe by -stop or by going into maintenace )
confdir/schedid.Y where Y == conf files/directories, vm disks and such. These files/directories are deleted by the -stop script and when going into maintenance mode
Current problem
As we are using basedir for all files, we have some race condition between the stop script wantring to remove files and the scheduler (marvind) wanto to read update files.
Furhtermore, as we add more config files we must keep track of these hidden dependencys in all scripts that use the files
Idea :
Split the different responsibilities between the different scripts so the responsibility is more straight forward.
basedir/schedid/ == user results, "cleaned" by monroe-user-experiments (that also syncs the results to the server)
statusdir/schedid.X where X == status, counters and traffic (more files?), these files are written to by the -deploy -start and -stop scripts but are not removed by them (or select files maybe by -stop or by going into maintenace )
confdir/schedid.Y where Y == conf files/directories, vm disks and such. These files/directories are deleted by the -stop script and when going into maintenance mode