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

Compare with Current View Page History

« Previous Version 17 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 – VM based VNFs (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 (TBD) → we need to see how successful "1" arrangement is. → no need to rush in thinking about "2" and we still didn't figure out "1". I STRONGLY SUGGEST NOT TO RUSH INTO THIS WITHOUT FIGURE OUT "1" AND PROVE MODEL WORKS.





 - 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

Questions need to be answered:

  • What happens when CNTT develop a requirement in, say, RI-1?
    • do CNTT goes directly to prospective OPNFV project and get it implemented (via that project PTL).
      • how are those implementation will link back to CNTT releases? 
      • Will each project has their own release cycle (with appropriate baggings) or will OPNFV has an overall release cadence ? how does the model work?
    • or will CNTT has to follow some kind of process to get their requirements implemented?
    • or will OPNFV itself regularly get CNTT releases and find the right OPNFV projects to implement any new requirements.
      • via CIRV?
    • what is the role of OPNFV TSC on all this? who is accountable for what?
    • we need to talk about accountability and make it clear who is accountable for what!
  • How does OVP fit into this matrix?
  • Given the GSMA process is it mostly a consumer and ratifier of the output from CNTT, or does it have a role in providing feedback?  I.e. how can this be set up to be a two way street? 
  • No labels