Page History

1. 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.
3. Model Planning for R7 ONAP R7 Modeling High Level Requirements

PLATFORM TOPICS:

Controller to NF Association

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

PLATFORM TOPICS:

Data Persistency, RunTime DB

PLATFORM TOPICS:

Controller LCM API Evolution

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

• 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 CASE/5G:

RAN (ORAN-3GPP) Standards Harmonization with ONAP

• Orchestration at the Edge.
• A1/O1/E2 communications. Edge to ENBs, Telemetry.
• E2 will not have this info. O1 is I/F for PM counts. Not a management I/F.
• WG3 (ORAN) is defining this.
• ONAP w/ O1. Changes w/ O1 interface.
• How to satisfy A1/O1 and in what time-frame.
• U/C ORAN - ONAP harmonization. 3GPP ORAN ONAP.
• Starting a new U/C in 5G. Marge, Vimal, Fred Feisullin
• Edge inventory & topology. Transport BH consideration w/ real-time near-RT aspects
• Akraino. MEC. Edge automation (Ramki).
• VES Listener Review completed version 7.1.1; Add version 5.4.1. CMNotify version 7.2 https://onap.readthedocs.io/en/latest/submodules/vnfrqts/requirements.git/docs/Chapter8/ves7_1spec.html  ; https://onap.readthedocs.io/en/latest/submodules/vnfrqts/requirements.git/docs/Chapter8/VES_Registration_3_2.html

Use Case WIKI: MOBILITY STANDARDS HARMONIZATION WITH ONAP

USE CASE/5G:

Licensing Management

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 CASE/5G:

OOF / SON / PCI

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

and also integration with Runtime DB work.

USE CASES:

BBS U/C Evolution

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/5G:

PM Dictionary/FM MD GUI

USE CASES/5G:

PNF S/W Upgrade

USE CASES/5G:

Preonboarding/Onboarding

PNF PREONBOARDING / ONBOARDING in R5

VNF-SDK Artifact package security

IoT Service Creation

IoT Create Services on 5G

5G Use Cases in R6 Frankfurt

June 19, 2019

USE CASES:

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:

5G NRM (Network Resource Model) Configuration

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

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

USE CASES:

PNF / Plug and Play

Architecture S/C

PNF POB/OB Flow

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:

PoC Definition

TSC/USE CASES:

Test Automation Progress

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.)

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

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 Component Descriptions:

ONAP Architecture Component Description - Dublin

Architecture Flows:

Dublin ONAP Information Flows

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

• READ THE DOCS: https://onap.readthedocs.io/en/latest/index.html
• Navigate to > USER GUIDES > Verified USE CASES
• Use Case Page: https://docs.onap.org/en/dublin/submodules/integration.git/docs/docs_usecases.html
• Doc PTL Sofia Wallin  - Ask Sofia to help w/ training. OPEN POINT.
  • Doc TEAM meets at 8AM EDT USA on Thursdays. https://zoom.us/j/907176290

"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