TOSCA Architecture Service Template Catalog Active Service Inventory (“Instance Model”) Substitution / Decomposition Requirement Fulfillment Profile Catalog Resource Inventory Operation Implementations Catalog API Service Management API Workflows Resource Management API 1
TOSCA Instance Model While TOSCA is widely considered a “design-time” language, many TOSCA features operate on runtime instance models: – – – – get_property and get_attribute functions (Dangling) requirement fulfillment Filters (node filters and substitution filters) Condition clauses Workflows Policies … Resulting Requirements: – Introduce a generic “instance model” into the TOSCA architecture • Without actually standardizing the associated Object Models – Define grammar for traversing the instance model topology graph • TOSCA Path 2
Domain-Independent Instance Model Creation Design-Time Model Node Template A Node Template B Run-Time Model Real World Node Instance A Node Instance B 0 Entity A Entity B 0 Node Instance B 1 Service Template Service Instance Domain-Independent (TOSCA Grammar) Entity B 1 Service Entities Domain-Dependent (Artifacts) Orchestrator Domain 3
Domain-Dependent Instance Model Creation Design-Time Model Run-Time Model Node Template A Real World Node Instance A Node Template B Node Instance B 0 Entity A Entity B 0 Node Instance B 1 Service Template Service Instance Domain-dependent translation Entity B 1 Service Entities Domain-Dependent Control Orchestrator Domain 4