1 Project Name:
2 Project description:
3 Scope:
4 Architecture Alignment:
5 Other Information:
6 Key Project Facts:
7 Release Components Name:
8 Resources committed to the Release:
9 Project Summarization:

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: 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 auto test scripts/use cases.

Scope:

Levels
- Component level: Workflow Engine(Aria Camunda DG) / Database(Graph Database)
- Module level: SO / 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

Test Point	Consistency	Performance	Function	Scalability
SO
√ Workflow Engine	BPMN/BPEL	Order/s—CPU--Memory	All Funtions	Cluster
Aria
Camunda/Activiti
DG
DCAE
Ves			All Functions

Database
Graph Database		Based on Service/Use Case (Service model)
		Based on Service/Use Case (Service model)

Specific Input and Output:

ONAP Benchmark (OBenk) test KPI:

KPI	Description

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

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

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	First Name Last Name	Linux Foundation ID	Email Address	Location

Role	First Name Last Name	Email Address	Location
PTL	Chen Yan	chenyan.bri@chinatelecom.cn	Beijing, China.
Committers	Chen Yan	chenyan.bri@chinatelecom.cn	Beijing, China.
	Kang Xi	kang.xi@huawei.com	Bridgewater, NJ, US.
	Meng Zhaoxing	meng.zhaoxing1@zte.com.cn	Chengdu, China
	Vivien Yang	vivien.yang@intel.com	Santa Clara, CA, US.

Contributors
	Huang Zonghe	huangzh.bri@chinatelecom.cn	Beijing, China.
	Kang Xi	kang.xi@huawei.com	Bridgewater, NJ, US.
	Yu Wenbin	yuwb.bri@chinatelecom.cn	Beijing, China.
	Wang Luman	wanglm.bri@chinatelecom.cn	Beijing, China.
	Zhang Peng	Zhangpeng.bri@chinatelecom.cn	Beijing, China.

Project Summarization:

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: