drydock/helm_drydock/drivers
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
..
node Last commit to push changes to master. Will use feature branches 2017-03-15 14:53:46 -05:00
oob Last commit to push changes to master. Will use feature branches 2017-03-15 14:53:46 -05:00
__init__.py Last commit to push changes to master. Will use feature branches 2017-03-15 14:53:46 -05:00
readme.md Last commit to push changes to master. Will use feature branches 2017-03-15 14:53:46 -05:00

readme.md

Drivers

Drivers are downstream actors that Drydock will use to actually execute orchestration actions. It is intended to be a pluggable architecture so that various downstream automation can be used.

oob

The oob drivers will interface with physical servers' out-of-band management system (e.g. Dell iDRAC, HP iLO, etc...). OOB management will be used for setting a system to use PXE boot and power cycling servers.

node

The node drivers will interface with an external bootstrapping system for loading the base OS on a server and configuring hardware, network, and storage.

network

The network drivers will interface with switches for managing port configuration to support the bootstrapping of physical nodes. This is not intended to be a network provisioner, but instead is a support driver for node bootstrapping where temporary changes to network configurations are required.