1. © 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 Streaming (VES) Project Proposal April 22 nd, 2016 For Questions, Please contact: Alok Gupta +1 732-420-7007; ag1367@att.com

2. Proposal  Background  Telemetry data formats and semantics / expected actions by management systems vary widely  For Fault Events, vendors use SNMP, 3GPP Corba, MTOSI, OSSJ etc, and semantics can differ (e.g. Critical Severity as “1” or “5”)  For Measurement events (KPI/KCI), vendors deliver CSV or XML based files, with varying internal data formats.  This variance complicates NF integration into management systems  Scope/Deliverables  A VNF Event Stream (VES) Common Event Data Model  Consisting of a Header and an Event Specific Block, with additional Name/Value fields for extensibility  OPNFV support for the VES Common Event Data Model  A VES Agent that can collect the VNF Event Stream data from the VNF and deliver it to the VES Collector  A VES Collector that can consume the VNF Event Stream data, and store the data in a database backend  VES plugins for integration with OpenStack infrastructure services such as Monasca and Vitrage  Documentation and test support (e.g. reference event data)  A plan for upstreaming the project code VES Project Proposal 2 Objective  Enable significant reduction in effort to develop and integrate VNF telemetry-related data into automated VNF management systems, by promoting convergence to a common event stream format and collection system. © 2015 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.

3. AT&T Proprietary (Internal Use Only). Not for use or disclosure outside the AT&T companies except under written agreement. 3 Problem Statement / Fault Management (FM) Interface Comparison Categories SNMP3GPP CorbaMTOSI via JMS MTOSI via REST over HTTPS (JSON) General Attributes - There are 3 current version of SNMP. - Devices are not compliant in all 3 versions. - SNMP V3 handling requires special adapter due to increased security - SNMP is connectionless, except for SNMPv3 - No assurance of delivery - No resynch functionality - Corba is connection oriented - assurance of delivery - resynch functionality - Corba has sets of actions - Corba payload provides more details in less traffic volume - JMS is Connection oriented - assurance of delivery - resynch functionality - MOTSI has a sets of actions - MTOSI payload provides more details in less traffic volume -service providing organized access to stateless resources -connectionless -stateless Availability Agents and processes are widely available Reasonable SupportMixed Reuseability LowHigh Exapndability LowHigh Authenticaltion-Security SNMP V3 over SSLHigh-SecurityIRPHigh - SSLHigh – SSL Platform Dependency Dependent Independent SOA Interface and Data event NoYes Implementation Vendor DependedntVendor Independent CLI Command Standard Payload HighConstantconstantConstant Multiple Device Support NoYes Multi-Vendor Support NoYes Sensititivity to new Alarm Data HighLow point-to-Point/Multipoint p-t-p deploy muiltple pub-sub to avoid bottleneckPub-Sub latency <1ms<10ms Server/Code deployment DifficultJava drivenIndependent interfacing to diffenet Apps DifficultEasy Output SNMP3GPPXML/JSON Cost of Wonership adapter 4972 line of codes 5000006500800 Equipment Type Supported 50205 © 2015 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.

4.  Common Event Data Model: Fault, Heartbeat, Performance, Syslogs, Other, Usage, Signaling, Security, others  Common Header and Domain Specific Event  Additional name value pair fields for extensibility  Profile Driven Event Data Needed at time of VNF Instantiated and Data Profile Support to change event streaming by VNF and Collector/Listner:  Collector Address: IP, Port  Authentication Data: User Name/Password  Data Profile: Event Type (Fault (Custom (Full, c1, c2..) or Programmable)) VES – Common Event Data Model - Dynamic Pre-Defined: No API Overhead Defined Real Time via API

5. VES and Other OPNFV Projects 5  VES is a standardized event framework that can be used by Open Stack, OPNFV projects  OPNFV projects that potentially benefit from the VES project  Fault Management (Doctor) Fault Management (Doctor)  Virtualized Infrastructure Deployment Policies (Copper) Virtualized Infrastructure Deployment Policies (Copper)  High Availability for OPNFV (Availability) High Availability for OPNFV (Availability)  Data Collection for Failure Prediction (Prediction) Data Collection for Failure Prediction (Prediction)  Audit (Inspector) Audit (Inspector)  Fault localization (RCA, Pinpoint ) Fault localization (RCA, Pinpoint )  Service Function Chaining (sfc) Service Function Chaining (sfc)  Moon Security Management Moon Security Management  OpenStack projects that potentially benefit from the VES project  Monasca: a monitoring-agent plugin for VES can provide a new/converged source for Monasca events Monasca  Vitrage: similar to Monasca can provide new data for the Graph DB of Vitrage Vitrage  Congress: Congress data source drivers can integrate additional data from Monasca, Vitrage, or directly Congress © 2015 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.

6. 1.Use cases that illustrate the value, reuse and increased efficiency/cost reduction 2.Software code behind: Library Capabilities Demo – Reference VNF – Event Library Integration AT&T’s Operational Experience using the Proposed Framework © 2015 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property. 6

7. In scope: Green/solid interfaces Agent/Collector interface support library and reference implementation OpenStack component plugins Agent code is embedded in VNFCs, Virtualization Hosts, and Bare Metal Hosts Agents / VNFCs can also deliver directly to OpenStack Plugins (not shown) VES Architectural View © 2015 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property. 7 OpenStack Application Controller SDNC Bare Metal Host Virtualization Host(s) VES Collector VES Agent VNFC VES Agent Plugins Monasca Vitrage Congress etc Event stream is controlled by and sent to collector (e.g. ECOMP DCAE) Collector can forward to OpenStack Plugins

8.  Use Case  Results  Once development is done for the first VNF, the subsequent VNF can be supported via Configuration changes and/or Policy Identification and Enforcement, resulting in over 80% cost and time savings Use Case and Results 8 Collector Event Processor Correlation Policy Enforcement/ Automation Data Bus Fault Event / Clear Ticketing System Scenario 3: High CPU Utilization Published an event for MSO to create a New VF Scenario 2: Payload Processor Failure Publish an event to Restart VM Scenario 1: False Alarm Scenario 2: VM Failure Scenario 3: Scaling Alert Scenario 1: Failure Event, Notification PM (Threshold Crossing Alert) Ticket Generated, Updated and Closed © 2015 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.

9. 9 Thank You