Versions Compared

Key

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

...

TrackKey PointsChallengesNext Steps / AIs
Guilin Planning


Guilin Planning  - Control loop sub committee - Guilin requirements


Moderator:

Pamela Dragosh

 Reviewed and discussed requirements for Control loop in G release :

Control Loop Sub Committee Guilin Release Planning



Security 


ETSI/CNF - ETSI NFV modeling and API 

Moderator: Hui Deng

#1 Latest ETSI NFV modeling and API progress Thinh Nguyenphu

#2 ETSI NFV model impact on R7 Xu Yang



Speaker: Bin Yang

  •  cFW - POC in progress based on ONAP MultiCloud project - Source code available here
  • What API is used in VID? VNF API or GR API? Does it make any difference? What about that override.yaml - is there an example available? VNF/VF API to instantiate the deploymen
  • No development yet related to fault and performance monitoring of the CNFs. Targeted for Guilin.
  •  Dummy heat template is temporary for now as we did not want to make any major changes to SDC and SO.  In R7, we intend to make Helm as first class citizen.  Until R6, Helm charts are hidden as artifacts under Dummy HEAT template.


Speaker: Fernando OliveiraByung-Woo Jun

  •  Discussions have started with SDC for ETSI alignment for the onboarding
  •  SVNFM/NFVO are coming from 3rd party vendors




ETSI/CNF - CNF Task Force -Review Multi Site Orchestration with ONAP4K8s (ONAP for K8s)

Moderators: Catherine LefevreSeshu Kumar Mudiganti

 Speaker: Srinivasa Addepalli

  • How to handle different VNF types i.e. Openstack based, Helm Chart based, Heat based etc? It should work based on the current ONAP4K8S
  •  How will the plugin with its own HPA placement logic interact with the rest of ONAP which also uses placement controller (OOF)?


#1 Upload Sandeep Sharma presentation

 Speaker: Rajendra Mishra


#1 Upload Sandeep Sharma presentation

E2E Network Slicing- Session 1

Moderator:

LIN MENG Swaminathan Seetharaman

  1. The overall requirements for E2E Network Slicing use case in Guilin release was presented. This covered:
  • New slice lifecycle operations to be supported. eg: slice modification, slice termination
  • Expansion in scope of E2E network slice to include RAN and Transport
  • Realization of NSSMF (Core/RAN/Transport) within ONAP, ONAP should also support NF set up and NF configurations under this condition
  • ONAP as NSMF connecting to external RAN NSSMF and Core NSSMF
  • KPI Monitoring, Closed Loop and Intelligent Slicing
  • Improvements to Frankfurt content

 2. User Operation Guidance for E2E Network Slicing Use case for Frankfurt release was presented. This covered:

(a)    ONAP components required for the use case, and the setup

(b)    How to create the associated design artifacts

(c)     UUI actions


 3. Questions asked:

  • How is Core NSSMF intended to be realized within ONAP?
  • How will a service be orchestrated by ONAP wherein part of the service only is within ONAP scope, whereas NSSMF within ONAP may be controlling the associated slice sub-net.
  • Details of modeling aspects and enhancements.
  • Are external domain controllers foreseen to be used for the domain-level actions?

 


Action Items

  1. Elaborate the modeling requirements and take it to the Modeling Sub-committee.
  2. Prepare further details, and illustrative flows showing interactions & APIs, including interaction with external domain controllers
 Joint Session


 Others



Day 3 - April 23, 2020

...