Cyclical healing
Reported by coryodaniel | September 21st, 2008 @ 10:28 AM | in Rubie Can't Fail (0.9.6)
A symlink may depend on a directory, but the directory may not exist yet (and directory runs after symlink). This could be fixed by changing the priorities, but this could introduce a situation where a directory depends on a symlink. Instead, all Managers must ONLY heal their type (ie, symlinks can't do mkdir_p), but there should be some method to go back and heal things that failed.
After healing, put all failtures in a failture bucket for that Manager instance, after healing process, start healing again using just the newest failures, if the number of failures change, continue to loop the healing process until either 0 errors or the error count doesn't change.
Comments and changes to this ticket
-
coryodaniel November 8th, 2008 @ 12:22 PM
- Milestone set to “Rubie Can't Fail (0.9.6)”
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
WarningShot is Depedendency Resolution Framework. Applications can be configured with WarningShot config files, and WarningShot will make sure the environment is configured correctly.
Great for deploying to freshly installed servers or for new developers who don't want to read through a wiki to figure out how to set an application up.
WarningShot is easy to extend and comes packaged with a number of dependency resolvers including: file, directories, binaries, and so forth.
coryodaniel