Patrik Lundin
01768129f0
While we already support setting a healthcheck timeout it probably makes sense to be able to control how long we wait for a fleetlock_lock() or fleetlock_unlock() call. This becomes important if only running cosmos once a night or something like that. In that case we you probably want to give a physical machine more than than 1 minute to complete a reboot etc. This can now be controlled by setting fleetlock_lock_timeout and fleetlock_unlock_timeout in /etc/run-cosmos-fleetlock-conf. Keep in mind that while it can make sense to increase the time for taking a lock, releasing a lock should always be fast (either you have it and release it, or you dont have it and it is a no-op) so setting a long unlock timeout should probably never be done. Since we also potentially wait the unlock timeout at boot (if the fleetlock server is broken etc) that is another reason to keep it short. The default 1m is probably OK for most uses. |
||
|---|---|---|
| default | ||
| docs | ||
| fabfile | ||
| global | ||
| scripts | ||
| .gitignore | ||
| addhost | ||
| apt | ||
| bump-tag | ||
| cosmos-rules.yaml | ||
| cosmos.conf | ||
| edit-secrets | ||
| host-puppet-conf-test | ||
| iaas-enable-root.sh | ||
| iaas-setup.sh | ||
| Makefile | ||
| prepare-iaas-debian | ||
| prepare-iaas-ubuntu | ||
| README | ||
The system documentation is in the docs directory of the multiverse repository.