Currently the wake/sleep status of Workers is managed by local cron jobs. This is both invisible (as it's a root-editable-only text file somewhere on the system) and hard to work with (workers cannot query "what is my expected status?"). This caused sleeping workers to become active after a restart. Scheduling the wake/sleep status via the Manager would solve this.
- Manager knows which status a worker should be in, and the worker can periodically check this.
- The schedule can be centrally edited via the Manager dashboard and thus be visible to everybody involved.