Automatic security alerts were created for pyyaml==3.12 and requests==2.19.1 suggesting these packages be upgraded to 2.20.0 and 5.1 respectively. Vulnerabilities addressed: CVE-2018-18074 on requests package CVE-2017-18342 on PyYAML package Change-Id: Iff5bc11d60c2724fef0bb8b2552e17573c79dc9f Signed-off-by: Alexander Hughes <Alexander.Hughes@pm.me>
|1 month ago|
|.github||1 month ago|
|alembic||1 year ago|
|charts/drydock||1 month ago|
|doc||7 months ago|
|etc/drydock||1 year ago|
|go/src/baclient||1 year ago|
|images/drydock||2 months ago|
|python||4 weeks ago|
|tools||1 month ago|
|.dockerignore||1 year ago|
|.gitignore||1 year ago|
|.gitreview||11 months ago|
|.readthedocs.yaml||6 months ago|
|.style.yapf||2 years ago|
|.zuul.yaml||1 month ago|
|LICENSE||3 years ago|
|Makefile||2 months ago|
|README.md||1 year ago|
|alembic.ini||2 years ago|
|entrypoint.sh||2 years ago|
|hostdeps.sh||2 months ago|
|requirements-host-test.txt||1 year ago|
|requirements-host.txt||1 year ago|
|tox.ini||7 months 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/.
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 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.
Use the Airship Promenade tool for starting a self-hosted Kubernetes cluster with Kubernetes Helm deployed.
There are Helm charts for deploying all the dependencies of Dryodck. Use them for preparing your Kuberentes cluster to host Drydock.
Ideally you will use the Airship Armada
tool for deploying the Drydock chart with proper overrides, but if not you can
helm CLI tool. The below are overrides needed during deployment