Use Case Realization Call: July 8, 2020

Use Case Realization Call: July 8, 2020

Date

Jul 8, 2020

Attendees

  • @Benjamin Cheung (Nokia)

  • @Gerard Hynes

  • Chris Rapposelli-Manzo

  • @Vimal Begwani

  • Melanie Sater

  • @Yuriy Malakov

  • John Keeney

  • @William Reehil

  • @James Forsyth

  • @Mike Elliott

  • @Zu Qiang

  • @Junfeng Wang (Ericsson)

  • Raghavan Subramanian

  • x

DISCUSSION ITEMS LOG

 

Ctgry

Item

Who

Notes

Meeting Notes Discussion

  1. A&AI team with Use Case Discussion

  2. x

  3. x

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:

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/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

@wangyaoguang

PNF software upgrade in R6 Frankfurt

Use Cases

USE CASES/5G:

Preonboarding/Onboarding

@Benjamin Cheung

@Zu Qiang

@Michela Bevilacqua [Ericsson]

PNF PREONBOARDING / ONBOARDING in R5

VNF-SDK Artifact package security

Use Cases

USE CASES:

Modeling gNB/5G RAN

@Thinh Nguyenphu (Unlicensed)

@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

@wangyaoguang

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/ Jan 22, 2020 - Pending  https://lf-onap.atlassian.net/browse/REQ-140- CMPv2 Security enhancements to AAF (Netconf & PM impacts also).

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 Tracking

R7 Frankfurt

All 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 Topics

Architecture Topics

All Team Members

Architecture Component Descriptions:

ONAP Architecture Component Description - Dublin

Architecture Flows:

Dublin ONAP Information Flows

Use Cases

Read the Docs

All members

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

"Are you referring to MS1 and the preliminary documentation?

https://lf-onap.atlassian.net/wiki/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

Use Cases

Req / Use Case Way of Working Process (WoW)

All members

ONAP Use Case / Requirements Teams Process Way of Working (WoW)

 

A&AI Use Case Analysis

A&AI impacts w/ use cases and requirements

@James Forsyth  A&AI PTL → @William Reehil  new A&AI PTL

working on A&AI for 4 years (as an architect & lead dev on platform team) worked in ONAP. attending weekly meetings.

Jimmy will fwd to Bill, can still reach out to Jimmy as needed.

USE CASE

REQUIREMENTS

DESCRIPTION & DISCUSSION

USE CASE

REQUIREMENTS

DESCRIPTION & DISCUSSION

E2E Network Slicing

WIKI PAGE: E2E Network Slicing Use Case in R7 Guilin

JIRA: https://lf-onap.atlassian.net/browse/REQ-342 , https://lf-onap.atlassian.net/browse/AAI-2916 , https://lf-onap.atlassian.net/browse/AAI-2917

IMPACT: (see Jiras) Impacts to mS to extract fields from SDC. Need to investigate. E2E Slicing.  Key contact: @Swaminathan Seetharaman

Configuration & Persistency

Service

WIKI PAGE: Configuration & Persistency Service R7

JIRA: Test Only

IMPACT: Test Only

Intent Based Networking

WIKI PAGE: Intent-Based Network

JIRA: https://lf-onap.atlassian.net/browse/REQ-329

IMPACT: INVESTIGATION. Identified A&AI. Contact @Huang ZongHe . Presented at the Architecture S/C. Possibly moved to POC status:

Linked to: https://lf-onap.atlassian.net/browse/ONAPARC-589 Arch S/C recordings: ONAPARC 2020 Meetings

Presentation https://jira.onap.org/secure/attachment/16127/16127_ONAP_Proposal_IBN+V1.7.pptx

CC VPN Transport Slicing

WIKI PAGE: Guilin release - functional requirements proposed list#ccvpnTransportSlicingCCVPN-TransportSlicing

An End-to-End 5G Network Slice consists of RAN, Transport and Core network slice sub-nets. This requirement is devoted to the realization Transport Slice sub-nets. It implements TN NSSMF, of which the functionality includes the modeling, orchestration and assurance of a Transport Slice. While TN NSSMF is a self-contained entity and thus this requirement can be independent, ensuring the integration with the E2E Network Slicing is an important aspect of this requirement. Standards-based interfaces and architectural framework (e.g., ETSI ZSM, IETF) are used by this requirement.

