cc77125953
- Support one or more repo specifications for a site - Add object model for repository - Add testing for repository parsing Update freeze job with make target - Update the requirements freeze job to have a mark target that rebuilds the tox virtualenv each run - Update Dockerfile to create a valid /etc/protocols file Change-Id: I9d09b7dd7226827995e23756ff968b36eaa4d16c |
||
|---|---|---|
| .. | ||
| __init__.py | ||
| base.py | ||
| bootaction.py | ||
| builddata.py | ||
| fields.py | ||
| healthcheck.py | ||
| hostprofile.py | ||
| hwprofile.py | ||
| network.py | ||
| node.py | ||
| promenade.py | ||
| rack.py | ||
| readme.md | ||
| site.py | ||
| task.py | ||
| validation.py | ||
readme.md
Drydock Model
Object models for the drydock design parts and subparts. We use oslo.versionedobjects as the supporting library for object management to support RPC and versioned persistence.
Features
Inheritance
Drydock supports inheritance in the design data model.
Currently this only supports BaremetalNode inheriting from HostProfile and HostProfile inheriting from HostProfile.
Inheritance rules:
- A child overrides a parent for part and subpart attributes
- For attributes that are lists, the parent list and child list are merged.
- A child can remove a list member by prefixing the value with '!'
- For lists of subparts (i.e. HostInterface and HostPartition) if there is a member in the parent list and child list with the same name (as defined by the get_name() method), the child member inherits from the parent member. The '!' prefix applies here for deleting a member based on the name.
Phased Data
The source of the data in a object instance can be one of three types.
- Designed - This is data directly ingested by Drydock representing a design part (Site, HostProfile, etc...) supplied by an external source
- Compiled - This is designed data that has been processed through the Drydock inheritance / merge system. It is the effective design that will be implemented.
- Build - This is the result of actual implementation. It should basically match the compiled view of the model, but might have some additional information only available after implementation.