Readthedocs failed to render Drydock exceptions with error:
> WARNING: autodoc: failed to import exception xxx from module
> 'drydock_provisioner'; the following exception was raised: No module
> named 'drydock_provisioner'
Trying to add Drydock requirements to the installed requirements list,
so that Readthedocs has all modules, including those needed for the
Drydock itself.
Unify docs building by utilizing Zuul docs-on-readthedocs template job.
Cosmetic readability changes:
1. combined all Makefile .PHONY targets into one
2. merged multiple LABEL instructions in Dockerfile into one
Change-Id: I6a9b47cffc66d739968fa886c51e25b1e09ef124
1) UCP -> Airship
2) readthedocs.org -> readthedocs.io (there is redirect)
3) http -> https
4) attcomdev -> airshipit (repo on quay.io)
5) att-comdev -> openstack/airship-* (repo on github/openstack git)
6) many URLs have been verified and adjusted to be current
7) no need for 'en/latest/' path in URL of the RTD
8) added more info to some setup.cfg and setup.py files
9) ucp-integration docs are now in airship-in-a-bottle
10) various other minor fixes
Change-Id: I64fb508a3ff72258d82c795193e918f2945deb29
- Added a new query param 'layers=x' to /tasks/{task_id}
where x is a number.
This param allows the API to drill down to all the subtasks.
If x is -1 it will reeturn all subtasks, otherwise it will return
x layers of subtasks.
- Added a new query param 'subtaskerrors=true' to /tasks/{task_id}.
If true then any errors from subtasks will be included in the
subtask_errors element in the response.
- Added a POST to /nodes that requires node_filter and site_design
in the body. Then uses those parameters to return a list of nodes.
Change-Id: I9b4c06dd1c9de2b0500092aa4b4bfacac08eac54
- Add list of build data to detailed task response when builddata=true
specifed in query string
- Add new endpoint for /nodes/nodename/builddata to retrieve
build data for a particular node
- Update docs for new API capabilities
- Testing all around
Change-Id: If0fcd2962d4389789af45ad1fbe61d226ac6a403
Route domains will allow multiple L3 networks
to self organize static routes. This allows additions
of L3 networks with manually updating previously deployed
networks.
- Fix a YamlIngester error with labels on NetworkLinks
- Update the CLI --block option
- Add routedomains attribue to Networks in schema and object model
- Add routedomain documentation
- Add unit test for routedomain route generation
- Add unit test coverage reporting
Change-Id: I059d2eae6da84c4f9ad909f0287432e6cf0970d0
This design is for the framework of deploying actions and assets to
nodes being deployed by Drydock. Included is an API for nodes to
report back the result status of any running boot actions.
Change-Id: I2becd6af33d0202d0da73bab01f21b010fc3ea60
Roman Gorshunov