User Tools

Site Tools


collaborative_development_projects:opnfv_telco_kpis

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
collaborative_development_projects:opnfv_telco_kpis [2014/11/06 11:58]
Christopher Price
collaborative_development_projects:opnfv_telco_kpis [2014/11/06 12:04] (current)
Christopher Price
Line 5: Line 5:
   * Project Categories: Requirements,​ Collaborative Development,​ Documentation,​ Integration & Testing   * Project Categories: Requirements,​ Collaborative Development,​ Documentation,​ Integration & Testing
  
-===== Project description: ​=====+==== Project description:​ ====
    
 The OPNFV platform (NFVI) requires functionality to: The OPNFV platform (NFVI) requires functionality to:
Line 22: Line 22:
 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. 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: ​====
- +
-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 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: The DPDK interface/​API will be updated to support:
-1. Exposure of NIC MAC/PHY Level Counters +  - Exposure of NIC MAC/PHY Level Counters 
-2. Interface for Time stamp on RX +  ​- ​Interface for Time stamp on RX 
-3. Interface for Time stamp on TX+  ​- ​Interface for Time stamp on TX
  
-       Specific testing and integration will be carried out to cover: +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 +  ​* ​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. +The following list of features and functionality will be developed. 
-1. DPDK APIs and functions for latency and interface monitoring +  ​- ​DPDK APIs and functions for latency and interface monitoring 
-2. A sample application to demonstrate usage+  ​- ​A sample application to demonstrate usage
         ​         ​
 The scope of the project is limited to the DPDK APIs and a sample application to demonstrate usage. The scope of the project is limited to the DPDK APIs and a sample application to demonstrate usage.
  
-In the diagram below, 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.+In the diagram below, 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: 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 RX 
-Packet TX +  ​* ​Packet TX 
-Packet loss +  ​* ​Packet loss 
-Interface errors + other stats+  ​* ​Interface errors + other stats
  
 The Proposed Packet Latency Monitor include: The Proposed Packet Latency Monitor include:
-Cycle accurate ‘stamping’ on ingress +  * Cycle accurate ‘stamping’ on ingress 
-Supports latency measurements on egress+  ​* ​Supports latency measurements on egress
  
    
-{{:​collaborative_development_projects:​opnfvtelcokpis.png?​200|}}+{{:​collaborative_development_projects:​opnfvtelcokpis.png?​600|}}
 Fig 1: Architecture overview Fig 1: Architecture overview
  
Line 61: Line 59:
 Support for additional types of Network Interfaces can be added in the future. Support for additional types of Network Interfaces can be added in the future.
  
-Testability:​ (optional, Project Categories: Integration & Testing)+=== Testability:​ (optional, Project Categories: Integration & Testing) ​===
  
 Scalability:​ 2x10g Interface support Scalability:​ 2x10g Interface support
 Tests: Traffic patterns include small packets (64 bytes) and average packet sizes of 200bytes. Tests: Traffic patterns include small packets (64 bytes) and average packet sizes of 200bytes.
 +There will be a specific testing resource assigned to the project
 +
 +==== Documentation:​ ====
 + 
 +  * Functional Architecture Specification
 +  * Release Notes
 +  * Programming Guide
 +  * API Reference Guide
 +  * Sample Application User Guide
  
-              There will be a specific testing resource assigned to the project 
  
-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.
  
-Dependencies+==== Committers and Contributors==== 
-• There are currently no similar projects underway or proposed in either OPNFV or in an upstream project+  * Maintainers:​ Thomas Monjalon, www.dpdk.org maintainer; email: Thomas.monjalon@6wind.com ​ 
-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.  +  * Committers: Bruce Richardson: Bruce.richardson@intel.com;​ Maryam Tahhan: maryam.tahhan@intel.com  
-• 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+  * Other contributors:​ John Browne: john.j.browne@intel.com;​ Mike Lynch: Michael.a.lynch@intel.com;​  
-• For the integration and test requirements,​ there is a dependency towards IA server Hardware and NICs being available ​to the committers.+  * Planned deliverables:​ 
 +  * The project ​release package will be an upstream ​contribution ​into www.dpdk.org ​ 
 +  * 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
  
-Committers and Contributors:​ +==== Proposed Release Schedule: ​==== 
-• Maintainers:​ Thomas Monjalon, www.dpdk.org maintainer; email: Thomas.monjalon@6wind.com  +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 201
-• Committers:​ Bruce Richardson: Bruce.richardson@intel.com;​ Maryam Tahhan: maryam.tahhan@intel.com  +
-• Other contributors:​ John Browne: john.j.browne@intel.com;​ Mike Lynch: Michael.a.lynch@intel.com;​  +
-Planned deliverables:​ +
-• The project release package will be an upstream contribution into www.dpdk.org  +
-• There will be the following updates to dpdk.org collateral to support the contribution:​ +
-o Updates to DPDK R2.0 Release Notes +
-o Updates to DPDK R2.0 Programming Guide +
-o Updates to DPDK R2.0 API Reference Guide +
-o 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 201+
  
collaborative_development_projects/opnfv_telco_kpis.1415275128.txt.gz · Last modified: 2014/11/06 11:58 by Christopher Price