A declarative host provisioning system.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Zuul c39a4ede1a Merge "Add Redfish as OOB driver" 1 year ago
alembic (format): yapf reformat 2 years ago
charts/drydock Add Redfish as OOB driver 1 year ago
docs Merge "Support multiple rack controllers" 1 year ago
etc/drydock Add Redfish as OOB driver 1 year ago
go/src/baclient Bootaction client initial implementation 1 year ago
images/drydock Merge "Fix: git commit id labels on images" 1 year ago
python Merge "Add Redfish as OOB driver" 1 year ago
tools (fix) Use endpoint for MAAS URL 1 year ago
.dockerignore Refactor build to include Go 1 year ago
.gitignore Refactor build to include Go 1 year ago
.gitreview Update .gitreview for openstack infra 2 years ago
.style.yapf Fix issues failing CI pipeline 2 years ago
.zuul.yaml (zuul) Consolidate tests 2 years ago
LICENSE Initial commit 3 years ago
Makefile Merge "Fix: adding back the possibility to add arbitrary labels" 1 year ago
README.md Fix: various documentation and URL fixes 1 year ago
alembic.ini DRYD47 - Task persistance and refactor 2 years ago
entrypoint.sh uWSGI http-timeout option 2 years ago
hostdeps.sh (zuul) Improve image building 2 years ago
requirements-host-test.txt (zuul) Improve image building 2 years ago
requirements-host.txt (fix) Use endpoint for MAAS URL 1 year ago
tox.ini Security update: Update pyghmi to avoid pycrypto 1 year ago



A python REST orchestrator to translate a YAML host topology to a provisioned set of hosts and provide a set of post-provisioning instructions.

See full documentation at https://airship-drydock.readthedocs.io/.


  • Python 3.5+
  • A running instance of Postgres v9.5+
  • A running instance of Openstack Keystone w/ the v3 API enabled
  • A running instance of Canonical MaaS v2.3+
  • A running Kubernetes cluster with Helm initialized
  • Familiarity with the Airship platform suite of services


This service is intended to be built as a Docker container, not as a standalone Python package. That being said, instructions are included below for building as a package and as an image.


To build and install Drydock locally in a virtualenv first generate configuration and policy file templates to be customized

$ tox -e genconfig
$ tox -e genpolicy
$ virtualenv -p python3.5 /var/tmp/drydock
$ . /var/tmp/drydock/bin/activate
$ pip install -r requirements-lock.txt
$ pip install .
$ cp -r etc/drydock /etc/drydock

Docker image

$ docker build . -t drydock


The preferred deployment pattern of Drydock is via a Helm chart to deploy Drydock into a Kubernetes cluster. Additionally use of the rest of the Airship services provides additional functionality for deploying (Armada) and using (Promenade, Deckhand) Drydock.

You can see an example of a full Airship deployment in the Airship in a Bottle repository.

Stand up Kubernetes

Use the Airship Promenade tool for starting a self-hosted Kubernetes cluster with Kubernetes Helm deployed.

Deploy Drydock Dependencies

There are Helm charts for deploying all the dependencies of Dryodck. Use them for preparing your Kuberentes cluster to host Drydock.

Deploy Drydock

Ideally you will use the Airship Armada tool for deploying the Drydock chart with proper overrides, but if not you can use the helm CLI tool. The below are overrides needed during deployment

  • values.labels.node_selector_key: This is the kubernetes label assigned to the node you expect to host Drydock
  • values.conf.dryodck.maasdriver: This is URL Drydock will use to access the MAAS API (including the URL path)
  • values.images.drydock: The Drydock docker image to use
  • values.images.drydock_db_sync: The Drydock docker image to use