c39963341f
1. OSH jobs now require gate_scripts_relative_path variable to be explicitly defined. 2. Strict-mode test cases require a test package that does not have to install dependencies, or the test case will fail (since strict mode will uninstall the dependency package and thus the originally requested package). 3. Reduce redundant logging of the entire pod log every time the pod status is checked; this was causing long test cases (e.g. apt strict mode) to fail. 4. Add a helper function to dump the pod log for debugging failed test cases, since we will no longer have the redundant logs above. Change-Id: I7d2f6d2d161689a8744275b3d07571c83862a89c |
||
---|---|---|
.github | ||
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.