airship
/
drydock
Code Issues Proposed changes
A declarative host provisioning system.
65 Commits 2 Branches 0 Tags 9.5 MiB
Python 97.2%
Go 1.3%
Shell 0.8%
Smarty 0.3%
Makefile 0.3%
Go to file
Scott Hussey 4efe40d184 Update Dockerfile to better pattern 
Add requirements layer
Add entrypoint.sh script to support future CLI
Change Dockerfile to use ENTRYPOINT
 		2017-06-28 11:26:53 -05:00
drydock_provisioner DRYD2 - MVP - Phase 2 2017-06-14 11:06:19 -05:00
examples Rename helm_drydock to drydock_provisioner 2017-05-25 08:48:27 -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 Update Dockerfile to better pattern 2017-06-28 11:26:53 -05:00
LICENSE Initial commit 2017-02-14 17:23:35 -05:00
README.md Rename helm_drydock to drydock_provisioner 2017-05-25 08:48:27 -05:00
entrypoint.sh Update Dockerfile to better pattern 2017-06-28 11:26:53 -05:00
requirements-direct.txt Update Dockerfile to better pattern 2017-06-28 11:26:53 -05:00
setup.py DRYD-2 MVP - phase 1 - node enlistment 2017-06-12 15:15:17 -05:00
testrequirements.txt Convert the object model to use oslo.versionedobjects (OVO) 2017-05-02 10:57:22 -05:00
tox.ini Initial Python skeleton and the model 2017-02-22 17:32:55 -06: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 run:

$ virtualenv -p python3 /var/tmp/drydock
$ . /var/tmp/drydock/bin/activate
$ python setup.py install
$ uwsgi --http :9000 -w drydock_provisioner.drydock --callable drydock --enable-threads -L

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