Versions Compared

Old Version 32

changes.mady.by.user Catherine Lefevre

Saved on

compared with

New Version 33

changes.mady.by.user Kenny Paul

Saved on

Key

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

...

TrackKey PointsChallengesNext Steps / AIs
LF StaffBe respectful of everyone's time
  • Presenters not on the bridge
    • Extended debates 
    • Presenters not concluding on time
    • Please be connected to the bridge 10 mins before schedule
    • Please request follow-up discussions
    • Please stick to your scheduled timeslot 
    Testing


    CNTT


    OPNFV


    ONAP

    Change Management support














    Presented what is done in Frankfurt and what is planned in Guilin












    Build and Replace worklfow schould allow to modufy existing instances of the VNFs on the fly.

    Lack of VNFC level reconfiguration is one if the missing features on SO/Controller side which is not suppoirted today. We want to solve this issue in the Guilin release

    PNF support by ONAP Change Management is the key challenge, planned to extend in Guilin

    Schema/VSP Update is a chalange in the Upgrade process in ONAP. We want to addres this issue and to enable update of the schema with adequate modification of the existing instnces of services - for PNFs, VNFs and CNFs

    Integration with CDS and K8s workloads as one of the key drivers for improvements of change management porocess in ONAP as K8s provides scaling, upgrades and traffic distribution capabilities by itself. For Frankfurt integration with CDS for CNFs creation is introduces. IN further releases K8s scaling and upgrade capabilities should be introduced.


    Transport slicing support by ONAP

    This presentation focused on:

    • Introduction to Transport Slicing in 5G context
    • Design of Transport Slicing
    • How to extend CCVPN to enable Transport Slicing
    • How Transport Slicing fit into E2E Network Slicing
    • How to work with SDOs on coordinating aspects of standards
    1. Continue to work with the SDO's to improve and finalize the IETF TEAS working group draft on Transport Slicing
    2. Finalize the architecture of Networking Slicing on how NFVO should be used
    3. Should the Transport Slicing solution support CNF Connectivity?
    4. Should Transport Slicing be considered as a Generic Network Building block?
    Network slicing (core network) ongoing support by ONAP

    CSMF and NSMF part of ONAP. External NSSMF to be used.

    Demo for Frankfurt:

    • Transport subnet not in scope
    • Simulator RAN and core NSSMF simulator


    Challenges on whether this is the only possible implementation or there may be more

    Alignment on API  with 3GPP and  ORAN A1

    Discussion on communication-service-profile introduced in ONAP

    Warning on  templates that are deprecated within 3GPP

    Impacts

    • No evolution in SDC
    • New WF for SO and NSSMFAdaptor
    • OOF used for NSI selection
    • &AI impact to include new 3GPP concepts (service profile, slice profile...)
    • 2 new portals: CSMF and NSMF (under UUI project)
    SECCOM: Password removalAll passwords should be stored only in Kubernetes secrets, users should be allowed to provide their own secrets for the deployment and allow to generate passwords at the deployment time.Further exchanges with ONAP community on best practice approval and implementation - sessions at the PTLs and TSCs calls.
    SECCOM: Ingress controller 

    Ingress Controller introduced for Frankfurt as an option deployment

    Effort on passing knowledge to ONAP teams on ingress controller and service mesh

    		Sessions at the PTLs calls.
    ONAP SECCOM ISTIO opportunity for common continuation discussion   Coexistance of AAF and Service Mesh in a long term security solution AAF and ISTIO to be treated as two separate tracks
     Use Case Cross-Carrier 5G 

     Get the Community Aligned on Network Slicing - AP for Architecture/Requirements subcommittee + Magnus (ONAP TCC)

    What are the "baby steps" to build a "Slicing" roadmap

    Promote ONAP through #1 use cases that does not require changes in ONAP; #2 POC so Innovation can continue while focus on ONAP Core. 

     Use Case Subcommittee

    •  Review of Frankfurt/Guilin Use cases


    ...