3007010064
The hash used by divingbell-perms to decide whether or not to rerun the permissions script was being generated incorrectly, using a fixed value instead of actually looking at the values passed to the chart. This change updates the hash to reflect conf.divingbell.perms, and will rerun the script if the hash changes. Also fixes the logic to revert permissions. Change-Id: I74f056f69a1b7f0eb9223915b1671e1e18091483 |
||
---|---|---|
.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.