Master Service Orchestrator MSO Highlevel Design Copyright 2017

Master Service Orchestrator (MSO) High-level Design Copyright © 2017 AT&T Intellectual Property. All rights reserved. Licensed under the Creative Commons License, Attribution 4. 0 Intl. (the "License"); you may not use this documentation except in compliance with the License. Open. ECOMP MSO High-level design

MSO: High Level Architecture and Interfaces OSS/BSS SDC Infrastructure Portal Service Order Requests Design Studio Distribution Service … and others VNF & Network Requests Service & Resource Artifacts AAI Master Service Orchestrator (MSO) Data Collector DCAE MSO metrics collection and fault monitoring Create/Update Virtual Resources Inventory Assign/Configure Resources Fault Collector Platform/Cloud Orchestrator Cloud Page 2 SDN Controller Open. Stack VM v. CE VM Open. ECOMP MSO High-level design APP Controllers VM VM

MSO: Software Architecture OCX/OMX Infrastructure Portal CSI REST SDC MSO … REST API Handler Request Handlers REST Service Recipes BPEL Execution Engine Data Stores Catalog DB Service Recipe Request DB REST HEAT Templates SOAP Resource/Controller Adapters VNF Resource Adapter Controller Adapter Network Adapter KEYSTONE/ HEAT Cloud Platform Orchestrator REST SDN Controller APP Controller Page 3 Open. ECOMP MSO High-level design AAI

MSO Interfaces – Other Open. ECOMP Components SDC § § Distribution of orchestration artifacts (service & resource recipes and templates) UEB event notifications, HTTP artifact retrieval AAI § Query and update inventory § RESTful API Cloud (Platform Orchestrator) § § Instantiation of virtual resources in the cloud Openstack APIs (primarily Heat and Keystone) SDN Controller § § Assign and configure network resources Yang-based RPC and REST App Controller (pending) § § Assign and configure application resources Yang and/or event based API Page 4 Open. ECOMP MSO High-level design

MSO Sub-components(1) API Handler § RESTful interface to northbound clients Handle service-level and infrastructure (VNF & network) requests § § § Use MSO Catalog to map input requests to recipes (BPEL flows) Track open and completed requests via MSO Request DB BPEL Execution Engine § § Execute BPEL service recipes Sequence orchestration steps by invoking Adapters for each Resource in the recipe § § § request and configure network resources via SDN-C manage cloud resources via PO (Open. Stack) configure Application VNFs via APP-C update inventory via AAI Perform additional orchestration steps (consult policy, etc. ) per individual recipes Perform error handling/rollback Page 5 Open. ECOMP MSO High-level design

MSO Sub-components(2) Resource Adapters § Provide interfaces to lower level controllers and other Open. ECOMP components Platform Orchestrator, SDN-Controller, APP Controller § § Hides the details of complex interfaces (e. g. Open. Stack APIs) via higher-level calls Expose interfaces to BPEL flows as SOAP or REST APIs (synchronous/asynchronous) Use MSO Catalog to map resource requests to a recipe/template VNF > Heat templates § § § SDN Resource > Yang models Merge input parameters with templates at run-time Data Stores § Request DB § § Tracks open and completed requests MSO Catalog § § Page 6 MSO view of the SDC Catalog • Service and resource recipes, templates, and definitions Populated via SDC distribution service Open. ECOMP MSO High-level design