drydock/drydock_provisioner/ingester
Scott Hussey 1964d7f9b0 Implement routedomain support
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
2017-12-14 13:45:38 -06:00
..
plugins Implement routedomain support 2017-12-14 13:45:38 -06:00
__init__.py Refactor orchestrator 2017-10-26 15:00:39 -05:00
ingester.py Add deckhand API integration 2017-12-01 11:49:03 -06:00
readme.md Orchestration of MaaS enlistment (#42) 2017-06-15 20:42:53 -07:00

readme.md

Ingester

Ingester is a pluggable consumer of site design data. It will support consuming data in different formats from different sources.

Each ingester plugin should be able source data based on user-provided parameters and parse that data into the Drydock internal model (drydock_provisioner.model).

Each plugin does not need to support every type of design data as a single site design may be federated from multiple sources.