Storing Slice ID, and which Element participating in the Slice. @Swaminathan Seetharaman ; https://wiki.lfnetworking.org/display/LN/2020+June+Virtual+Recordings

Slides: https://wiki.lfnetworking.org/pages/viewpage.action?pageId=34606297#id-2020JuneVirtualLFNDeveloper&TestingForumTopicProposals-ONAP-E2ENetworkSlicingSession2

JIRA:https://lf-onap.atlassian.net/browse/REQ-347 , https://lf-onap.atlassian.net/browse/AAI-2920

IMPACT:

PNF Software Upgrade

WIKI PAGE: Support xNF Software Upgrade in association to schema updates

JIRA:https://lf-onap.atlassian.net/browse/REQ-324 , https://lf-onap.atlassian.net/browse/AAI-2935

IMPACT: Lead: @Zu Qiang , Support xNF Software Upgrade in association to schema updates. VNF S/W version into A&AI.

Done in eComp? ported to ONAP (confirmed) (from Chris Rapposelli-Manzo). Email sent from Lukasz to @Zu Qiang

Generic-VNF object in A&AI will have software-version attribute. It should be optional and should be of string type. Exemplary values are: "1.0", "1.0.1", "2.0.0"

It is in the S/W but Not in Swagger file yet (version 19). Perhaps swagger not generated yet. How is the swagger file updated?

Targeted for V20? still needs to generated and published. (will be other changes too)

CNF Orchestration

WIKI PAGE: Guilin release - functional requirements proposed list#SupportforContainerizedNetworkFunctionorchestrationthroughONAPserviceorchestrator

JIRA:https://lf-onap.atlassian.net/browse/REQ-341

IMPACT: DDF Presentation: https://wiki.lfnetworking.org/download/attachments/40370243/CNF%20Orchestration%20through%20ONAP.mp4?api=v2

Provide CNF orchestration support through integration of K8s adapter in ONAP SO

  • Support for provisioning CNFs using an external K8s Manager

  • Support the Helm based orchestration

  • leverage the existing functionality of Multi cloud in SO

  • Bring in the advantages of the K8s orchestrator and

  • Set stage for the Cloud Native functioanl scenarios to be demosntarted through ONAP

Led by @Seshu Kumar Mudiganti  @Srinivasa Addepalli  @Lukasz Rajewski

 

ETSI Alignment

WIKI PAGE: Guilin release - functional requirements proposed list

and model planning page: ONAP R7 Modeling High Level Requirements

JIRA: https://lf-onap.atlassian.net/browse/REQ-334

IMPACT: Note: if AAI needs some minor schema changes for ETSI modeling, one of the ETSI-Alignment participating companies will update the AAI schema. It is part of the user stories.

@Fernando Oliveira  leading this work.  @Byung-Woo Jun

Multi-Tenancy

WIKI PAGE: ff

JIRA:  https://lf-onap.atlassian.net/browse/REQ-340

IMPACT: Lead @Olivier Phénix  , @Mike Elliott  (AMdocs OOM)

schema, multiple tenant pointing to same A&AI instance. Retreive operate on their own PNFs. (not available in A&AI yet).

How to support multiple ONAP components on same cluster. Access Control. Can't tag PNFs.

Q: U/C & Non-functional Req. U/C help out on NFRs. U/C owner should contribute to some NFRs for components they are working on (TSC guidance). Need resources for "must have" A&AI NFRs. should allocate some space/work to help out.

Q: Yuriry and I have a question about the UI for C&PS. Will it be making enhancements to an existing UI like CDS or is the plan to develop its own?

 

COMPONENT IMPACTS TABLE

The following table shows the impacts of each requirement/use case per component

See also the Release: Guilin Impact View per Component

Use Case

A&AI

AAF

CLAMP

CCSDK

DCAE

EXT API

MODEL

MVIM

OOF

POLICY

PORTAL

SDN-C

SDC

SO

UUI

VID

VNF REQTS

VNF SDK

OOF SON

 

 

 

YES

C&PS

Depend

YES

 

 

 

YES

YES

 

YES

 

 

 

 

 

 

5G Svce

 

 

 

 

 

 

YES

 

 

 

 

 

 

 

 

 

 

 

SD VES

 

 

 

 

YES

 

YES

 

 

 

 

 

 

 

 

 

YES

 

A1Adap

 

 

 

YES

 

 

Possible

 

 

 

 

YES

 

 

 

 

 

 

NRM

 

 

 

YES