34c6d930e4
Gate enhancements: 1. On certain opendev hardware, it's not possible to change ethtool tunables, or the expected tunables are unavailable. Until we have a mechanism to schedule to the right hardware, we will issue a warning whenever these tests fail instead of failing the gate. 2. Add a check so that gate script will not run until there are no other instances of the gate script running on the same node, as this can cause spurious gate failures. 3. Print gate script tracebacks in the event of gate script faliure 4. Increase check interval for two exec tests that were seen to fail on one ocassion due to insufficient wait time. Change-Id: Ifdbb203a1b14242e3801ba10ef7e932931771878 |
||
---|---|---|
divingbell | ||
doc | ||
tools | ||
.gitignore | ||
.gitreview | ||
.zuul.yaml | ||
LICENSE | ||
Makefile | ||
README.rst | ||
TODO | ||
Vagrantfile | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini |
README.rst
Divingbell
Introduction
Divingbell is a lightweight solution for:
1. Bare metal configuration management for a few very targeted use cases via the following modules:
- apparmor
- ethtool
- exec (run arbitrary scripts)
- system limits
- mounts
- permissions (perm)
- sysctl values
- basic user account management (uamlite)
- Bare metal package manager orchestration using apt module
What problems does it solve?
The needs identified for Divingbell were:
- To plug gaps in day 1 tools (e.g., Drydock) for node configuration
- To provide a day 2 solution for managing these configurations going forward
- [Future] To provide a day 2 solution for system level host patching
Documentation
Find more documentation for Divingbell on Read the Docs.