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.
 
 
 
 
 
Scott Hussey ecb3e01527
Bootaction client initial implementation
4 years ago
alembic (format): yapf reformat 5 years ago
charts/drydock Update Keystone API ports in Drydock chart 5 years ago
docs Bootaction cleanup 4 years ago
etc/drydock Add destroy_node config items to sample 5 years ago
go/src/baclient Bootaction client initial implementation 4 years ago
images/drydock Bootaction cleanup 4 years ago
python Bootaction cleanup 4 years ago
tools Refactor build to include Go 4 years ago
.dockerignore Refactor build to include Go 4 years ago
.gitignore Refactor build to include Go 4 years ago
.gitreview Update .gitreview for openstack infra 5 years ago
.style.yapf Fix issues failing CI pipeline 6 years ago
.zuul.yaml (zuul) Consolidate tests 5 years ago
LICENSE Initial commit 6 years ago
Makefile Bootaction client initial implementation 4 years ago
README.md Zuul: Initial Airship-Drydock checks 5 years ago
alembic.ini DRYD47 - Task persistance and refactor 5 years ago
entrypoint.sh uWSGI http-timeout option 5 years ago
hostdeps.sh (zuul) Improve image building 5 years ago
requirements-host-test.txt (zuul) Improve image building 5 years ago
requirements-host.txt (zuul) Improve image building 5 years ago
tox.ini Refactor build to include Go 4 years ago

README.md

drydock_provisioner

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 http://att-comdev-drydock.readthedocs.io/.

Required

  • 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 AT&T Community Undercloud Platform (UCP) suite of services

Building

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.

Virtualenv

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

Running

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 UCP services provides additional functionality for deploying (Armada) and using (Promenade, Deckhand) Drydock.

You can see an example of a full UCP deployment in the UCP Integration repository.

Stand up Kubernetes

Use the UCP 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 UCP 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