airship
/
drydock
Code Issues Proposed changes
drydock/helm_drydock/drivers
History
Scott Hussey 2f1968fa25 Convert the object model to use oslo.versionedobjects (OVO) 
- Initially this is a naive implementation and not
fully utilizing the abilites of OVO
- Updated test YAML files to match model
- Did not convert Task objects as they will be refactored
for Celery in the near future
 		2017-05-02 10:57:22 -05:00
..
node Last commit to push changes to master. Will use feature branches 2017-03-15 14:53:46 -05:00
oob Convert the object model to use oslo.versionedobjects (OVO) 2017-05-02 10:57:22 -05:00
__init__.py Convert the object model to use oslo.versionedobjects (OVO) 2017-05-02 10:57:22 -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.