Versions Compared

Key

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

...

Attendees

Discussion items

No.ItemWhoNotes
1Integration testing status update
 2

EXT API Bug Fix update - EXTAPI-602 - multiple instantiations of same service fails IN PROGRESS

3

Update on Core Slicing issues:

1)  https://jira.onap.org/browse/SO-3810 2)  https://jira.onap.org/browse/SO-3835
3)  https://jira.onap.org/browse/SO-3838

  • SO-3810, SO-3835 in progress
  • CBA package from I release not working properly, getting help from Sashmita.
    • Able to create core slice, NFs are updated, error with service instantiation in the 2nd time  
4E2E Network Slicing requirements for Kohn Release

Requirements deferred from Jakarta release

  1. Dynamic Discovery of Core & RAN endpoints at NSMF (Ahila/Wipro)
    • Consider backhaul endpoints only for K release
    • Discovery of core endpoints and mid-haul & fronthaul endpoints is a stretch goal
  2. CPS-TBDMT enhancement to integrate with NCMP (Ahila/Wipro). To confirm with CPS team
    • if the catching mechanism will be supported in K release so that CPS-E-05 can be included in network slicing flow
    • if RAN configuration from NCMP to SDNC will be supported in Kohn release
  3. Use case test automation (Ahila/Wipro, Tech-Mahindra, and other integration teams)
  4. DCAE Non-functional requirements (Ahila/Wipro) – impact on DCAE
    • DCAEGEN2-2907: REQ-358 No root (superuser) access to database from application container
    • DCAEGEN2-2801: Enhancements to KPI Computation MS, as a stretch goal
  5. TN NSSMF enhancements according to IETF latest specification (CCVPN team)
  6. Transport Slicing enhancement to support IBN based TN slicing (CCVPN team)
  7. CSIT for TN slicing (CCVPN team)
  8. Fix to Core Slicing issues (could also be put to the Jakarta maintenance release (REQ-3810, 3835, 3838)

New requirement proposals

  1. IBN driven E2E Network Slicing – CS request is given as business intent and to be integrated with the existing E2E slice flow. (Impact on DCAE, Policy, …) 
    • Focus on RAN slicing. Three sub-tasks includes
    • Integration of ML prediction MS with DCAE (IBN and NS teams)
    • Enhancement to intent creation and workflow to support E2E Network Slicing based on UUI, AAI and DCAE (IBN team)
    • Enhancement to the closed-loop and the ML slicing analysis MS for slicing KPI monitoring to support IBN (NS team)
  2. Leverage the current existing eMBB slice management to support mIoT slices – Impact on SO, SDN-R, New Policies needed (Ahila/Wipro)
  3. Closed loop updates over A1 interface (Ahila/Wipro) – impact on SDN-R, RAN Simulator, possible collaboration with SON use case

...