airship/drydock
Code Issues Proposed changes
A declarative host provisioning system.
386 Commits 2 Branches 0 Tags 9.5 MiB
Python 97.2%
Go 1.3%
Shell 0.8%
Makefile 0.3%
Smarty 0.3%
f57301fae9
Go to file
Scott Hussey f57301fae9 Add build data for MAAS logs 
- Collect logs from MAAS when failures happen
  during deployment
- Save the logs to build data so it is available via
  API
- Add postgres integration test

Change-Id: Ied2d8539fe02a75f1f175a421b897b4f8ce07c8d
2018-07-30 10:08:22 -05:00
alembic (format): yapf reformat 2018-07-27 20:16:25 -05:00
charts/drydock Add test pods labels. 2018-07-11 08:05:10 -05:00
docs [411430] Validate bootaction pkg_list 2018-06-12 09:58:02 -05:00
drydock_provisioner Add build data for MAAS logs 2018-07-30 10:08:22 -05:00
etc/drydock Support links for task status 2018-07-27 20:16:24 -05:00
images/drydock Libvirt OOB driver 2018-05-25 11:13:53 -05:00
tests Add build data for MAAS logs 2018-07-30 10:08:22 -05:00
tools (zuul) Consolidate tests 2018-07-20 08:52:44 -05:00
.dockerignore [390773] Support SRIOV fields in definition profiles 2018-03-14 14:12:51 -05:00
.gitignore [390136] Drydock client timeout options 2018-03-07 16:59:15 -06:00
.gitreview Update .gitreview for openstack infra 2018-05-17 19:23:48 +01:00
.style.yapf Fix issues failing CI pipeline 2017-08-24 10:18:11 -05:00
.zuul.yaml (zuul) Consolidate tests 2018-07-20 08:52:44 -05:00
alembic.ini DRYD47 - Task persistance and refactor 2017-10-26 14:54:25 -05:00
entrypoint.sh uWSGI http-timeout option 2018-02-07 13:38:13 -06:00
hostdeps.sh Libvirt OOB driver 2018-05-25 11:13:53 -05:00
LICENSE Initial commit 2017-02-14 17:23:35 -05:00
Makefile Add build data for MAAS logs 2018-07-30 10:08:22 -05:00
README.md Zuul: Initial Airship-Drydock checks 2018-05-24 16:59:12 -05:00
requirements-direct.txt [411429] maasdriver support of packages 2018-06-12 09:58:02 -05:00
requirements-host.txt Update docs for developer overview 2018-06-01 14:50:05 -05:00
requirements-lock.txt [411429] maasdriver support of packages 2018-06-12 09:58:02 -05:00
requirements-test.txt Implement routedomain support 2017-12-14 13:45:38 -06:00
setup.py Refactor orchestrator 2017-10-26 15:00:39 -05:00
tox.ini Unifying proxy variables for tox and docker build 2018-06-22 14:45:51 +02:00

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+

Recommended

  • 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