airship
/
drydock
Code Issues Proposed changes
A declarative host provisioning system.
25 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 839c83651f Last commit to push changes to master. Will use feature branches 
going forward

Added readmes to submodules
Refactored model into multiple files
Standardized on 'node' for physical server
Pinned requirements.txt to versions
Began orchestration action outline in conjunction with DAG
 		2017-03-15 14:53:46 -05:00
examples Merge branch 'start_coding' 2017-02-28 15:18:52 -06:00
helm_drydock Last commit to push changes to master. Will use feature branches 2017-03-15 14:53:46 -05:00
tests Last commit to push changes to master. Will use feature branches 2017-03-15 14:53:46 -05:00
LICENSE Initial commit 2017-02-14 17:23:35 -05:00
README.md Last commit to push changes to master. Will use feature branches 2017-03-15 14:53:46 -05:00
requirements.txt Last commit to push changes to master. Will use feature branches 2017-03-15 14:53:46 -05:00
setup.py Last commit to push changes to master. Will use feature branches 2017-03-15 14:53:46 -05:00
testrequirements.txt Initial Python skeleton and the model 2017-02-22 17:32:55 -06:00
tox.ini Initial Python skeleton and the model 2017-02-22 17:32:55 -06:00

README.md

helm_drydock

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.

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