Use Case Realization Call: July 15, 2020

Use Case Realization Call: July 15, 2020

Date

Jul 15, 2020

Attendees

  • @Benjamin Cheung (Nokia)

  • @Vijay Kumar

  • @Dan Timoney

  • @Zu Qiang

  • @David McBride

  • Marge Hillis

  • Melanie Sater

  • Raghavan Subramanian

  • Chris Rapposelli-Manzo

  • x

DISCUSSION ITEMS LOG

 

Ctgry

Item

Who

Notes

Meeting Notes Discussion

  1. DCA&E team with Use Case Discussion

  2. 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:

PNF S/W Upgrade

@Zu Qiang

@wangyaoguang

R7 Support xNF Software Upgrade in association to schema updates

Use Cases

USE CASES/5G:

Preonboarding/Onboarding

@Benjamin Cheung

@Zu Qiang

@Michela Bevilacqua [Ericsson]

R7 PNF Pre-onboarding / (onboarding)

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

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

R7: R7 PNF Plug and Play PnP

TSC

TSC/USE CASES:

Test Automation Progress

@Benjamin Cheung

@Alla.Goldner

Use Case Test Automation

Action Items: Use case subcommittee to provide current percentage of testing automation regarding your use case and functional requirements

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

Demos

Plug- fest

Demo Plugfest

@Tracy Van Brakle

@Marci Haas

@Martin Skorupski

POC & Plugfest in September 2020

WINLAB? A1/O1 ORAN & ONAP Joint Plugfest

Panel Discussion -

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

Architecture Topics

Architecture Topics

All Team Members

Architecture Component Descriptions and Architecture Flows: https://safratech.net/onapdocs/

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

Use Cases

Req / Use Case Way of Working Process (WoW)

All members

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

 

DCA&E Use Case Analysis

DCA&E impacts w/ use cases and requirements

R7 Release tracking PER component impact:  Guilin Impact View per Component

R7 Cross-interaction table: Guilin (R7) - Use Cases (and Requirements in Use Cases)

USE CASE

REQUIREMENTS

DESCRIPTION & DISCUSSION

USE CASE

REQUIREMENTS

DESCRIPTION & DISCUSSION

CMPv2 ENHANCEMENTS

WIKI PAGE: R7 Certificate Management Protocol (CMPv2)

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

IMPACT: in discussion w/ @Pawel Baniewski  this feature had AAF dependency

but AAF doesn't have PTL, so containers will be R6 only (no new software)

Will use the R6 version of AAF cert-service container, no code impact but DCAE  can progress.

DCAE team requests output artifacts should be configurable (P12, PEM)

DCAE Micro-service onboarding & design (MOD) - Work Internal to DCAE. Component specifications modified to accommodate parameters to execute the client, with certificate details. In DCAE changed deploying applications collectors, servers, analytics – understood by DCAE only, cloudify blueprint created and DMaaP configuration to deploy the service and connected w/ DMaaP topic. JSON/YAML internally to DCAE. Micro-service onboarding artifact. DCAE MOD. Cloudify Manager (Development)

OPEN - two ways ext. jks files from AAF. initial work, come back on how to resolve that.

OOF SON PCI USE CASE

WIKI PAGE: R7 OOF SON Use Case

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

IMPACT: enhancement to SON handler.

  • SON based on data/KPI analysis

  • CLC interaction

  • Machine Learning (ML) aspects in DCAE

(discuss w/ SON team) @Swaminathan Seetharaman

3GPP ORAN ONAP

STANDARD DEFINED VES EVENT

WIKI PAGE: ONAP/3GPP & O-RAN Alignment-Standards Defined Notifications over VES

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

IMPACT: New Standard Defined (stndDef) VES event for DCAE VES Collector. Uses VES 7.2 standard.

Some of it has started and Progressing. Followup item will be presenting Jul 15, 2020

Dependency on ORAN-3GPP team publishing schema expected to be used by R7

Specs were just updated, this should be its next priority available in July 2020.

From ONAP PoV need to doc ext.schema & spec that will be supported go into VNF-REQ project.

A note stdDef, these are the ext. schema being supported by VES. New Schemas made official incorporate into DCAE VES

collector for secondary validation. @damian.nowak  initiated w/ standards Reps. Marge will follow up for deliveries.

Need by M2/M3 API freeze milestone. Crossing ONAP & O-RAN. Due: Aug 6, 2020 

Presenting show a possibility of Mapping new standard def events into existing Fault-file ready, heartbeat VES events.

transformational mapping inc. mapping mS into R8 or beyond.

showing HOW it could be done, not proposing actual S/W deliveries until R8 beyond.

VES 7.2 reviewed and approved in May appears in readthedocs.

E2E Network Slicing

WIKI PAGE: E2E Network Slicing Use Case in R7 Guilin

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

IMPACT: Key contact: @Swaminathan Seetharaman

Configuration & Persistency Service

WIKI PAGE: Configuration & Persistency Service R7

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

IMPACT: C&PS PoC is USING the StndDef VES Event. (test only??)

Data from DMaaP, NameSpace 3GPP-Configuration (DMaaP topic)

Coordinate become from DCAE and when the C&PS PoC can USE & Test ... @Tony Finnerty  & @Toine Siebelink

Bulk PM / PM CONTROL Extensions

WIKI PAGE: Bulk PM/ PM Data Control Extension

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

IMPACT: Dedicate discussion

Intent Based Networking

WIKI PAGE: Intent-Based Network

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

IMPACT: Contact @Huang ZongHe . Presented at the Architecture S/C. Possibly moved to POC status:

Linked to:  Arch S/C recordings: ONAPARC 2020 Meetings

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

Discussion w/ China Telcom ... questions still to be reviewed.

MDONS EXTENSION

WIKI PAGE: (NONE)

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

IMPACT: Test ONLY. @Xin Miao   has been in contact with Vijay.

VES flow. VES mapper. would not need code change. Initially thought.

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" DCAE NFRs. should allocate some space/work to help out.

NFRs

Description

NFRs

Description

 

Guilin release - non-functional requirements proposed list#ONAPmustcompleteupdateofthejavalanguage(fromv8-%3Ev11)

 

See non-functional requirements R7 page;

Guilin Impact View per Component

 

 

 

FR=N NFR=N

 

FR=Y NFR=N and FR=N NFR=Y

 

FR=Y NFR=Y

 

 

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

 

 

 

 

 

 

 

 

 

Possible

 

 

 

 

E2ESlice

YES

 

 

YES

C&PS

Depend

YES

YES

YES

 

YES