airship
/
divingbell
Code Issues Proposed changes
A lightweight solution for configuration of baremetal nodes.
101 Commits 1 Branch 0 Tags 2.5 MiB
Shell 56.8%
Smarty 41.6%
Makefile 1%
Python 0.6%
Go to file
Schiefelbein, Andrew (as3525) as3525@att.com ac357b9bff This is to allow for ganged install of packages instead of single 
package installations with apt

Change-Id: Ifd268e7eca212fb5686b30213c1c7c1e47f5eb25
 		2020-01-17 16:03:03 -06:00
divingbell This is to allow for ganged install of packages instead of single 2020-01-17 16:03:03 -06:00
doc apt: chart update: allow conf.apt.packages as map 2020-01-07 12:31:53 -08:00
tools apt: chart update: allow conf.apt.packages as map 2020-01-07 12:31:53 -08:00
.gitignore Enhance docs rendering; update documentation 2019-03-18 22:46:50 +01:00
.gitreview OpenDev Migration Patch 2019-04-19 19:52:20 +00:00
.zuul.yaml Fix airship-divingbell-ubuntu zuul gate 2020-01-07 12:31:53 -08:00
LICENSE Initial commit 2017-10-17 13:25:54 -05:00
Makefile Create Makefile target to install Helm binary 2018-11-26 16:34:45 -06:00
README.rst Enhance docs rendering; update documentation 2019-03-18 22:46:50 +01:00
TODO Initial commit. 2017-11-16 05:59:36 +00:00
Vagrantfile Minor: Git URI schema and URL change 2019-03-21 00:57:07 +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
tox.ini Set up publishing of docs 2018-10-04 16:38:36 +00: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.