This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
bottlenecks [2015/12/23 09:03] panghao |
bottlenecks [2016/03/23 03:41] (current) hongbo tian [Contributors] |
||
---|---|---|---|
Line 5: | Line 5: | ||
* Project Category: Integration & Testing \\ | * Project Category: Integration & Testing \\ | ||
* Project IRC: #opnfv-bottlenecks \\ | * Project IRC: #opnfv-bottlenecks \\ | ||
- | * [[meetings/bottlenecks|Team meeting page]] \\ | + | * Project Meetings: [[meetings/bottlenecks|Working meeting page]] |
^ {{:information.png?60|}} ^ **Quick links** \\ [[https://jira.opnfv.org/projects/BOTTLENECK/issues|Bottlenecks Jira tasks]] \\ [[bottlenecks#documentation|Bottlenecks documentation]] ^ | ^ {{:information.png?60|}} ^ **Quick links** \\ [[https://jira.opnfv.org/projects/BOTTLENECK/issues|Bottlenecks Jira tasks]] \\ [[bottlenecks#documentation|Bottlenecks documentation]] ^ | ||
Line 44: | Line 44: | ||
* **Project proposal:** [[project_proposals:bottlenecks|Bottlenecks Project Proposal]] | * **Project proposal:** [[project_proposals:bottlenecks|Bottlenecks Project Proposal]] | ||
- | The scope of Release Engineering project includes: | + | ===== Scope ===== |
- | *Forming a staging test framework | + | The scope of Bottlenecks project includes: |
- | - Release candidates A,B... provides a foundation to be tested of Infrastructure layer | + | |
- | - A workload generator generates workloads which go through VNFs. This workload generator will be scalable and may cover multiply workload models for different scenarios | + | |
- | - Monitor and analysis units will monitor the infrastructure and VNFs status and present results after analysis | + | |
- | *Automatically generating the full set of experimental specification | + | |
- | - Document and codes to describe how to generate experimental specification according to different service level agreement (SLA) | + | |
- | - 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 | + | |
- | - Different hardware resource adopted to produce test data used for bottleneck analysis | + | |
- | - Different parameters adopted in software configuration files to produce test data used for bottleneck analysis | + | |
- | *Automated iterative staging process for finding bottlenecks | + | |
- | - 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. | + | |
- | - Reassignment and reconfiguration of hardware resources | + | |
- | - Reassignment and reconfiguration of software resource | + | |
- | Presentation | + | * **Forming a staging test framework** |
+ | - Release candidates A,B... provides a foundation to be tested of Infrastructure layer | ||
+ | - A workload generator generates workloads which go through VNFs. This workload generator will be scalable and may cover multiply workload models for different scenarios | ||
+ | - Monitor and analysis units will monitor the infrastructure and VNFs status and present results after analysis | ||
- | {{:undefined:bottlenecks.pdf|}} | + | * **Automatically generating the full set of experimental specification** |
+ | - Document and codes to describe how to generate experimental specification according to different service level agreement (SLA) | ||
+ | - Document to describe how to find some typical bottlenecks according to specific monitoring | ||
- | meeting materials | + | * **Measuring the performance of standard benchmarks over a wide range of hardware and software configurations** |
+ | - Different hardware resource adopted to produce test data used for bottleneck analysis | ||
+ | - Different parameters adopted in software configuration files to produce test data used for bottleneck analysis | ||
- | {{:bottlenecks_project_for_test_meeting_20150820.pptx|}} | + | * **Automated iterative staging process for finding bottlenecks** |
+ | - 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. | ||
+ | - Reassignment and reconfiguration of hardware resources | ||
+ | - Reassignment and reconfiguration of software resource | ||
+ | ===== Deliverable & Reference ===== | ||
- | Please see the [[project_proposals:bottlenecks|Bottlenecks Project Proposal]] for more details. | + | ==== Presentation Slides ==== |
+ | * {{:undefined:bottlenecks.pdf|Bottlenecks Introduction}} at Project proposal | ||
+ | * concepts, classification of bottlenecks: https://jira.opnfv.org/projects/BOTTLENECK/issues/BOTTLENECK-34?filter=allopenissues | ||
- | ====== Meetings ====== | + | ==== project documents ==== |
- | Meeting details: | + | * basic information and how to use rubbos/vstf in bottlenecks project: http://artifacts.opnfv.org/bottlenecks/brahmaputra/bottlenecks_brahmaputra_docs/index.html |
- | ** Goto Meeting **: | + | ==== Meeting materials ==== |
- | *Meeting ID: [[https://global.gotomeeting.com/join/882532573]] | + | {{:bottlenecks_project_for_test_meeting_20150820.pptx|}} |
- | ** IRC meeting **: | ||
- | *freenode.net #opnfv-bottlenecks ([[http://webchat.freenode.net/?channels=opnfv-bottlenecks]]) | + | documents for bottlenecks: http://artifacts.opnfv.org/bottlenecks/docs/bottlenecks_brahmaputra_docs/index.html |
- | *Every Thursdays UTC 1:00-2:00, Beijing Time 9:00-10:00 | + | |
- | ** meeting agenda and logs ** | + | ==== Additional links ==== |
- | *[[https://wiki.opnfv.org/meetings/bottlenecks]] | + | * [[https://wiki.opnfv.org/releases/brahmaputra|Brahmaputra release page]] |
+ | * [[https://wiki.opnfv.org/testing|OPNFV Main Testing Page]] | ||
+ | * [[https://wiki.opnfv.org/developer/contribution_guidelines|OPNFV Coding Guidelines]] | ||
+ | * [[https://ask.opnfv.org/questions/|Ask OPNFV]] | ||
+ | * [[https://wiki.opnfv.org/releases/brahmaputra/release_plan|Brahmaputra release plan]] | ||
- | ** IRC **: | + | ===== Key Project Facts ===== |
- | + | ||
- | *freenode.net #opnfv-bottlenecks ([[http://webchat.freenode.net/?channels=opnfv-bottlenecks]])\\ | + | |
- | + | ||
- | ** etherpad for version plan **: | + | |
- | + | ||
- | *[[https://etherpad.opnfv.org/p/bottlenecks]]\\ | + | |
- | + | ||
- | ==== Key Project Facts ==== | + | |
{{scrape>https://gerrit.opnfv.org/gerrit/gitweb?p=bottlenecks.git;a=blob_plain;f=INFO;}} | {{scrape>https://gerrit.opnfv.org/gerrit/gitweb?p=bottlenecks.git;a=blob_plain;f=INFO;}} | ||
- | ==== Contributors ==== | + | ===== Contributors ===== |
Lynch Michael A(Intel): michael.a.lynch@intel.com\\ | Lynch Michael A(Intel): michael.a.lynch@intel.com\\ | ||
Line 107: | Line 101: | ||
Mingjiang Li: limingjiang@huawei.com\\ | Mingjiang Li: limingjiang@huawei.com\\ | ||
Lingli Deng: denglingli@chinamobile.com\\ | Lingli Deng: denglingli@chinamobile.com\\ | ||
+ | Qunwei Yang: qwyang0126@gmail.com\\ | ||
+ | Yaoguang Wang: sunshine.wang@huawei.com\\ | ||
+ | |||
+ |