Page tree
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Project Name:

  • Proposed name for the project: VNF Event Stream (VES)
  • Proposed name for the repository: ves

Project description:

Objective:

This project will develop OPNFV platform support for VNF event streams, in a common model and format intended for use by NFV Service Providers (SPs), e.g. in managing VNF health and lifecycle. The project’s goal is to enable a significant reduction in the effort to develop and integrate VNF telemetry-related data into automated VNF management systems, by promoting convergence toward a common event stream format and collection system.

Powerpoint intro to the project: OPNVF VES.pptx

Background

In a typical Service Assurance (SA) Environment, the VNF Provider defines and provides the format and protocol for sending telemetry data to SPs responsible for managing VNF health and lifecycle. The standards for telemetry data come in many varieties and for each particular standard, the expected actions also differ from one VNF to another. As an example:

  • Fault Events can be conveyed via SNMP, 3GPP Corba, MTOSI, OSSJ etc. For each standard the actions can differ from one VNF to another (e.g. Critical Severity can be marked as 1 in one implementation, 5 for another).
  • For Measurement events, related to Key Performance Indicators (KPI)/Key Capacity Indicator (KCI), they can be in Comma Separated files (CSV) or XML. Within these file formats, events vary across implementations.

The result of a multitude of standards is that every time a new VNF or a new VNF release is introduced, implementer choice can require SPs to make changes to their SA support system that manages the VNFs. This results not only in added costs for SPs, but also in deployment delays.

Recommendations Summary:

We are recommending a Common Event Data Model:

  • A VNF Event Stream (VES) Common Data Model consisting of a Header and an Event Specific Block (Domain is specified in the header).
  • Additional name/value fields for extensibility.

Use of Restful API using JSON with Common Event Format for Telemetry Data (detailed definitions for Heartbeat. Fault, Measurements (KPI/KCI), Syslogs, Mobile Flow and with extensibility to others, i.e. Usage, Security, Signaling etc.).

Scope:

The project will develop and integrate into the OPNFV platform:

  • A Common Event Data Model (“VNF Event Stream”)
  • OPNFV platform support the VNF Event Stream, including:
    • 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
  • A plan for upstreaming the project code

As input this project, AT&T will contribute a proposed specification and implementation of the VNF Event Stream framework developed for AT&T’s ECOMP (Enhanced Control, Orchestration, Management and Policy) platform, and described as part of the “Analytic Framework” support in the ECOMP white paper available at http://att.com/ecomp.

The following diagram illustrates the concept for the VES architecture and scope:

Testability:

The project will support testability through:

  • VES collector support under all OPNFV base system installers, either as a base system deploy component or post-deploy installed components
  • Test cases to be supported through Functest and DoveTail
  • Reference VNF generating events, for lab testing per the event definitions

Documentation:

The project will produce:

  • Detailed step by step documentation for developing to and using the code and event specification.
  • Blueprint proposals for upstreaming the event library, collector, and specification.

Dependencies:

VES is a standardized event framework that can be used by OpenStack and OPNFV projects.

OPNFV projects that potentially benefit from the VES project:

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
  • Vitrage: similar to Monasca can provide new data for the Graph DB of Vitrage
  • Congress: Congress data source drivers can integrate additional data from Monasca, Vitrage, or directly

Committers and Contributors:

Committers:

  • Alok Gupta, AT&T

Contributors:

  •  

Planned deliverables:

The project will deliver specifications and code as described in the scope section, and supporting information:

  • Reference VNF generating events, for lab testing per the event definitions.
  • Detailed step by step documentation for developing to and using the code and event specification.
  • Blueprint proposals for upstreaming the event library, collector, and specification.

Proposed Release Schedule:

VES is targeted for the 4th OPNFV release (“D” river). For the Colorado release, an initial reference implementation will be developed and made available for testing on the OPNFV Colorado release platform, as well as by VNF implementers.

Key Project Facts:

Project Name: VNF Event Stream (VES)
Repo name: VES
Lifecycle State: Incubation
Primary Contact: Alok Gupta, AT&T
Project Lead: Alok Gupta, AT&T
Jira Project Name: VNF Event Stream
Jira Project Prefix: VES
mailing list tag: VES
Committers:

  • Alok Gupta, AT&T

 

  • No labels