A configuration management service with support for secrets.
Go to file
Zuul 64975c820a Merge "doc(typo): Correct spelling" 2018-08-08 22:05:17 +00:00
alembic [396582] Add alembic support to Deckhand 2018-04-06 23:30:16 -04:00
charts/deckhand Add test pods labels. 2018-07-11 08:47:48 -05:00
deckhand Merge "Remove deprecated substitution_sources kwarg" 2018-08-02 18:55:36 +00:00
doc Merge "doc(typo): Correct spelling" 2018-08-08 22:05:17 +00:00
etc/deckhand Add missing Keystone options to registration of config 2018-06-16 06:31:03 +00:00
images/deckhand Allow Deckhand image to be built behind proxy 2018-06-07 21:18:51 +01:00
releasenotes style(pep8): remove identation ignores 2018-06-01 22:08:42 +00:00
tools Move to stestr for functional/integration tests 2018-07-21 15:32:26 -04:00
.coveragerc Add Deckhand coverage job 2017-08-15 16:11:35 -04:00
.dockerignore Collect profile data on DH requests 2018-02-15 13:09:16 -05:00
.gitignore Add integration tests job to .zuul.yaml 2018-07-03 02:07:19 +00:00
.gitreview Update .gitreview for openstack infra 2018-05-17 19:21:56 +01:00
.stestr.conf Switch to stestr 2018-03-28 13:06:46 -04:00
.zuul.yaml trivial: Use airship-deckhand-single-node for nodeset in zuul.yaml 2018-07-11 09:50:38 -04:00
HACKING.rst Add sphinx job for auto-generating docs 2017-09-21 16:16:23 +01:00
LICENSE Update Apache LICENSE 2018-05-10 22:25:14 +01:00
Makefile Unifying proxy variables for docker build 2018-06-22 14:43:03 +02:00
README.rst Rename some instances of ucp to airship 2018-07-23 20:56:00 +01:00
REVIEWING.rst docs: Add developer overview documentation 2018-06-20 15:00:46 -04:00
alembic.ini [396582] Add alembic support to Deckhand 2018-04-06 23:30:16 -04:00
entrypoint.sh [fix] Drop deckhand.conf from default DECKHAND_CONF_DIR path 2018-04-07 00:20:47 -04:00
requirements.txt Add cryptography to Deckhand 2018-07-30 12:21:16 -05:00
setup.cfg Update releasenotes/docs tox jobs 2018-04-24 22:34:49 +01:00
setup.py Oslo config integration (#1) 2017-06-26 16:57:50 -07:00
test-requirements.txt Update Deckhand test-/requirements.txt 2018-06-16 18:18:28 -04:00
tox.ini Merge "Move to stestr for functional/integration tests" 2018-07-29 06:28:20 +00:00

README.rst

Deckhand

Doc Status

Deckhand is a storage service for YAML-based configuration documents, which are managed through version control and automatically validated. Deckhand provides users with a variety of different document types that describe complex configurations using the features listed below.

Find more documentation for Deckhand on Read the Docs.

Core Responsibilities

  • layering - helps reduce duplication in configuration by applying the notion of inheritance to documents
  • substitution - provides separation between secret data and other configuration data for security purposes and reduces data duplication by allowing common data to be defined once and substituted elsewhere dynamically
  • revision history - maintains well-defined collections of documents within immutable revisions that are meant to operate together, while providing the ability to rollback to previous revisions
  • validation - allows services to implement and register different kinds of validations and report errors
  • secret management - leverages existing OpenStack APIs -- namely Barbican -- to reliably and securely store sensitive data

Getting Started

For more detailed installation and setup information, please refer to the Getting Started guide.

Testing

Automated Testing

To run unit tests using sqlite, execute:

$ tox -epy27
$ tox -epy35

against a py27- or py35-backed environment, respectively. To run individual unit tests, run:

$ tox -e py27 -- deckhand.tests.unit.db.test_revisions

for example.

To run functional tests:

$ tox -e functional

You can also run a subset of tests via a regex:

$ tox -e functional -- gabbi.suitemaker.test_gabbi_document-crud-success-multi-bucket

Integration Points

Deckhand has the following integration points:

Note

Currently, other database back-ends are not supported.

Though, being a low-level service, has many other UCP services that integrate with it, including:

  • Drydock is orchestrated by Shipyard to perform bare metal node provisioning.
  • Promenade is indirectly orchestrated by Shipyard to configure and join Kubernetes nodes.
  • Armada is orchestrated by Shipyard to deploy and test Kubernetes workloads.

Further Reading

Airship.