airship
/
divingbell
Code Issues Proposed changes
A lightweight solution for configuration of baremetal nodes.
68 Commits 1 Branch 0 Tags 2.5 MiB
Shell 56.8%
Smarty 41.6%
Makefile 1%
Python 0.6%
Go to file
Anderson, Craig (ca846m) 87268308f8 Use common logger for consistent log output 
Use the common logger for consistent log output for some echo statements
that were not making use of it.

Change-Id: I7fae2a950318f5cd3245a4571dc464009726d4ae
 		2019-04-11 13:23:05 -07:00
divingbell Use common logger for consistent log output 2019-04-11 13:23:05 -07:00
doc Enhance docs rendering; update documentation 2019-03-18 22:46:50 +01:00
tools Use common logger for consistent log output 2019-04-11 13:23:05 -07:00
.gitignore Enhance docs rendering; update documentation 2019-03-18 22:46:50 +01:00
.gitreview Update .gitreview for openstack infra 2018-05-17 20:03:32 +00:00
.zuul.yaml Set up publishing of docs 2018-10-04 16:38:36 +00: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.