Project Name:
- Proposed name for the project: ONAP Benchmark
- Proposed name for the repository: OBenk
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.
Scope:
Levels
Component level: Workflow Engine(Aria Camunda DG) / Database(MySQL Graph Database)
Module level: SO / SDC / 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 | ||||
| Order/s—CPU--Memory | All Functions | ||
Database | ||||
| Based on Service/Use Case (Service model) | |||
| ||||
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)
Use the above information to create a key project facts section on your project page
Key Project Facts:
Facts | Info |
|---|---|
| Jira Key | TBD |
| Jira Project Name | TBD |
| Link to Wiki Space | TBD |
| Project ID | TBD |
| PTL (first and last name) | TBD |
Release Components Name:
Note: refer to existing project for details on how to fill out this table
Components Name | Components Repository name | Maven Group ID | Components Description |
|---|---|---|---|
| ONAP Benchmark | org.onap. | ||
Resources committed to the Release:
Note 1: No more than 5 committers per project. Balance the committers list and avoid members representing only one company. Ensure there is at least 3 companies supporting your proposal.
Note 2: It is critical to complete all the information requested, that will help to fast forward the onboarding process.
Role | Name | Gerrit ID | Company | TimeZone | |
|---|---|---|---|---|---|
Primary Contact | Chen Yan | China Telecom | Beijing, China. UTC +8 | ||
Contributors | HUAWEI | Beijing, China. UTC +8 | |||
ZTE | |||||
Committers | Huang Zonghe Chen Huiguang Luo Guangfeng Yu Wenbin Wang Luman Li min Du Jinyu Zhang Peng Wan Long | China Telecom | Beijing, China. UTC +8 | ||
Beijing, China. UTC +8 |
Key Project Facts
Project Name:
- JIRA project name: ONAP Benchmark (OBenk)
- JIRA project prefix: obenk
Repo name: OBank
Lifecycle State:
Primary Contact: Yan Chen (chenyan.bri@chinatelecom.cn)
Project Lead: TBD
mailing list tag [Should match Jira Project Prefix]
Committers:
Please refer to the table above.
*Link to TSC approval:
Link to approval of additional submitters: