TOSCA Orchestration Paradigm Northbound APIs VNF VNF VDU Managed Service Components VDU VDU VDU VNF VNF VDU Resource Resource VDU VDU VDU Operate Southbound APIs Hosted On Monitor Resource Resource

TOSCA Orchestration Paradigm (cont’d) Northbound APIs API inputs (specified in topology_template) initialize instance model Using get_input By driving substitution mapping By defining node filters to fulfill requirements API Inputs VNF VNF VDU VDU VDU VDU Interface Operations defined in service templates provide southbound APIs to communicate with managed service components Resource Resource Operations retrieve inputs from instance model Using get_property or get_attribute Operation Inputs Southbound APIs

Managing a Running Service Challenge How to define lifecycle management tasks in TOSCA for managing a running service? Current solution Imperative workflows Problem Imperative workflows bypass instance model Copyright © 2019 Ubicity Corp.

Managing a Running Service Northbound APIs Imperative workflows cannot be used to modify instance model Change configuration values Change deployment flavor Change external connectivity API calls map to imperative workflows VNF VNF API inputs are passed directly to workflows Bypassing the instance model VDU VDU VDU VDU Resource Resource API Inputs Operation Inputs Imperative Workflows Workflow Inputs Southbound APIs