Design-Time Data Model vs Run-Time Data Model
- Anatoly Katzman
- andreik
Design-Time Model | Run-Time Model | |
What it is | A prototype for multiple deployments. | A live reflection of a running deployment |
What it contains | Contains static definitions and patterns of the future deployments. | Representations of resource/function/service instances running within a deployment. Captures the current state of each instance. Maintains run-time identities. Possibly keeps track of changes. “Links” to the design-time model + perhaps other models (business offers, government regulations, etc.) |
Who creates it | A service designer in SDC | The Orchestration engine business logic (SO, VNF-M), based on the design-time model, driven by policies, external and internal events and operator instructions. |
Lifecycle | Design-time lifecycle: import of vendor models, composition, validation/testing, certification, distribution for deployment. | Run-time lifecycle: instantiation, configuration, activation, changes, state transitions, deactivation, undeployment, etc. "Links" to design-time model: LCM states per nodes etc. |
Where it is stored | SDC Catalog | AAI, DCAE, SO, VNF-M and other run-time componenets |
References | TOSCA names; model UUID (Catalog) | Paths or pointers to run-time instances |