airship
/
drydock
Code Issues Proposed changes
drydock/drydock_provisioner/objects
History
Scott Hussey 3eac4d4d53 Boot Action document definition 
Boot actions are defined by YAML documents in the site topology.
This PS defines the schema for those documents and adds a representation
to the Drydock ORM and ingester.

- Create JSON schema document for boot action documents
- Model for BootAction objects
- Parsing for BootAction documents

Change-Id: I154807e8400389ff94a596ffd1fb2cab0efa128b
 		2017-10-27 13:55:44 -04:00
..
__init__.py Boot Action document definition 2017-10-27 13:55:44 -04:00
base.py Node storage configuration support 2017-09-21 10:04:18 -05:00
bootaction.py Boot Action document definition 2017-10-27 13:55:44 -04:00
fields.py Refactor orchestrator 2017-10-26 15:00:39 -05:00
hostprofile.py Add Task persistence and KOTH 2017-10-26 14:56:13 -05:00
hwprofile.py Refactor orchestrator 2017-10-26 15:00:39 -05:00
network.py Refactor orchestrator 2017-10-26 15:00:39 -05:00
node.py Node storage configuration support 2017-09-21 10:04:18 -05:00
promenade.py Refactor orchestrator 2017-10-26 15:00:39 -05:00
rack.py DRYD21 - YAPF formatting for 375626 2017-08-25 11:21:22 -05:00
readme.md Rename helm_drydock to drydock_provisioner 2017-05-25 08:48:27 -05:00
site.py Boot Action document definition 2017-10-27 13:55:44 -04:00
task.py Refactor orchestrator 2017-10-26 15:00:39 -05:00

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:

  1. A child overrides a parent for part and subpart attributes
  2. For attributes that are lists, the parent list and child list are merged.
  3. A child can remove a list member by prefixing the value with '!'
  4. 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.