High Level Solution Architecture REST API create VF

High Level Solution Architecture • REST API – create VF module Design Time • VNF Onboarding in SDC using TOSCA SO • TOSCA csar contains cloud specific Tosca extensions, install scripts, etc • Run Time Cloud auth info Service design • BPMN does the following: • gets the cloud authentication information from AAI-ESR VNF AAI-ESR BPMN • The Northbound API of SO – ‘Create VNF module’ is invoked Assigned data (pre-load) SDC SDNC Homing (simulator) • gets the assigned resource data from SDNC (pre-load) • Invokes a homing simulator which specifies the cloud region where the VNF is to be deployed • invokes the Multi. VIM adaptor Distribute artifacts SO DB • Multi. VIM adaptor does the following: Get CSAR Multi. VIM Adaptor two calls: 1. Create stack 2. Get stack • gets the Azure TOSCA extension csar MSB (API Gateway) • Invokes the ‘Create Stack’ API of Multi. VIM via MSB • Azure plugin returns a ‘stack. ID’ (service. ID of Aria) • Polls the status of the stack creation by invoking the ‘Get stack’ API of Multivim Multi. VIM config broker • Broker resolves the cloud plugin using the cloud info given by SO and passes the payload to the Azure plugin. • Azure plugin converts the TOSCA azure extensions from the CSAR to Azure specific API’s and deploys the VNF Azure plugin • Azure plugin consists of ARIA TOSCA parser and Cloudify Azure plugin. • SO updates the inventory to store the ‘stack. ID’ in AAI. Note : Legend Not all components are shown in the diagram as there are no changes in other components Some details during design time like service catalog and run time details like service and vnf creation flows are not shown as these have not changed Azure cloud New components Existing components