| Table of Contents | ||||
|---|---|---|---|---|
|
Proposal declined by TSC as a stand-alone project TSC 2018-01-04. Recommended to be part of Integration Project
Project Name:
- Proposed name for the project: ONAP Benchmark
- Proposed name for the repository: OBenkobenk
Project description:
The ONAP Benchmark project aims to provide Function/Performance/Scalability/Security test for ONAP component/module/system level.
Finding bottleneck for E2E system and making advice for corresponding module for code improvement.
Making test report for ONAP developer/user/cooperator.
ONAP Benchmark develops auto test environment and develop auto test scripts/use cases.
...
Levels
Component level: Workflow Engine(Aria Camunda DG) / Database(MySQL Graph Database)
Module level: SO / SDC DCAE / SDNC / A&AI /…
System level: E2E test for release use case
ONAP Benchmark test
Functional test
Performance test
- Stability test
- Scalability test
Consistency test
Stress Test
- ...
Current Resources and Scope for R2:
Specific Test for R2:
Test Point | Consistency | Performance | Function | Scalability |
|---|---|---|---|---|
SO | ||||
√ Workflow Engine | BPMN/BPEL | Order/s—CPU--Memory | All Funtions | Cluster |
| ||||
| ||||
|
SDNC
DCAE | ||||
|
- Controller
All Functions | ||||
Database | ||||
| Based on Service/Use Case | |||
(Service model) |
- MySQL
Specific Input and Output:
ONAP Benchmark (OBenk) test KPI:
KPI | Description |
|---|---|
Query Per Second | |
Single request maximum response time | |
Maximum support specification capacity | |
Funtion points | |
Maintainable reliability | |
Reconciliation function | Configuration reservation after device restart |
Architecture Alignment:
Other Information:
- Link to seed code (if applicable)
Vendor Neutral
Meets Board policy (including IPR)
Key Project Facts:
Facts | Info |
|---|---|
| Jira Key |
| OB |
| Jira Project Name |
| ONAP Benchmark |
| Link to Wiki Space |
| Project ID |
| ONAP Benchmark |
| PTL (first and last name) |
| Chen Yan |
Release Components Name:
Components Name | Components Repository name | Maven Group ID | Components Description |
|---|---|---|---|
| ONAP Benchmark | org.onap. | ||
...
Role | First Name Last Name | Linux Foundation ID | Email Address | Location | ||||||
|---|---|---|---|---|---|---|---|---|---|---|
| PTL | Chen Yan | Chenyanchenyan.bri@chinatelecom.cn | Beijing, China. | |||||||
| Committers | Chen Yan | Chenyanchenyan.bri@chinatelecom.cn | Beijing, China. | |||||||
| Huang Zonghe Kang Xi | Huangzhbri@chinatelecomcn | BeijingBridgewater, NJ, ChinaUS. | ||||||||
| Kang XiMeng Zhaoxing | kangmeng.xi@huaweizhaoxing1@zte.com.cn | BeijingChengdu, China. | ||||||||
| Vivien Yang | vivien.yang@intel.com | Santa Clara, CA, US. | ||||||||
| Contributors | ||||||||||
| Huang Zonghe | huangzh | Contributors | Chen Huiguang | chenhg.bri@chinatelecom.cn | Beijing, China. | Luo Guangfeng | luogf.bri@chinatelecom.cn | Beijing, China. | ||
Kang Xi | Bridgewater, NJ, US. | |||||||||
| Yu Wenbin | yuwb.bri@chinatelecom.cn | Beijing, China. | ||||||||
| Wang Luman | wanglm.bri@chinatelecom.cn | Beijing, China. | Li min | limin.bri@chinatelecom.cn | Beijing, China. | |||||
| Du Jinyu | Dujy.bri@chinatelecom.cn | Beijing, China. | Zhang Peng | Zhangpeng.bri@chinatelecom.cn | Beijing, China. | Wan Long | wanlong.bri@chinatelecom.cn | Beijing, China. | ||
Project Summarization:
Project Name:
...