• Project Name: Bottlenecks
  
• Project Repository: bottlenecks
  
• Project Category: Integration & Testing
  
• Project IRC: #opnfv-bottlenecks
  
• Team meeting page
  

This project aims to find system bottlenecks by testing and verifying OPNFV infrastructure in a staging environment before committing it to a production environment. Instead of debugging a deployment in production environment, an automatic method for executing benchmarks which plans to validate the deployment during staging is adopted. This project will provide a framework to find the bottlenecks of OPNFV infrastructure. The framework has four components，Workload generator and VNFs (WV), Monitor and Analysis (MA), Deployment and Configuration (DC), Automated Staging (AS), as shown below.

• Workload generator and VNFs: workload generator generates workloads which go through VNFs
• Monitor and Analysis: monitor VNFs status and infrastructure status to output analyzed results
• Deployment and Configuration: deploy and configure infrastructure and WV
• Automated Staging: implement automated staging

The scope of Release Engineering project includes:

• Forming a staging test framework

1. Release candidates A,B… provides a foundation to be tested of Infrastructure layer
2. A workload generator generates workloads which go through VNFs. This workload generator will be scalable and may cover multiply workload models for different scenarios
3. Monitor and analysis units will monitor the infrastructure and VNFs status and present results after analysis

• Automatically generating the full set of experimental specification

1. Document and codes to describe how to generate experimental specification according to different service level agreement (SLA)
2. Document to describe how to find some typical bottlenecks according to specific monitoring

• Measuring the performance of standard benchmarks over a wide range of hardware and software configurations

1. Different hardware resource adopted to produce test data used for bottleneck analysis
2. Different parameters adopted in software configuration files to produce test data used for bottleneck analysis

• Automated iterative staging process for finding bottlenecks

1. Achieve full automation in system deployment, evaluation, and evolution, by creating code generation tools to link the different steps of deployment, evaluation, reconfiguration, and redesign in full lifecycle.
2. Reassignment and reconfiguration of hardware resources
3. Reassignment and reconfiguration of software resource

Presentation

bottlenecks.pdf

meeting materials

bottlenecks_project_for_test_meeting_20150820.pptx

Please see the Bottlenecks Project Proposal for more details.

Meeting details:

Goto Meeting :

• Meeting ID: https://global.gotomeeting.com/join/882532573

IRC meeting :

• freenode.net #opnfv-bottlenecks (http://webchat.freenode.net/?channels=opnfv-bottlenecks)
• Every Thursdays UTC 1:00-2:00, Beijing Time 9:00-10:00

meeting agenda and logs

• https://wiki.opnfv.org/meetings/bottlenecks

IRC :

• freenode.net #opnfv-bottlenecks (http://webchat.freenode.net/?channels=opnfv-bottlenecks)
  

etherpad for version plan :

• https://etherpad.opnfv.org/p/bottlenecks
  

Lynch Michael A(Intel): michael.a.lynch@intel.com
Qi Liang: liangqi1@huawei.com
Mingjiang Li: limingjiang@huawei.com
Lingli Deng: denglingli@chinamobile.com