You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 18 Next »

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

AgreementComments
Reference Model





  - RM Development/UpdatesCNTTCNTT, GSMAOPNFVLFN GovernanceYes 29May2020

GSMA feedback loop to make sure that any GSMA changes are folded back into CNTT WS.

Jack Morgan OPNFV has other requirements that might affect the work output.

Sync communications with related LFN projects (ONAP, LF Edge, etc.)  ONAP needs to be considered, but still needs more detailed definition.








"1" Stream – Virtualization (OpenStack)





 - RA-1 Requirements Development/UpdatesCNTTCNTTOPNFVGSMA, LFN GovernanceYes 29May2020

Vincent Danno How can we make sure that we keep to the agreement practically?

 - RI-1 Requirements Development/UpdatesCNTTCNTTOPNFVGSMA, LFN Governance
Need to clarify the differences between RA, RI requirements and RI Cookbook.  What is requirements and what falls into actual implementations.
 - RI-1 Implementation (Cookbook), Integration, OperationsOPNFVOPNFVCNTTGSMA, LFN Governance
Need to clarify the differences between RA, RI requirements and RI Cookbook.  What is requirements and what falls into actual implementations.
 - RC-1 Requirements Development/UpdatesCNTTCNTTOPNFVGSMA, LFN Governance
Need to clarify the differences between RC requirements and RI Cookbook.  What is requirements and what falls into actual implementations.
- RC-1 Implementation (Cookbook), Integration, OperationsOPNFVOPNFVCNTTGSMA, LFN Governance

Al Morton limitations:

  • available implementatons (installers)
  • available HW/infrastructure
 - Traceability MatrixCNTTCNTTOPNFVGSMA, LFN Governance

Al Morton some see traceability between RM and RA as traceability, too.








"2" Stream - Containers (Kubernetes)





 - RA-2 Requirements Development/UpdatesCNTTCNTTOPNFVGSMA, LFN

 - RI-2 Requirements Development/UpdatesCNTTCNTTOPNFVGSMA, LFN

 - RI-2 Implementation (Cookbook), Integration, OperationsTBDTBD
GSMA, LFN

 - RC-2 Requirements Development/UpdatesCNTTCNTTCNTTGSMA, LFN

- RC-2 Implementation (Cookbook), Integration, OperationsTBDTBD
GSMA, LFN

 - Traceability MatrixCNTTCNTTOPNFVGSMA, LFN








Cook Books





 - InstallerOPNFVOPNFVCNTTGSMA, LFN

 - LabOPNFVOPNFVCNTTGSMA, LFN

 - TestOPNFVOPNFVCNTTGSMA, LFN

  • No labels