![](/download/attachments/36966186/image2018-7-17_10-52-40.png?version=1&modificationDate=1531839161000&api=v2)
SDNC Modeling Process (via Controller Design Studio UI). - Heat Mapping: Start by the HEAT environment file as final product required for Openstack spin up. Then for each cloud parameter we define the following:
- Cloud parameters assignment type (Default, Input, Capability)
- Resources ruleset (Assignment logic : Recipe, ingredients, Model-driven vs Custom logic)
- Assignment Capabilities: (microServices, DG-Capability logic, Policy models...)
- Data Dictionaries: Define the SDNC model used to resolve resource values from various systems.
- Define source type (default. Input, DB, A&AI, mS…etc)
- Define model used to retrieve the resource value from the various sub-systems (input-key-mapping, output-key-mapping, url, path)
- Define DD’s name, type, complex data type (if sub-system supports a list of complex data structure)
- Controller Blueprint: Create SDNC model and all associated capabilities, artifact templates, Data Dictionaries
- model Identifier: (model name, version, author…etc)
- Capabilities ( Resource-Assignment, Artifact-template)
- Template Instance (Upload Artifact Templates)
- Edit/View each Artifact Template
- Upload Artifact Template JSON file
- Load template and Auto-Map to Data Dictionaries
- Review Mapping Table and Edit DDs, Default values, DD Source
|