Versions Compared

Old Version 2

changes.mady.by.user Benjamin Cheung

Saved on

compared with

New Version 3

changes.mady.by.user Benjamin Cheung

Saved on

Key

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

...

CtgryItemWhoNotes
Meeting Notes Discussion
  1. R7 Requirements / Use Cases - Guilin release - functional requirements proposed list
  2. Upcoming Meetings - R7 Use Case Realization Meetings MoM
  3. Use Case Process - ONAP Use Case Teams Process

Discussion Notes from

Presentation on CDS Designer UI Client, CDS Customer building blocks & Flexible W/F designer
  2. Virtual Sub-Committee meeting Apr 21-23 / R7 planning & presentation F2F. will be done virtually is still happening, coordinating via Kenny Paul looking for volunteers to coordinate. Link: https://wiki.lfnetworking.org/display/LN/2020+April+Virtual+Technical+Event
  3. Model Planning for R7 ONAP R7 Modeling High Level Requirements
  • CDS is used for configuring & provisioning automation, in CDS create a package manually to enable automation; evolving w/ orange team to create a designer UI where package creation is simplified. doesn't see TOSCA enable automation for PNF/VNF U/Cs. In CDS support provisioing & configuration. Driven by design time package, what can we automated? Create own TOSCA imperative W/F. For these actions, these are step to take (sequential or parallel) → how to create W/F within CDS. W/F for provisioning (not svc orchestration). e.g. if you have SO triggering controller a post-action, might want to do configuration, or config-deploy, update BSS/OSS, imperative steps can be described in design time using TOSCA framework → deploy into run-time systems; different execute different actions ; W/F creation where you can create set of steps → once you create your W/F (reusable- customizable) can IMPORT scripts/templates essential artifacts of those W/F. What you trigger W/F action done in generic way. In R6, as part of E2E automation be able to integration SO, Policy, CDS generically; new BB recipie you don't need to provide custom flows. Introduce new features on the fly as part of design time instead of having bound to a code release. This W/F can be executed from SO as singular action. Generic way to implement SO & Policy w/ controller, execute any xNF service level action generically for any W/F action. When package is created in R6 integration with SO & Policy, CLAMP → update tables to integrate with CDS. W/F executed on singular VNF. Action name selection does it correspond to the SO building block name > "test 2" is a function name
  • Designer / Scripting "experienced user - developer" EDITOR type functionality ... inside file ; depending on experience - have two types of users, two types different needs to user experiences. explicit enrichment process user-driven ; ind designer implicit → drag & drop capabilities based on what you are doing (simpler, easy to use)
    • Additional notes from
    1. Additional notes from   Yuriy Malakov Here are additional information to learn more about the CDS Project.

    Pltfm


    PLATFORM TOPICS:

    Controller to NF Association

    Benjamin Cheung

    See Slides Nov 6, 2018. Development of Controller to NF assignment association S/W.

    CDS, VF-C, APP-C, SDN-R, SDN-C; will the CCSDK "merging" of controllers happen in R6?

    USE CASE REALIZATION MEETING (Notes 2018-11-6) Ctrl-NF

    Use Case

    PLATFORM TOPICS:

    Data Persistency, RunTime DB

    N.K. Shankaranarayanan

    Joanne Liu Rudel

    Benjamin Cheung

    RunTime Config DB is now a R6 use case :

    USE CASE REALIZATION MEETING (Notes 2019-01-30) U/C Cross-Interaction, Persistency

    CONFIGURATION & PERSISTENCY SERVICE

    Jan 22 - CMNotify; SA5 3GPP Meeting. CMNotify domain. VES Event spec 7.1.1. Alok Gupta has not updated the VES event. On a leave of absence (Hip surgery). CMNotify is going to be done by Nokia. Sync with Sandeep Shah CM Notification Support in ONAP

    Pltfm

    PLATFORM TOPICS:

    Controller LCM API Evolution

    Oskar Malm

    https://wiki.onap.org/download/attachments/50202249/2019-04-09%20ONAP_LCM_API_Evolution_El_Alto.pptx?api=v2

    Goals (Architecture Evolution)
    • Target is common LCM API in CCSDK usable by different controller personas to simplify for both clients and controller implementations
    • Support PNFs for applicable LCM operations in a consistent way
    • Enable use of CDS blueprint processor to customize behavior of LCM operations in the 'self-service' category
      • In ONAP R4, CDS can be used for pre/post-instantiation configuration. Generic and model-driven design should allow CDS usage to be extended for additional operations and use cases.
    • Evolution steps that preserve backwards compatibility for clients

    Present at the Arch S/C Apr 9 (Tue) second presentation.

    Use Cases

    USE CASE/5G:

    RAN (ORAN-3GPP) Standards Harmonization with ONAP

    Marge Hillis

    Vimal Begwani

    Fred Feisullin

    Use Case WIKI: MOBILITY STANDARDS HARMONIZATION WITH ONAP

    Use Cases

    USE CASE/5G:

    Licensing Management

    Timo Perala

    Samuli Kuusela

    New U/C added to the 5G Use Cases Wiki: LICENSING MANAGEMENT

    (Oct 8 2019) Arch Samuli presented on Licensing Management.

    Modeling work: ONAP R6 Modeling High Level Requirements

    Kevin Skaggs Proposed Licensing Platform Model

    Use Cases

    USE CASE/5G:

    OOF / SON / PCI

    N.K. Shankaranarayanan

    PoC for December 2019? SDN-R south-bound NetConf I/F w/ model

    and also integration with Runtime DB work.

    Use Cases

    USE CASES:

    BBS U/C Evolution

    David Perez Caparros

    Tim Carey

    Chaker Al-Hakim

    BBS Evolution - Slide set linked in R6 proposed U/C. List of proposals & functional requirements.

    1. Change Service - want to use ONAP platform.
    2. Full Closed Loop for Fault Management - CLAMP.
    3. Service Update API (SO) - will be developed

    https://wiki.onap.org/download/attachments/60887504/BBS_R5_v1.pptx?version=1&modificationDate=1554180715000&api=v2

    Use Cases

    USE CASES/5G:

    PM Dictionary/FM MD GUI

    Marge Hillis
    		FM META DATA & PM DICTIONARY in R5
    Use Cases

    USE CASES/5G:

    PNF S/W Upgrade

    Zu Qiang (Ericsson)

    yaoguang wang

    		PNF software upgrade in R6 Frankfurt
    Use Cases

    USE CASES/5G:

    Preonboarding/Onboarding

    Benjamin Cheung

    Zu Qiang (Ericsson)

    Michela Bevilacqua

    PNF PREONBOARDING / ONBOARDING in R5

    VNF-SDK Artifact package security

    Use CasesUSE CASES:

    IoT Service Creation

    Atul Purohit

    IoT Create Services on 5G

    5G Use Cases in R6 Frankfurt

    June 19, 2019

    Use Cases

    USE CASES:

    Modeling gNB/5G RAN

    Thinh Nguyenphu

    Benjamin Cheung

    Melanie Sater

    Tracy Van Brakle

    Martin Skorupski

    Kevin Scaggs

    Align & harmonize information models to ONAP model and ONAP internal information & data model:

    ETSI SOL001 ... 007 with ONAP internal Model, PNFD modeling (Model S/C), 5G Model (3GPP, RAN), ORAN (WGs, RAN), Open ROADM (reconfig optical add/drop multiplexer, Optical), ONF (Optical), ISOMII (Optical), OTCC (Optical transport config & control)

    Use Cases

    USE CASES:

    5G NRM (Network Resource Model) Configuration

    		yaoguang wang

    June 2019 LFN DDF, titled as '5G Provisioning management service to NRM' 

    Presentation: 5G Network Resource Model (NRM) Configuration in R6 Frankfurt

    Use Cases

    USE CASES:

    PNF / Plug and Play

    		Benjamin Cheung

    PNF Plug and Play

    M2/ - Pending 

    Jira
    serverONAP JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId425b2b0a-557c-3c0c-b515-579789cceedb
    keyREQ-140
    - CMPv2 Security enhancements to AAF (Netconf & PM impacts also).

    Arch

    Architecture S/C

    PNF POB/OB Flow

    Benjamin Cheung

    Arch S/C Information Flows: Draft ONAP Information Flows

    New Information flow for Preonboarding/Onboarding xNF packages/resources.

    ARCHCOM: InfoFlow - Onboard Resource into SDC Flow

    TSC

    TSC:

    PoC Definition

    Benjamin Cheung

    Alla Goldner

    		POC definition
    TSC

    TSC/USE CASES:

    Test Automation Progress

    Benjamin Cheung

    Alla Goldner

    Use Case Test Automation

    Action Items: Use case subcommittee to reach the Dublin use case owner to provide the following information. what's the current percentage of testing automation regarding your use case and functional requirements; what will be the plan to be 100% and constraints (resources availability etc.)

    Release TrackingR6 Frankfurt / M2All Team Members

    Use Case Tracking Template

    Need the U/C teams to fill out the Dev. Impacts.

    More Generalized Use Case Template (discussed w/ Model team):

    Use Case Tracking Template and Use Case Template

    Frankfurt Release Requirements

    Demos

    Plug- fest

    		Demo Plugfest

    Tracy Van Brakle

    Marci Haas

    Martin Skorupski

    POC & Plugfest in End June 2020

    WINLAB? A1/O1 ORAN & ONAP Joint Plugfest

    Panel Discussion - ? / Maybe in January-February

    Setup. Bronze Release. / Slicing, Heart Beat-Health Check


    Architecture TopicsArchitecture TopicsAll Team Members

    Architecture Component Descriptions:

    ONAP Architecture Component Description - Dublin

    Architecture Flows:

    Dublin ONAP Information Flows


    		Read the DocsAll members

    DOCUMENTATION - Documentation (Read the Docs) - M1 - M4

    "Are you referring to MS1 and the preliminary documentation?

    https://wiki.onap.org/display/DW/Frankfurt+Documentation

    Multiple Repo / Use Cases are under Integration Repo

    VNFREQ has Repo / Verified U/C in Integration Repo

    Andreas Geissler - Discussed should put docs on the readthedocs (not in wiki)

    should have own Repo for Use Cases or Req sub-committee own repo

    Discuss w/ Sophia. Linked to completed readthedocs consisting of multiple repos. Make docs inside of components independent of main bulid process. subfolder structure made independent. own RST files for each Use Case. linked into the main docs.

    Is multi-repo planned for R7? Integ, SecCom, Architecture.

    Hackathon - comming events

    ...