airship/divingbell
Code Issues Proposed changes
A lightweight solution for configuration of baremetal nodes.
133 Commits 1 Branch 0 Tags 2.5 MiB
Shell 56.5%
Smarty 41.9%
Makefile 1%
Python 0.6%
master
Go to file
Mosher, Jaymes (jm616v) c46c253729 Add ignorepkgs option 
Add option for list of packages for divingbell-apt to completely ignore

Change-Id: I79f7ff7887c110d88f052705e2c62f12a6974a30
2024-11-14 10:47:07 -07:00
.github Add SECURITY.md 2020-02-20 17:07:16 -06:00
divingbell Add ignorepkgs option 2024-11-14 10:47:07 -07:00
doc Update zuul gates 2024-11-01 17:09:05 -06:00
tools Update zuul gates 2024-11-01 17:09:05 -06:00
.gitignore [zuul] Zuul gates fixes and Helm version upgrade to 3.x 2022-09-30 01:17:39 +00:00
.gitreview OpenDev Migration Patch 2019-04-19 19:52:20 +00:00
.zuul.yaml Update zuul gates 2024-11-01 17:09:05 -06:00
LICENSE Initial commit 2017-10-17 13:25:54 -05:00
Makefile [zuul] Zuul gates fixes and Helm version upgrade to 3.x 2022-09-30 01:17:39 +00:00
README.rst Enhance docs rendering; update documentation 2019-03-18 22:46:50 +01:00
setup.cfg Exec: Use nsenter to enter all host namespaces when running exec 2019-03-11 19:32:48 -07:00
setup.py docs(tox): Add tox target to generate docs 2018-05-22 14:26:20 -05:00
test-requirements.txt docs(tox): Add tox target to generate docs 2018-05-22 14:26:20 -05:00
TODO Initial commit. 2017-11-16 05:59:36 +00:00
tox.ini Add readiness probe to divingbell-exec 2023-04-30 23:03:17 -05:00
Vagrantfile Update divingbell to use Ubuntu 18.04 2020-09-23 08:57:02 -05:00

README.rst

Divingbell

Documentation Status

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)
  1. Bare metal package manager orchestration using apt module

What problems does it solve?

The needs identified for Divingbell were:

  1. To plug gaps in day 1 tools (e.g., Drydock) for node configuration
  2. To provide a day 2 solution for managing these configurations going forward
  3. [Future] To provide a day 2 solution for system level host patching

Documentation

Find more documentation for Divingbell on Read the Docs.

Further Reading

Airship.