ONAP External APIs Proj Plan

ONAP External APIs Proj Plan

Defining ONAP APIs With BSS/OSS 28 June 2017 Andy Mayer, Ph.D. 2016 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property. AT&T Proprietary (Internal Use Only). Not for use or disclosure outside the AT&T companies except under written agreement. What Common APIs between ONAP and BSS/OSS allow Service Providers to utilize the capabilities of ONAP while using their existing BSS/OSS environment minimizing customization ONAP Architecture ONAP Portal E Services BSS / OSS OA&M Data Collection & Analytics Service Service Design Design & & Creation Creation Analytic Analytic Application Application Design Design Design Functions Active & Available Inventory Service Orchestrator Common Services, Data Movement, Access Control & APIs Recipe/ Recipe/ Engineering Engineering Rules Rules & & Policy Policy Distribution

Distribution Policy Policy Creation Creation External External Data Data Movement Movement & & APIs APIs Dashboard Operation Operation Administration Administration & & Maintenance Maintenance Big Data Operational Functions ONAP Controller Storage Compute Networking VNFs / Applications Controllers Engineering Engineering Rules Rules & & Inventory Inventory Why Service Providers need a clear and unambiguous ONAP service abstraction so that the BSS/OSS can exchange service requirements and service capabilities in a common and consistent fashion. Service Providers want to rapidly integrate new Services and Service Components into ONAP so that they can quickly introduce capabilities for their customers and within their infrastructure. Service Providers want to manage the entire lifecycle of Services within ONAP in a common way so that they can ensure orchestration, manageability and

control of each Service in an easily integrateable and low cost way. Model Driven approach: a cohesive way to have a shared view of information across ONAP external interfaces that can be used for or be input into a model driven process whereby the cost of delivering platform functionality is drastically reduced and the time to delivery is dramatically decreased. E Services BSS/OSS Interactions With ONAP BSS / OSS Big Data Service feasibility; External Data Movement & APIs ONAP Portal Dashboard Service provisioning configuration & activation; OA&M Request fallout; Operation Service Active & Available Administration Usage events & metrics; Orchestrator Inventory & Maintenance License accounting; Service performance & quality (e.g., KPI); Common Services, Data Movement, Access Control & APIs Service trouble management; Recipe/Engineering Service policy; Rules & Policy Capacity engineering; Data Collection & Distribution Controllers Engineering Rules Address allocation management; Analytics Analytics Service Design & Creation Policy Creation

Operational Functions ONAP Controller Analytic Application Design Design Functions 2017 AT&T Intellectual Property. All rights reserved. AT&T, Globe logo, Mobilizing Your World and DIRECTV are registered trademarks and service marks of AT&T Intellectual Property and/or AT&T affiliated companies. All other marks are the property of their respective owners. Storage Compute Networking VNFs / Applications & Inventory E Services BSS/OSS Interactions With ONAP ONAP Portal BSS / OSS Big Data Initial Focus on BSS/OSS: External Data Movement & APIs Dashboard Service provisioning configuration & activation; OA&M Operation management; Active & Available License Administration Address allocation management; Inventory & Maintenance Service Orchestrator Common Services, Data Movement, Access Control & APIs Recipe/Engineering Rules & Policy Distribution Service Design & Creation

Policy Creation Data Collection & Analytics Operational Functions ONAP Controller Analytic Application Design Design Functions 2017 AT&T Intellectual Property. All rights reserved. AT&T, Globe logo, Mobilizing Your World and DIRECTV are registered trademarks and service marks of AT&T Intellectual Property and/or AT&T affiliated companies. All other marks are the property of their respective owners. Storage Compute Networking VNFs / Applications Controllers Engineering Rules & Inventory Related ONAP Projects Modeling Project Identify overall modeling guidelines and approaches, determine modeling tools and tool chaining, and identification of industry standard models (e.g., TMF SID, ONF TAPI, etc.) that may be applied to the APIs Service Orchestrator Project Gather information about the relevant Service Orchestrator APIs (particularly the Service Instantiation API). Will collaborate with Service Orchestrator team to ensure that APIs remain consistent for R1. Change Management project Define external API capabilities to support the Change Management DMaaP Data Filtering, data transport, and data processing Standards Coordinator

Related activities in the TM Forum, MEF, etc. High Level Project Plan For Release 1 Focus: Service Instantiation; License Management; Network Address Space Management Common APIs between ONAP and BSS/OSS allow Service Providers to utilize the capabilities of ONAP using their existing BSS/OSS environment with minimal customization 1. Analysis of current Service Orchestrator APIs and flows 2. Functional description of target ONAP capabilities for interactions with BSS/OSS 3. Functional reference architecture (MEF LSO mapping, Interface Reference Point definition, etc.) Note that the BSS/OSS to ONAP APIs are relevant to the MEF LSO Legato Interface Reference Point. 4. Identify BSS/OSS ONAP Use Cases and interactions 5. Definition of information model for ONAP service abstraction (with Modeling Project) 6. API definition (e.g., JSON) in cooperation with ONAP Projects (including Service Orchestrator) Time Line ONAP-BSS/OSS APIs Select a period to highlight at right. A legend describing the follows. Plan DurationM2 M1ng 1 charti ACTIVITY PLAN START Project Project Scope June WEEKS 1 29 2 June 3 4 PLAN 12 DURATION Analyze SO APIs 1 4 Fnct Ref Arch 1

4 Target Capabilities 1 4 Use Cases 2 4 Service Abstraction 2 6 UML Models - SI 4 4 API - SI 6 5 UML Models - Lic 4 4 API - Lic 6 5 UML Models - Addr 4 4 API - Addr

6 5 5 Actual M3 Start Functionali API ty 24 August 6 3 August 7 8 9 10 11 12 13 Possible Approach Define BSS/OSS ONAP Use Cases, Interactions, Information Model, and API description Apply MEFs LSO Reference Architecture; Interface Reference Points, Operational Threads, etc. (MEF was working with OPEN-O on relating architecture and APIs) Work with Modeling Project to determine base service abstraction Information Model on best in breed standard models (e.g., ONF TAPI, TM Forum, etc.) API Development: Well defined specifications for the BSS/OSS APIs (e.g., JSON Swagger). These define what the BSS/OSSs would need to build to. An ONAP implementation of these APIs o Engage MEF / ONF TAPI based APIs where applicable o Explore use of Tool Chain to automatically generate APIs based on models Characterize Current ONAP Interactions with BSS/OSS Identify relevant ONAP Component APIs Characterize and describe interactions supported by each API This set of interactions becomes the current capabilities base that will be used for gap analysis and identification of API enhancements or the need for additional APIs ONAP Component BSS/OSS Type Interaction Description Service Orchestrator Ordering

Service Instantiation ... ... ... 10 Describe Target Use Cases & Interactions (Example) sd Simple Serviceability and Ordering Customer BSS/OSS ONAP Network Cloud Feasibility & Quote Inq() Component Serviceability() Response() Response() Customer Order() Service Fulfillment() NF & Connect Activation() Response() Test Rqst() Response() Response() Response() 11 Describe Shared ONAP Service Abstraction (Example) class Serv ice Characteristics ServiceNetworkAssociation Serv iceNetw orkAssociation DirectedGraph Recipe A 0..* Serv iceCatalogItemVersion ServiceCatalogItemModificationsRecordedAs * Serv iceCatalogItemCharacteristicValueRelationship

ServiceCatalogItemCharacteristicValueReferences 0..* 0..* Serv iceCatalogItemCharacteristicValue - unitOfMeasure: String value: String valueType: String 0..1 * 0..* ServiceCatlogItemCharUseDescribedBy 0..* 1 1 - AT&T Contact: char Capacity: Document 1.. Category: DropDown Constraints Cost: char D2RequirementsChecklist: Document EntitlementID: char EntitlementUnitNumber: char EntitlementUnitType: char FaultRequirements: Document Features: Document History: char Icon: Image LicensingModel: DropDown Performance: Document Requirements ServiceDescription: char ServiceDisplayName: char ServiceSystemName: Char ServiceUUID: char Status: char Subcategory: DropDown T ags/Keywords: Char T emplate: DropDown T estScripts: Document VendorTestResults: Document

Version: char VF-SpecificPolicies: File VFArtifacts: char VFConfigParameters: File VFImage: char Can have high level characteristic to address functional dimensions, including application, operations, security, & environment. Can be further broken down to address multi-tenancy. ServiceCatalogItemMadeAvailableAs ServiceNetworkAssoc may be the relationship and not an object by itself 0..* InstanceItem Requires 0..* InstanceItem Serv iceInstance 0..* 1 ServiceInstanceCharactieristicValue DefinesT heConfigurationOf * Serv iceInstanceCharacteristicValue ServiceSpecDescribes * 0..1 ServiceCatalogItemDescribedBy 0..* Serv iceItemCharacteristic 0..1 - Description: String Name: String 0..*

