History

Scott Hussey 28d460590c DRYD-31 Drydock driven by a config file Config file support via oslo_config Example config file in examples/drydock.conf		2017-07-05 10:22:30 -05:00
..
__init__.py	Orchestration of MaaS enlistment (#42 )	2017-06-15 20:42:53 -07:00
api.py	Orchestration of MaaS enlistment (#42 )	2017-06-15 20:42:53 -07:00
base.py	Merge branch 'master' into dryd_2_node_commission	2017-06-23 08:04:29 -05:00
designs.py	Orchestration of MaaS enlistment (#42 )	2017-06-15 20:42:53 -07:00
middleware.py	DRYD-31 Drydock driven by a config file	2017-07-05 10:22:30 -05:00
readme.md	Merge branch 'master' into module_rename	2017-06-23 07:54:14 -05:00
tasks.py	Orchestration of MaaS enlistment (#42 )	2017-06-15 20:42:53 -07:00

readme.md

Control

This is the external facing API service to control the rest of Drydock and query Drydock-managed data.

v1.0 Endpoints

/api/v1.0/tasks

POST - Create a new orchestration task and submit it for execution GET - Get status of a task DELETE - Cancel execution of a task if permitted

/api/v1.0/designs

POST - Create a new site design so design parts can be added

/api/v1.0/designs/{id}

GET - Get a current design if available. Param 'source=compiled' to calculate the inheritance chain and compile the effective design.

/api/v1.0/designs/{id}/parts

POST - Submit a new design part to be ingested and added to this design GET - View a currently defined design part PUT - Replace an existing design part Not Implemented

/api/v1.0/designs/{id}/parts/{kind}/{name}

GET - View a single design part. param 'source=compiled' to calculate the inheritance chain and compile the effective configuration for the design part.