A declarative host provisioning system.
Go to file
Scott Hussey 459ddf1023 Update tox with new requirements
Change requirements file naming to be
similar to the requirements-direct.txt name
and update tox.ini with the new name
2017-07-19 13:20:26 -05:00
drydock_provisioner Completion of wiring of design cli commands 2017-07-19 13:20:26 -05:00
examples Add bootdata to sample config 2017-07-13 21:06:20 -05:00
tests Rename helm_drydock to drydock_provisioner 2017-05-25 08:48:27 -05:00
.gitignore Adding Python .gitignore 2017-06-12 15:41:12 +01:00
Dockerfile Initial Dockerfile cleanup 2017-07-18 22:41:08 -05:00
LICENSE Initial commit 2017-02-14 17:23:35 -05:00
README.md Initial Dockerfile cleanup 2017-07-18 22:41:08 -05:00
entrypoint.sh Initial Dockerfile cleanup 2017-07-18 22:41:08 -05:00
requirements-direct.txt Update Dockerfile to better pattern 2017-06-28 11:26:53 -05:00
requirements-test.txt Update tox with new requirements 2017-07-19 13:20:26 -05:00
setup.py Add logging configuration for cli. Begin action approach 2017-07-19 13:20:26 -05:00
tox.ini Update tox with new requirements 2017-07-19 13:20:26 -05: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 cloud-init post-provisioning instructions.

To build and run, first move into the root directory of the repo and run:

$ sudo docker build . -t drydock
$ sudo docker run -d -v $(pwd)/examples:/etc/drydock -P --name='drydock' drydock
$ DDPORT=$(sudo docker port drydock 8000/tcp | awk -F ':' '{ print $NF }')
$ curl -v http://localhost:${DDPORT}/api/v1.0/designs

Modular service

Design Consumer

aka ingester

Pluggable service to ingest a inventory/design specification, convert it to a standard internal representaion, and persist it to the Design State API. Initial implementation is the consumer of YAML schema.

Design State API

aka statemgmt

API for querying and updating the current design specification and persisted orchestration status. CRUD support of CIs that are not bootstrap-related, but can be used by other automation.

Control API

aka control

User-approachable API for initiating orchestration actions or accessing other internal APIs

Infrastructure Orchestrator

aka orchestrator

Handle validation of complete design, ordering and managing downstream API calls for hardware provisioning/bootstrapping

OOB Driver

Pluggable provider for server OOB (ILO) management

aka driver/oob

Node Driver

aka driver/node

Pluggable provisioner for server bootstrapping. Initial implementation is MaaS client.

Introspection API

aka introspection

API for bootstrapping nodes to load self data. Possibly pluggable as this is basically an authenticated bridge to the Design State API