Materials:

CNTT-OPNFV Current mode of operations: Resolving gaps and issues proposal

Attendees:

• Scot Steele (AT&T)
• Jack Morgan
• Phil Robb (Ericsson Software Technology)
• Cedric Ollivier (Orange)
• Scott Steinbrueck  (AT&T)
• Heather Kirksey (LFN)
• Jim Baker  (LFN)

...

• Discuss/define remediation for Gaps, Issues, Scope between CNTT/OPNFV
  • Topics Discussed revolved on the proposal below, Please review and comment on the proposal at the following Link: CNTT-OPNFV Current mode of operations: Resolving gaps and issues proposal
  • 1) CNTT RA-1 Requirements Traceability Matrix (link).  The existing requirements’ tables in RA-1 chapter 2 will be updated with columns for RI-1 and RC-1.
    • RA-1 chapter 2 will be updated in the near future via PR to move “may” and “should” entries from section 2.3 (“Requirements”) to section 2.4 (“Recommendations”).
    • The proposed updated matrix will specify which requirements are applicable to RI-1 (via new columns).
    • All “must” requirements will be applicable to RC-1, and this will be stated in RA-1 chapter 2.
    • Each RA-1 release will be mapped to a specific OSTK release; thus, the updated matrix contained in chapter 2 will also map to a specific OSTK release.
  • 2) CNTT RI-1/RC-1 Cookbook Ownership.  OPNFV team members have requested for OPNFV to own these documentation chunks.  This is ok with CNTT, based on the following conditions:
    • Cookbooks considered:  Installer, Lab, Test.
    • Cookbooks must conform to CNTT requirements and be dedicated for that unique purpose  (even though they could be used for additional purposes).
    • Cookbooks must state conformance to CNTT requirements.
    • Cookbooks must be linkable in a static location.  (any changes to the location need to be coordinated with CNTT)
    • Cookbooks must be released in alignment with CNTT releases, such that changes are coordinated and versioned together.
    • CNTT RI-1 and RC-1 will link to these OPNFV cookbook documents.

...