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
- Add validations that OOB configs for nodes are valid for the
oob type defined
- Add documentation for using Drydock/MAAS to deploy libvirt VMs
- Add logic to update the MAAS node power parameters to allow power
control of libvirt VMs
Change-Id: Ia7d5fbd1659636d46cf1790fe3fc66ca6c6fee89
Hostnames with underscores caused a deployment failure.
Update to use a double underscore as a delimiter and provide
a design validator to check that hostnames do not contain it.
Closes #78
Change-Id: Ib148aed5cffe7fd8bc08441eaef8a45af6601bdd
- Add hugepages and cpu_sets stanzas to HardwareProfile as the
size and count of hugepages and the exact CPUs to pin for SRIOV
are dependent on hardware.
- Add sriov stanza to a node interface to specify vf_count and
trustedmode. These will be passthrough values as Drydock doesn't
configure SRIOV.
- Add sriov information to the bootaction context so it can be written
to disk on a deployed node if needed
- Allow an interface configuration to be skipped when an interface has
no defined network_link for things like SR-IOV interfaces.
- Add kernel parameter reference support to access hardware profile
information
- Add unit tests
- Update topology documentation for usage of HardwareProfile
and kernel parameter references
Change-Id: Iefd326f5c6fad19dbd21300ee249019a3dfd4848
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
Refactor orchestrator to break large
monolithic functions into small functions
per action.
- Update orchestrator to match new statemgmt API
- Pull most code out of __init__.py files
- Create action classes for Orchestrator actions
- Create action classes for Driver actions
- Orchestrator consumes tasks from database queue
- Additional encapsulation of task functionality into Task class
- Create shared integration test fixtures
- Fix Sphinx entrypoint so package install works
- Disable bootdata API until BootAction implementation
- Bring codebase into PEP8 compliance
- Update documentation reflect code changes
- Mark SQL #nosec for bandit
Change-Id: Id9a7bdedcdd5bbf07aeabbdb52db0f0b71f1e4a4
This PS adds tooling and automation to automatically generate
Drydock's documentation into feature-rich HTML pages that can
be hosted.
To run the documentation job, simply execute:
tox -e docs
A future PS should add warning_is_error to 'build_sphinx' in
setup.py once the import warnings are addressed.
Change-Id: I91a3c585b2c27096e7fde12d180638d1ae4bdb81
Roman Gorshunov