Current Mode OPNFV/CNTT RACI Chart

This chart serves as a high level RACI to ensure OPNFV and CNTT teams are working within their scope and boundaries. This is meant to be a high level chart to reach consensus, and promote open dialog regarding lower level responsibilities based on accepted boundaries.

Stakeholders Identified in the RACI are:

LFN
GSMA
OPNFV
CNTT

This is a living document!

Deliverable/Boundary	Responsible (Does actual work)	Accountable (Owns the end product)	Consulted (May use output, has input)	Informed (Uses Output, agnostic to input	Agreement	Comments

Deliverable/Boundary	Responsible (Does actual work)	Accountable (Owns the end product)	Consulted (May use output, has input)	Informed (Uses Output, agnostic to input	Agreement	Comments
Reference Model
- RM Development/Updates	CNTT	CNTT, GSMA	OPNFV	LFN Governance	Yes 29May2020	GSMA feedback loop to make sure that any GSMA changes are folded back into CNTT WS. Sync communications with related LFN projects (ONAP, LF Edge, etc.) ONAP needs to be considered, but still needs more detailed definition. CNTT will participate in the LFN Community Release Mgmt process

"1" Stream – Virtualization (OpenStack)
- RA-1 Requirements Development/Updates	CNTT	CNTT	OPNFV	GSMA, LFN Governance	Yes 29May2020	@vincent.danno@orange.com How can we make sure that we keep to the agreement practically? @Scot Steele Proposal: a monthly Joint TSC call to review the RACI, and Discuss issues with Boundaries. Issues should be based on live examples.
- RI-1 Requirements Development/Updates	CNTT	CNTT	OPNFV	GSMA, LFN Governance		Need to clarify the differences between RA, RI requirements and RI Cookbook. What is requirements and what falls into actual implementations. Traceability Matrix Resolves this issue.
- RI-1 Implementation (Cookbook), Integration, Operations	OPNFV	OPNFV	CNTT	GSMA, LFN Governance		Need to clarify the differences between RA, RI requirements and RI Cookbook. What is requirements and what falls into actual implementations. Traceability Matrix Resolves this issue.
- RC-1 Requirements Development/Updates	CNTT	CNTT	OPNFV	GSMA, LFN Governance		Need to clarify the differences between RC requirements and RI Cookbook. What is requirements and what falls into actual implementations. Traceability Matrix Resolves this issue.
- RC-1 Implementation (Cookbook), Integration, Operations	OPNFV	OPNFV	CNTT	GSMA, LFN Governance		@Al Morton limitations: available implementations (installers) available HW/infrastructure Cookbook 5 to 6 batch commands Traceability matrix BASH/Shell
- Requirements Traceability Matrix (Update RA-1 Ch 02 to be the master source of requirements;, add columns to show applicability to RI-1 and RC-1 requirements; then RI and RC can simply link back to RA-1 Ch 02) link to draft Requirements Traceability Matrix staged in Wiki	CNTT	CNTT	OPNFV	GSMA, LFN Governance	Yes 5June2020	@Al Morton some see traceability between RM and RA as traceability, too. OPNFV provides the possible Test cases CNTT select test cases to be executed.
RC-1 test result verification for badges	LFN Governance	LFN Governance	CNTT, OPNFV	CNTT, OPNFV		CNTT is in charge of the test case selection and the test case criteria CNTT published the cookbook which generates the zip file which may be shared to LFN for badges OVP/CVC/Dovetail via the web portal collects the zip files and verifies the test results are successful and not truncated

"2" Stream - Containers (Kubernetes)
- RA-2 Requirements Development/Updates	CNTT	CNTT	OPNFV	GSMA, LFN
- RI-2 Requirements Development/Updates	CNTT	CNTT	OPNFV	GSMA, LFN
- RI-2 Implementation (Cookbook), Integration, Operations	TBD	TBD		GSMA, LFN
- RC-2 Requirements Development/Updates	CNTT	CNTT	CNTT	GSMA, LFN
- RC-2 Implementation (Cookbook), Integration, Operations	TBD	TBD		GSMA, LFN
- Traceability Matrix	CNTT	CNTT	OPNFV	GSMA, LFN

Cook Books
- Installer	OPNFV	OPNFV	CNTT	GSMA, LFN
- Lab	OPNFV	OPNFV	CNTT	GSMA, LFN
- Test	OPNFV	OPNFV	CNTT	GSMA, LFN