0..1 Serv iceCatalogItemCharacteristicRelationship 0..* ServiceCatalogItemCharacteristicReferences ServiceCatalogItemCharacteristicValueInstanciatedAs 0..* ServiceInstanceCharacteristicValueReferences 0..* CanBeOverridden: boolean MaxCardinality: int MinCardinality: int ServiceCatalogItemEnumeratedBy 1 Serv iceCatalogItem Serv iceCatalogItemCharacteristicUse - 12 CatalogItem CatalogItem Serv iceRecipe use flow 0..* Name: Author: Version: Created: Updated: Service Characteristics KS0567 1.0 10/26/2015 12:00:00 AM 10/21/2016 1:22:52 PM

* Define APIs (Example) createServiceInstance Client Service Instantiation Client Service Instantiation POST /serviceInstances/v3 POST /serviceInstances/v3/ {serviceInstanceId}/replace 202 with serviceInstanceId and requestId or 4xx/5xx with requestError 202 with new serviceInstanceId and requestId or 4xx/5xx with requestError (0 Many) asyncRequestStatus callbacks Client replaceServiceInstance sync response (0 Many) asyncRequestStatus callbacks optional async responses Service Instantiation Client deleteServiceInstance Client 13 Client sync response optional async responses

Service Instantiation updateServiceInstance Service Instantiation Client Service Instantiation DELETE /serviceInstances/v3/{serviceInstanceId} PUT /serviceInstances/v3/{serviceInstanceId} 202 with serviceInstanceId and requestId or 4xx/5xx with requestError sync response 202 with serviceInstanceId and requestId or 4xx/5xx with requestError sync response (0 Many) asyncRequestStatus callbacks optional async responses (0 Many) asyncRequestStatus callbacks optional async responses Service Instantiation Client Service Instantiation BACKUP MATERIAL 14 2016 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property. AT&T Proprietary (Internal Use Only). Not for use or disclosure outside the AT&T companies except under written agreement.

Recently Viewed Presentations

  • Meet the Oxford Reading Tree Characters This is

    Meet the Oxford Reading Tree Characters This is

    This is Wilf and Wilma. They are Biff and Chip's friends. Wilf and Wilma are brother and sister.
  • Things to know for tomorrows quiz  Static electricity

    Things to know for tomorrows quiz Static electricity

    Bohr-Rutherford Diagram Rules. The atomic number of an element shows you how many protons and electrons there are (# of protons = # of electrons). ... Notation for Boron-10 and Boron-11. Mass number. Atomic number. Notation for Boron-10 and Boron-11....
  • Credit Card Reconciliation Finance Systems Training Finance Business

    Credit Card Reconciliation Finance Systems Training Finance Business

    - prior payments received - previous unsettled charges - tax free items Refer to Finance Knowledge Base under Purchasing for guidance - Mixed Treatment Invoices: GST NOT = 1/11th of the Total Invoice 5 - Coles Randwick Taxable Items -...
  • Part II: Preparation/Process - Professor Mark J. Grossman

    Part II: Preparation/Process - Professor Mark J. Grossman

    Receiver's Bias: Peer Groups and Media. Peer pressure influences the way messages are perceived. Peer groups influence attitudes and actions. Media is a powerful agenda setter - tells us what issues are important
  • Unit 3 Part 1 Resistance to Slavery Divides the Nation

    Unit 3 Part 1 Resistance to Slavery Divides the Nation

    Pre-Beard Lincoln. John Brown and His Failed Raid on Harper's Ferry. John Brown, a white abolitionist, planned to end slavery by force. ... Unit 3 Part 1 Resistance to Slavery Divides the Nation Last modified by: Gay, Jonathan
  • S5 Pupils CfE Presentation

    S5 Pupils CfE Presentation

    Other mandatory requirements: Not considered for entry from S5. S5 grades must include Chemistry and Biology, and either Maths or Physics. It is acceptable to take Biology, Chemistry, Maths or Physics as crash Highers in S6, a minimum Grade B...
  • Assemblee Generale De La Section Regionale

    Assemblee Generale De La Section Regionale

    PRESENTATION DE L'UNAF Power Point GB 03_03_17 L'UNAF est dirigée par un Comité National de 11 membres Didier LACHIZE Jean Pierre ZAMO Pascal FOIRET Jérôme LANIER Président Délégué Adhésions, Bulletin, Communication, Informatique, Photothèque Vice Président Trésorier Payeur Solidarité Secrétaire Général...
  • Research Questions and Projects

    Research Questions and Projects

    Arial Default Design Research Questions and Projects Veronica Renee Boehmer: Source of Fatigue and Love Research Process Origin of Research Questions Beginning Empirical Research: Reasoning Deductive and Inductive Logic Social research strategies Subjectivity and Ideas Slide 9 Slide 10 Slide...