Versions Compared

Version Old Version 15 New Version Current
Changes made by

Beth Cohen

Scot Steele

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Stakeholders Identified in the RACI are:

  • LFN
  • GSMA
  • OPNFV
  • CNTT

General group agreement 

...

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.

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
Stream – Virtualization (OpenStack)





 - RA-1 Requirements Development/UpdatesCNTTCNTTOPNFVGSMA, LFN GovernanceYes 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/UpdatesCNTTCNTTOPNFVGSMA, 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, OperationsOPNFVOPNFVCNTTGSMA, 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/UpdatesCNTTCNTTOPNFVGSMA, 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, OperationsOPNFVOPNFVCNTTGSMA, 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

CNTTCNTTOPNFVGSMA, LFN
"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.
GovernanceYes 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 badgesLFN GovernanceLFN GovernanceCNTT, OPNFVCNTT, 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/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:

...

  • 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!

...