5G Use Case Meeting notes for Oct 31, 2019

• Documentation (Read the Docs) - 
  • READ THE DOCS: https://onap.readthedocs.io/en/latest/index.html
  • Navigate to > USER GUIDES > Verified USE CASES
  • Use Case Page: https://docs.onap.org/en/dublin/submodules/integration.git/docs/docs_usecases.html
  • Doc PTL Sofia Wallin  - Ask Sofia to help w/ training
• Security Vulnerabilities - (done by PTLs)? OPEN POINT.
• Product Management - Jira/ Backlog Epics OCT 24: In Progress. OPEN POINT
  
• Release Management - Frankfurt Release Requirements OCT 24: DONE
• Testing / Integration - Test plans OPEN POINT.
• Development -

ACTIONS:

1. Harmonization U/C Identify Integration Lead

Dongho Kim - discussing with Ericsson and AT&T who can commit. A1 adaptor unit testing. RESOLUTION A1/O1 Sandeep Shah

For O1 part Nokia. CMnotif. fault, CallTrace(no), ...

• FINISHEDmarge.hillis Need to find Integration Lead. RESOLUTION A1/O1 Sandeep Shah
  

2. RunTime Config DB Integration Lead

• Joanne Liu Rudelfind the Integration Lead  RESOLUTION: Need to identify SDC-R integration work. Build processor MariaDB; SDN-R receives the SDC CSAR package S/W will be REUSED so no new development.
  

3. OOF/SON/PCI U/C Integration Lead

• Swaminathan Seetharamanto identify lead. Oct 24 still an open item ACTION: Identify lead
  Swami (Oct 25th) - lead identified and updated in Frankfurt Release Requirements page. 

4. Pre-onboarding/Onboarding U/C

  We do not need full E2E Integration Zu Qiang , only need to integrate the new development in VNF-SDK CLOSED FINISHED. Nokia will be integration the VNF-SDK work (confirmed).

5. Network Slicing is Missing per company Commitment & Integration lead(s)

• Borislav Glozman to fill in information. CLOSED FINISHED, Added now.
  

ACTIONS:

• Benjamin CheungContact cl664y@att.com to let her know that we have removed the RED marking the per company commitment cells
  
• Benjamin Cheung Raised at TSC "What does an Integration Lead Do?" (formal definition): ONAP "Use Case/Requirement" Integration Lead

31 Oct 2019  Reviewed Frankfurt Release Requirements

All 5G Use Cases have a Jira Ticket tree (w/ TSC Milestone child-Jiras)

For Bulk PM : PM Control Support + Secure communication between xNFs and ONAP in 5G Bulk PM 

For NRM: NRM Configuration with RESTFul protocol

RunTime DB

Architecture S/C presentation for Run Time DB.

Documenting (1) Arch component wiki ARC RunTime DB Component Description - R6 Frankfurt

(2) Flow using Run Time DB. Presented Oct 15, 2019.

(3) Making RunTime DB as a separate common service component

   - Discussed at the Architecture S/C Oct 23.

(4) Need to present TSC AFTER approval from Architect S/C.

(5) Meeting with David McBride

OCT 24 - Presented at the Architecture S/C Oct 22, Arch S/C said it was ok to proceed with the RunTime Config DB as a new ONAP component. So need to fill out the New component page.

Weekly Meetings on Fridays. https://zoom.us/j/230322363 (ONAP 4 hosted)

31 Oct 2019  Reviewing the Frankfurt Release Requirements, we notice that the TSC made a comment:

• For the network slcing.  The following is a Go from architecture
  
  • SO plug-in to an External NSSMF (for core).
  • CSMF and NSMF representation in ONAP, and also allowing CSMF external.
  • What is not approved is NSSMF in ONAP; nor connecting two subslices together as that requires the NSSMF and that still needs quite some more discussion.

This should limit the impacts to SO and External API for Frankfurt 

And some of the Code Impact/Code Commit cells are RED. Vimal Begwani  stated that swami et al team will indicate what is the exact scope for R6. Debate only NSSMF or SO impact might not be as stated here.

• 05 Nov 2019 PRESENTATION TO ARCH Subcommittee - This will be presented to the Architecture S/C.

Trying to settle on scope of the Use Case. List of many possible contributions that will take more than one release to complete. Impacts for items to be added to wiki (analysis).

Prioritize the work items what we could propose to accomplish.

CM Notify & Payload as a new domain has been accepted on the DCAE S/C today Oct 24 2019.

New VES specification 7.1.1; addendum being added.

3GPP Fault event fields specified in 3GPP mismatched VES specification; 3GPP SA5.

Use Case Template - discuss updating the Use Case template & pages with some of these fields. Modeling team has said it would be useful for them to have the pre-condition & post-conditions, and information being passed (info-flows) documented.

Use Case Template

Filling out, describing and creating the Wiki for a Use Case

Use Case Tracking Template and Use Case Template

Proposed Functional Template for Use Cases

Ben talked w/ Andy Mayer U/CR call Oct 23. He said he is preparing the page, and would present here at the 5G U/C S/C call.