Wiki

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
**OPNFV Project Proposal – Software Fastpath Service Quality Metrics**
Version: 1.3 (December 11th, 2014)

**Project Name:
**Software Fastpath Service Quality Metrics

**Proposed name for the repository:** fastpathmetrics


**Project Categories: **  
  * Collaborative development

**Project description: 
**
The OPNFV platform (NFVI) requires functionality to:

  * Create a low latency, high performance packet processing path (fast path) through the NFVI that VNFs can take advantage of;
  * Measure Telco Traffic and Performance KPIs through that fast path;
  * Detect and report violations that can be consumed by VNFs and higher level EMS/OSS systems

This project is focused on the development of utilities and libraries to support the above. An ability to measure and enforce Traffic Quality KPI’s (Service Assurance) in the data-plane will be mandatory for any Telco-grade NFVI Implementation, regardless of whether the data plane is implemented in hardware or software.  

Examples of local measurable QoS factors for Traffic Monitoring which impact both Quality of Experience and 5’9s availability would be (using Metro Ethernet Forum Guidelines as reference):

  * Packet loss
  * Packet Delay Variation
  * Uni-directional frame delay

Other KPIs such as Call drops, Call Setup Success Rate, Call Setup time etc. are measured by the VNF.

In addition to Traffic Monitoring, the NFVI must also support Performance Monitoring of the physical interfaces themselves (e.g. NICs), i.e. an ability to monitor and trace errors on the physical interfaces and report them.

All these traffic statistics for Traffic and Performance Monitoring must be measured in-service and must be capable of being reported by standard Telco mechanisms (e.g. SNMP traps), for potential enforcement actions.

**Scope:
**

The output of the project will provide interfaces and functions to support monitoring of Packet Latency and Network Interfaces while the VNF is in service.

The DPDK interface/API will be updated to support:

  - Exposure of NIC MAC/PHY Level Counters
  - Interface for Time stamp on RX
  - Interface for Time stamp on TX

Specific testing and integration will be carried out to cover:

  * Unit/Integration Test plans:  A sample application provided to demonstrate packet latency monitoring and interface monitoring

The following list of features and functionality will be developed:

  - DPDK APIs and functions for latency and interface monitoring
  - A sample application to demonstrate usage

The scope of the project is limited to the DPDK APIs and a sample application to demonstrate usage.
{{:collaborative_development_projects:telcokpis_update.png|}}



















































Fig 1: Architecture overview (showing provided functionality in green)

In the diagram above, the interfaces 1, 2, 3 are implemented along with a sample application.  The                      sample application will support monitoring of NIC counters/status and will also support             measurement of packet latency using DPDK provided interfaces.

VNF specific processing, Traffic Monitoring, Performance Monitoring and Management Agent are out of scope. The scope is limited to Intel 10G Niantic support. 

The Proposed MAC/PHY Interface Counters include:

  * Packet RX
  * Packet TX
  * Packet loss
  * Interface errors + other stats


The Proposed Packet Latency Monitor include:

  * Cycle accurate ‘stamping’ on ingress
  * Supports latency measurements on egress


Support for additional types of Network Interfaces can be added in the future.

Support for failover of DPDK enabled cores is also out of scope of the current proposal. However, this is an important requirement and must-have functionality for any DPDK enabled framework in the NFVI. To that end, a second phase of this project will be to implement DPDK “Keep Alive” functionality that would address this and would report to a VNF-level Failover and High Availability mechanism that would then determine what actions, including failover, may be triggered.


**Consumption Models:
**

Fig 1. above shows how a sample application will be provided to demonstrate usage. In reality many VNFs will have an existing performance or traffic monitoring utility used to monitor VNF behavior and report statistics, counters, etc.

To consume the performance and traffic related information provided within the scope of this project should in most cases be a logical extension of any existing VNF performance or traffic monitoring utility, in most cases it should not require a new utility to be developed. We do not see the Software Fastpath Service Quality Metrics data as major additional effort for VNFs to consume, this project would be sympathetic to existing VNF architecture constructs. The intention is that this project represents a lower level interface for network interface monitoring to be used by higher level fault management entities (see below).

Allowing the Software Fastpath Service Quality Metrics data to be handled within existing VNF performance or traffic monitoring utilities also makes it simpler for overall interfacing with higher level management components in the VIM, MANO and OSS/BSS. The Software Fastpath Service Quality Metrics proposal would be complementary to the Fault Management and Maintenance project proposal (“Doctor”) which is also in flight, which addresses NFVI Fault Management support in the VIM. To that end, the project committers and contributors for the Software Fastpath Service Quality Metrics project wish to work in sync with the “Doctor” project – to facilitate this, one of the “Doctor” contributors has also been added as a contributor to the Software Fastpath Service Quality Metrics project.


**Testability:** (optional, Project Categories: Integration & Testing)

Scalability: 2x10g Interface support

Tests: Traffic patterns include small packets (64 bytes) and average packet sizes of 200bytes.


**Documentation: 
**
  * Functional Architecture Specification
  * Release Notes
  * Programming Guide
  * API Reference Guide
  * Sample Application User Guide

**Dependencies:
**
  * There are currently no similar projects underway or proposed in either OPNFV or in an upstream project.
  * The relevant upstream project for this contribution is www.dpdk.org  and the aim is to intersect DPDK R2.0 with contribution patches including this functionality. DPDK R2.0 is provisionally planned for end March 2015. 
  * In terms of external fora or standard development organization dependencies to the project, there are no hard dependencies. The functionality developed by the project is designed to be consumed by existing northbound interfaces and implementations.
  * For the integration and test requirements, there is a dependency towards IA server Hardware and NICs being available to the committers.

**Committers and Contributors:
**

  * Committers: Thomas Monjalon: Thomas.monjalon@6wind.com; Bruce Richardson: Bruce.richardson@intel.com; Maryam Tahhan: maryam.tahhan@intel.com; Christoph Meyer :christoph.meyer@ericsson.com 
  * Other contributors: John Browne: john.j.browne@intel.com; Mike Lynch: Michael.a.lynch@intel.com; Jarmo Virtanen: jarmo.virtanen@nsn.com; Aihua Li: aihuali@huawei.com

**Planned Deliverables:
**
  * The project release package will be an upstream contribution into the www.dpdk.org code base for consumption by OPNFV
  * There will be the following updates to dpdk.org collateral to support the contribution:
    - Updates to DPDK R2.0 Release Notes
    - Updates to DPDK R2.0 Programming Guide
    - Updates to DPDK R2.0 API Reference Guide
    - Updates to DPDK R2.0 Sample Applications User Guide


**Proposed Release Schedule:
**
  * The first release of this functionality is planned to align with DPDK 2.0 in March 2015, which should align with OPNFV R1.0 timeframe of 1H 2015.
Wiki

User Tools

Site Tools

Page Tools
