ONAP Service Assurance Data Driven Flows

Slides:



Advertisements
Similar presentations
A Java Architecture for the Internet of Things Noel Poore, Architect Pete St. Pierre, Product Manager Java Platform Group, Internet of Things September.
Advertisements

1 Doctor Fault Management 18 May 2015 Ryota Mibu, NEC.
Gerald Kunzmann, DOCOMO Carlos Goncalves, NEC Ryota Mibu, NEC
© 2015 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property. 1 VF (Virtual Functions) Event.
© 2016 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property. VF (Virtual Functions) Event.
SDN-O LCM for Mercury Release Key Points and Overview
ONAP E2E Flow `.
ONAP Management Requirements
Bryan Sullivan, AT&T June 13, 2017
Master Service Orchestrator (MSO)
ONAP and MEF LSO External API Framework Functional Reference Architecture 12 July 2017 Andy Mayer, Ph.D. © 2016 AT&T Intellectual Property. All rights.
Orchestration and Controller Architecture Alignment Vimal Begwani AT&T
Rationalizing ONAP Architecture for R2 and Beyond Vimal Begwani – AT&T
Defining ONAP APIs With BSS/OSS
Data Collection Framework
VNF Event Streaming: Onboarding Telemetry Policies
Service Assurance in the Age of Virtualization
Multi-VIM/Cloud High Level Architecture
Orchestration and Controller Alignment for ONAP Release 1
Example Services Managed by OpenECOMP Demo
CLAMP Flows for vCPE Use Case in ONAP R1 Ron Shacham AT&T
Aligning Orchestration and Controller Per Merger Agreement Vimal Begwani – AT&T Jamil Chawki – Orange Alla Goldner -- Amdocs.
Defining ONAP VNF Package Model
Multi-VIM/Cloud High Level Architecture
Multi-VIM/Cloud High Level Architecture
Tina Tsou, Bryan Sullivan,
Aligning Orchestration and Controller Per Merger Agreement Vimal Begwani – AT&T Jamil Chawki – Orange Alla Goldner -- Amdocs.
Interface to External Controllers and SD-WAN Use Case
Alla Goldner (outcomes from brainstorming meetings) Sept, 2017
ARC: Definitions and requirements for SO/APP-C/VF-C discussion Chris Donley Date , 2017.
ARC 5: Deployment Options Chris Donley
MEF LSO Legato SDK 24 October 2017 Andy Mayer, Ph.D. Tara Cummings.
Multi-VIM/Cloud High Level Architecture
ONAP Run-time Catalog Project
ONAP Amsterdam Architecture
Beijing Release use cases/requirements for endorsement/approval
Enhanced Platform Awareness (EPA) Alex Vul Intel Corporation
Agenda Where we are (Amsterdam Architecture)
ONAP APIs Andrew Mayer, AT&T
Usecase 1 – Upgrade Image
ONAP Amsterdam Architecture
Casablanca Platform Enhancements to Support 5G Use Case (Network Deployment, Slicing, Network Optimization and Automation Framework) 5G Use Case Team.
Casablanca Platform Enhancements to Support 5G Use Case Architecture Review 5G Use Case Team June 26, 2018.
A road to network automation Christophe Closset Gervais-Martial Ngueko FOSDEM – Brussels, Feb. 3, 2018.
Documenting ONAP components (functional)
Multi-VIM/Cloud High Level Architecture
State of OPNFV MANO OPNFV MANO WG Report
Casablanca Platform Enhancements to Support 5G Use Case Summary of Planned Enhancement Areas 5G Use Case Team June 14, 2018.
20409A 7: Installing and Configuring System Center 2012 R2 Virtual Machine Manager Module 7 Installing and Configuring System Center 2012 R2 Virtual.
ONAP Beijing Architecture Chris Donley 1/9/18
Casablanca Platform Enhancements to Support 5G Use Case (Network Deployment, Slicing, Network Optimization and Automation Framework) 5G Use Case Team.
ONAP Service Assurance VES Spec 7
Casablanca Platform Enhancements to Support 5G Use Case (Network Deployment, Slicing, Network Optimization and Automation Framework) 5G Use Case Team.
Simplified Development Toolkit
Defining ONAP VNF Package Model
Casablanca Platform Enhancements to Support 5G Use Case (Network Deployment, Slicing, Network Optimization and Automation Framework) 5G Use Case Team.
FM Dictionary provided via VES Registraton Nokia September 14, 2018
ONAP Information Model Topics Timeline
Casablanca Platform Enhancements to Support 5G Use Case (Network Deployment, Slicing, Network Optimization and Automation Framework) 5G Use Case Team.
ONAP 5G USE CASE ENHANCEMENTS FOR PNF DEPLOYMENTS
Casablanca Platform Enhancements to Support 5G Use Case (Network Deployment, Slicing, Network Optimization and Automation Framework) 5G Use Case Team.
Technical Capabilities
Candidate for ONAP Dublin Implementation 5G RAN E2E Slice Design, Deploy and Manage 5G Use Case Team.
DCAE Data Files Collector
DCAE Data Files Collector
ONAP Service Assurance VES Spec 7
GNFC Architecture and Interfaces
ONAP Optimization Framework (OOF) POC for Physical CellID (PCI) Optimization July 30, 2018.
ONAP Architecture Overview Template
ONAP Architecture Principle Review
Presentation transcript:

ONAP Service Assurance Data Driven Flows July 5th, 2017 For Question Please Contact Alok Gupta +1 (732)-420-7007 ag1367@att.com © 2015 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.

VES (VNF Event Stream) Objective Enable significant reduction in effort to integrate VNF telemetry into automated VNF management systems Convergence to a common event stream format to simplify closed loop automation Enable Self Service onboarding thru VES Artifact for defining telemetry policy: Enable Driven Automation in DCAE Current Different interfaces and formats requiring customization (3 to 6 months development) Defined by vendors Varies by network functions and software releases Future Common predictable, flexible, reusable event format for all VFs => Closed Loop Automation Defined by AT&T based on conformance to standards Vendor agnostic and Configurable https://wiki.opnfv.org/display/VES

Project Scope & Deliverables VNF Event Stream Common Event Data Model Now on the 3rd major revision in OPNFV Further updates to be developed in ONAP VNF On-boarding Artifact (in YAML) YAML-based artifact defining VNF telemetry capabilities and needs Integration into the OPNFV platform as a monitoring framework Agent code from the Barometer project (collectd) ONAP VES library for integration with C-based agents (Java being worked) (e.g. VES demo agent) - https://gerrit.onap.org/r/gitweb?p=demo.git;a=tree;f=vnfs;hb=HEAD ONAP Collector and telemetry backend systems (e.g. database, message bus, closed- loop policy framework, dashboards)

VES – Common Event Data Model Common Header and Domain Specific Event Extensible for additional fields or domains Collector connection and data profile established at VM creation Connection/authentication /profile parameters injected into VM Data profile is fully controllable, to optimize telemetry overhead

VES Demo Leveraging ONAP demo VES Agent and Collector Demonstrating InfluxDB/Grafana backend Covering host, VM, and VNF status/stats Showing fault/stats correlation OpenStack Compute Host VDU1/2 VM JSON/REST VDU3 VM VDU4 VM VDU5 VM VES Collector InfluxDB Jumphost (TripleO) Tacker / Docker Terminal SSH etc Barometer Collectd Agent Host and VM (libvirt) stats: CPU, NIC, memory, … VES C Agent ONAP C Agent NGiNX / Web Server traffic Grafana vLB (iptables) vFW Traffic, status CPU, vNIC stats OpenStack Controller OpenStack Client API Nova-compute Neutron-gw etc VNF Event Streaming: Onboarding Telemetry Policies Copyright 2017 AT&T Intellectual Property. All rights reserved.

VES On-Boarding Artifact (One Document) To enable Self-Service, an on-boarding artifact can be provided by VNF Vendors, covering Which VES event Domains are supported by the VNF’s VES agents Optional fields supported, both in the body and as name/value extensions Enumeration of Fault events with recommended action to resolution Ranges and related Thresholding Crossing Alert/Actions for VNF Measurement fields Complex (multi-field correlated) Thresholding Crossing Alert/Actions Scale in/out recommendation based upon single or correlated fields Syslog Tag data with recommended actions All Artifacts at one place (ASDC), no need for AIDs, MIBS, NMTPs; Drives Automation

VES On-Boarding Artifact Use

Service Design (CLAMP) VES PoC Architecture SDC Reg YAML Service Design (CLAMP) Select VNF Trigger Policy Display generated policies Modify and Approve policies (Tech/Ops) Add policies to VNF blueprint Policy Pull VES Reg YAML by VNF Return policies to DCAE DS for display Final Policies (Respositry) VNF Onboarding catalog Blueprints DCAE Distribution Templates DCAE Controller DCAE Inventory Deploy Microservices & Distribute Policies Runtime Data Collection & Normalization Flows Policies are applied to named events within a Service-Vnf context P P P Correl MS Ticket MS TCA MS VNF Event Streaming: Onboarding Telemetry Policies Copyright 2017 AT&T Intellectual Property. All rights reserved.

VES SA Proposed E-t-E Architecture Create Policies from YAML Artifact Policy Hardening (from intent to detailed specification) Explore Data Storage Build Micro-Services that can be used by Policies Build Flows to Analyze Data and Take Action Data Store (influxDB) Grafana Service Design and Creation (SDC) Policy Apps Analytics Apps OpenStack Compute Host VDU1/2 VM JSON/REST VDU3 VM VDU4 VM Barometer Collectd Agent Host and VM (libvirt) stats: CPU, NIC, memory, … vMRF ONAP VPP vLB/vDNS ONAP VPP vFW DCAE Collector DCAE/App-C Controllers OpenStack Controller Nova-compute Neutron-gw etc VES C Agent ONAP vLB C Agent Traffic, status VPP stats ONAP vFW C Agent DMaaP VNF Event Streaming: Onboarding Telemetry Policies Copyright 2017 AT&T Intellectual Property. All rights reserved.

Backup Material © 2015 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.

Registration Registration Spec Sample Event 11 --- # registration for Heartbeat_vMRF event: {presence: required, structure: { commonEventHeader: {presence: required, structure: { domain: {presence: required, value: heartbeat}, eventName: {presence: required, value: Heartbeat_vMRF }, eventId: {presence: required}, nfNamingCode: {presence: required, value: mrfx}, priority: {presence: required, value: High}, reportingEntityName: {presence: required}, sequence: {presence: required}, sourceName: {presence: required}, startEpochMicrosec: {presence: required}, lastEpochMicrosec: {presence: required}, version: {presence: required, value: 3.0} }}, heartbeatFields: {presence: optional, structure:{ heartbeatFieldsVersion: {presence: required, value: 1.0}, heartbeatInterval: {presence: required, range: [ 0, 600 ], default: 60 } }} ... { "event": { "commonEventHeader": { “domain”: “heartbeat”, "eventName": "Heartbeat_vMRF", "eventId": "ab305d54-85b4-a31b-7db2-fb6b9e546015", “nfNamingCode”: “mrfx”, "priority": "Normal", “reportingEntityId”: “cc305d54-75b4-431b-adb2-eb6b9e541234”, “reportingEntityName”: “MegaMRFVf”, "sequence": 0, "sourceId": "de305d54-75b4-431b-adb2-eb6b9e546014", “sourceName”: “MegaMRF”, “startEpochMicrosec”: 1413378172000000, “lastEpochMicrosec”: 1413378172000000, “version”: 3.0 } 11 VNF Event Streaming: Onboarding Telemetry Policies Copyright 2017 AT&T Intellectual Property. All rights reserved.

Registering EventType: Fault_vMRF_InvalidLicense Registration Spec Sample Event { "event": { "commonEventHeader": { “domain”: “fault”, “eventName”: “Fault_vSCF_InvalidLicense”, "eventId": "ab305d54-85b4-a31b-7db2-fb6b9e546015", “nfNamingCode”: “mrfx”, "priority": "High", “reportingEntityId”: “cc305d54-75b4-431b-adb2-eb6b9e541234”, “reportingEntityName”: “MegaMRFVf”, "sequence": 0, "sourceId": "de305d54-75b4-431b-adb2-eb6b9e546014", “sourceName”: “MegaMRF”, “startEpochMicrosec”: 1413378172000000, “lastEpochMicrosec”: 1413378172000000, “version”: 3.0 }, "faultFields": { “faultFieldsVersion”: 1.2 "alarmCondition": “Invalid license key", "eventSourceType": "virtualNetworkFunction", "specificProblem": "The node license key is invalid" “eventSeverity": "CRITICAL", “vfStatus”: “Active”, “alarmAdditionalInformation”: [ “name”: “license_key”, “value”: “1000” } ] --- # registration for Fault_vMRF_InvalidLicense event:{ presence: required, action: [any, any, invalidLicense, RECO-renewLicence], structure: { commonEventHeader: {presence: required, structure: { domain: {presence: required, value: fault}, eventName: {presence: required, value: Fault_vMRF_InvalidLicense}, eventId: {presence: required}, nfNamingCode: {presence: required, value: mrfx}, priority: {presence: required, value: High}, reportingEntityName: {presence: required}, sequence: {presence: required}, sourceName: {presence: required}, startEpochMicrosec: {presence: required}, lastEpochMicrosec: {presence: required}, version: {presence: required, value: 3.0} }}, faultFields: {presence: required, structure: { faultFieldsVersion: {presence: required, value: 1.2}, alarmCondition: {presence: required, value: "Invalid license key"}, eventSourceType: {presence: required, value: virtualNetworkFunction}, specificProblem: {presence: required, value: "The node license key is invalid"}, eventSeverity: {presence: required, value: CRITICAL}, vfStatus: {presence: required, value: Active}, alarmAdditionalInformation: {presence: required, array: [ field: {presence: required, structure: { name: {presence: required, value: license_key}, value: {presence: required} }} ]} ... 12 VNF Event Streaming: Onboarding Telemetry Policies Copyright 2017 AT&T Intellectual Property. All rights reserved.

Registering EventType: MFVS vMRF --- memoryUsageArray: {presence: required, array: { # registration for Mfvs_vMRF memoryUsage: {presence: required, structure: { event: {presence: required, structure: { vmIdentifier: {presence: required}, commonEventHeader: {presence: required, structure: { memoryFree: {presence: required, range: [ 0, 100 ], action: [ domain: {presence: required, value: measurementsForVfScaling}, 100, down, FreeMemLow, RECO-scaleOut, eventName: {presence: required, value: Mfvs_vMRF}, Tca_vMRF_LowFreeMemory ], action: [1000, up, FreeMemHigh, eventId: {presence: required}, RECO-scaleIn, Tca_vMRF_HighFreeMemory nfType: {presence: required, value: mrfx}, ]}, priority: {presence: required, value: Normal}, memoryUsed: {presence: required} reportingEntityName: {presence: required}, sequence: {presence: required}, sourceName: {presence: required}, numberOfMediaPortsInUse: {presence: required, range: [ 1, 300 ] }, startEpochMicrosec: {presence: required}, additionalMeasurements: {presence: required, array: [ lastEpochMicrosec: {presence: required}, measurementGroup: {presence: required, structure: { version: {presence: required, value: 3.0} name: {presence: required, value: licenseUsage}, }}, measurements: {presence: required, array: [ measurementsForVfScalingFields: {presence: required, structure: { field: {presence: required, structure: { measurementsForVfSclaingFieldsVersion: {presence: required, value: 2.0}, name: {presence: required, value: [ G711AudioPort, measurementInterval: {presence: required, range: [ 60, 1200 ], default: 180 }, G729AudioPort, G722AudioPort, AMRAudioPort, concurrentSessions: {presence: required}, AMRWBAudioPort, OpusAudioPort, H263VideoPort, cpuUsageArray: {presence: required, array: { H264NonHCVideoPort, H264HCVideoPort, MPEG4VideoPort, cpuUsage: {presence: required, structure: { NP8NonHCVideoPort, VP8HCVideoPort, PLC, NR, NG, NLD, cpuIdentifier: {presence: required}, G711FaxPort, T38FaxPort, RFactor, T140TextPort ] }, percentUsage: {presence: required, range: [ 0, 100 ], action: [ value: {presence: required} 90, up, CpuUsageHigh, RECO-scaleOut, Tca_vMRF_HighCpuUsage ], action: [25, down, CpuUsageLow, RECO-scaleIn, Tca_vMRF_LowCpuUsage ]} }} ... 13 VNF Event Streaming: Onboarding Telemetry Policies Copyright 2017 AT&T Intellectual Property. All rights reserved.

Registering EventType: Complex TCAs --- # Rules Rules: [ rule: { trigger: CpuUsageHigh && FreeMemLow, microservices: [scaleOut] # Note: this presumes there is a scaleOut microservice alerts: [Tca_vMRF_OutOfResources] # Note: this TCA should be defined in the YAML }, rule: { trigger: CpuUsageLow && FreeMemHigh, microservices: [scaleIn] # Note: this presumes there is a scaleIn microservice } ] ... 14 VNF Event Streaming: Onboarding Telemetry Policies Copyright 2017 AT&T Intellectual Property. All rights reserved.

Registering EventType: syslogs vMRF # registration for Syslog_vMRF # log all, restart if tag = Out_of_Memory event: {presence: required, action: [any, any, null, RECO-log] structure: {     commonEventHeader: {presence: required, structure: {         domain: {presence: required, value: syslog},         eventName: {presence: required, value: Syslog_vMRF},         eventId: {presence: required},         nfNamingCode: {presence: required, value: mrfx},         priority: {presence: required, value: Normal},         reportingEntityName: {presence: required},         sequence: {presence: required},         sourceName: {presence: required},         startEpochMicrosec: {presence: required},         lastEpochMicrosec: {presence: required},         version: {presence: required, value: 3.0}     }},         syslogFields: {presence: required, structure: {         eventSourceHost: {presence: required},         eventSourceType: {presence: required, value: virtualNetworkFunction},         syslogFacility: {presence: required, range: [0, 23]},         syslogFieldsVersion: {presence: required, value: 3.0},         syslogMsg: {presence: required},         syslogPri: {presence: required, range: [0, 192]},         syslogProc: {presence: required, range: [0, 65536]},         syslogSData: {},         syslogSdId: {},         syslogSev: {presence: required, range : [0-7]},         syslogTag: {presence: required, action: [“Out_of_Memory”,at,null,reco-restart]},         syslogVer: {presence: required, value 0}     }} }} ... 15 VNF Event Streaming: Onboarding Telemetry Policies Copyright 2017 AT&T Intellectual Property. All rights reserved.

ECOMP Vendor Event Listener code on Github and ONAP Gerrit Hosted in the ONAP github site: https://gerrit.onap.org/r/gitweb?p=demo.git;a=tree;f=vnfs;hb=HEAD VES Documentation https://github.com/att/evel-test-collector/tree/master/docs/att_interface_definition VES EVEL Demo:  https://github.com/att/evel-library/tree/master/code/evel_demo VES You tube Video from June 15, 2017 OPNFV, Beijing: https://www.youtube.com/watch?v=Zoxcj4mwUwU

Summary AT&T Requesting VNF Vendors to provide Fault, Measurement and Syslog as per the definition in the following AID* (includes JSON Schema): AT&T has it’s Event Library (Agent and Collector Code) available for VNF Vendors that can be used for integration with their VNF to VES events: Following are the Yaml On-boarding files for vFW and vMRF The demo files can be found at: https://gerrit.onap.org/r/gitweb?p=demo.git;a=tree;f=vnfs;hb=HEAD * The AID assumes that Vendors will support AT&T VNF naming convention. AT&T Proprietary (Internal Use Only). Not for use or disclosure outside the AT&T companies except under written agreement.