Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

Date

Attendees

Table of Key Presentations/Overviews

DATETOPICPRESENTERDESCRIPTION
Apr 10, 2019Controller LCM API 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

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

May 1, 2019A&AI GraphGraph Visualizer

Visualizer for A&AI Model Layout

Use Case Realization Call: May 1, 2019

May 8, 2019A&AI Model Browser, Sparky

A&AI developer Model Browser to navigate and viewing attributes, object types & edge view

Recording & Slides: Use Case Realization Call: May 8, 2019

May 15, 2019A&AI Run Time Browser (Sparky)A&AI Run-Time Browser
May 22, 2019Edge Automation Overview

Central & Distributed Edge ONAP configuration.

Topics include: Onboarding, Instantiation, Edge Orchestration, A&AI, Architecture, Work-flows, Multi-Tenancy

Use Case Realization Call: May 22, 2019

May 29, 2019Modeling S/C , Use Case Project Teams, Architecture S/C Way of Working

Model S/C (Sub committee) contributions page:

Modeling sub-committee Contributions

https://wiki.onap.org/display/DW/Proposed+ONAP+Release+Process+Updates+for+Information+and+Data+Modeling

Jun 5, 2019Use Case slides for Dev. ForumBenjamin CheungUse Case Realization Call: June 5, 2019
Jun 12, 2019(No Meeting)Developer's Forum(No Meeting)
Jun 19, 2019

Discussion of U/C items
Jun 26, 2019PNF Software Upgrade

ONAP Read the Docs/R4 Announcements

PoC

Demos





Discussion items


TimeItemWhoNotes

Business Drivers

Discussion of Business Imperatives added to Use Case Pages

From U/C S/C call on Monday May 6

See example from PNF PNP and PNF Pre-onboarding/onboarding

5G - PNF Plug and Play

PNF PREONBOARDING / ONBOARDING in R6 Frankfurt

BUSINESS DRIVERS TEMPLATE:

Business Driver Template for Use Cases


R5 El Alto Cadence Release Proposal

(EUAG / End-User Advisory Group)

https://wiki.lfnetworking.org/display/LN/EUAG+2019-04-09+meeting+minutes

Summary: The R5 El Alto release could be shortened and focus on internal (tech) debt and defect backlogs. A proposed release cycle is presented.

El-Alto Release Requirements


Agile Process vs Waterfall Process
Will ONAP move to a an Agile Sprint-based process vs Waterfall Process

R4/Dublin (RC2)

May 30, 2019

Release Candidate 0 - End 2 End Release Test Cases and End 2 End functional Test Cases. Project Team focused its effort on:

  1. TESTING - integration testing (complete Health Check and Pair Wise Testing)
  2. DEFECTS - closing high priority defects
  3. DOCS - supporting Documentation team

R4 Dublin Release Planning Wiki: Release Planning

Score Card: M4 Dublin Release Requirements

testing & Integration status: Dublin Release Integration Testing Status

RC2 passed (TSC Jun 6 2019)


PLATFORM TOPICS:

Controller to NF Association

R5/R6 Topic

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

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


PLATFORM TOPICS:

Data Persistency

STATUS: Work for ConfigDB completed, not merged in R4

Dan Timoney moved to R5, one Jira for ConfigDB. One issue about merging.

ONAP code added can take a test ONAP deployment to have the ConfigDB work.

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


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

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:

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

FM META DATA & PM DICTIONARY in R5

USE CASES/5G:

Preonboarding/Onboarding

PNF PREONBOARDING / ONBOARDING in R5

USE CASES:

Modeling gNB/5G RAN

Align, harmonize, reconcile various information models to ONAP model:

Expand & verify model and harmonize with the ONAP internal information & data model:

ETSI SOL001 ... 007 with ONAP internal Model

PNFD modeling (Model S/C)

5G Model (3GPP)

ORAN (WGs)

Open ROADM (reconfig optical add/drop multiplexer)

ONF

ISOMII

OTCC (Optical transport config & control)

 - Use Cases that need transport models need some model consistency.

 - Try a Use Case with extended ONAP model & real equipment.


Arch 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


A&AI - Model Browser

A&AI updates - presentation given Jun 5 2019 about new views being developed in A&AI.

Recording - 2019-06-05 AAI Meeting Notes

graphgraph + model browsers. (Pavel in progress)


IoT Service Creation

IoT Create Services on 5G

5G Use Cases in R6 Frankfurt

June 19, 2019


O-RAN Modeling & alignment with ONAP

Tracy Van Brakle

Melanie Sater

work with Open RAN alliance availability of 3GPP baseline (that vendor & operators agreed upon) add to ONAPs information model and expand existing management I/F for CM management.

want to plug them into ONAP and facilitate the 5G and other use cases working these open I/F specifications. For El Alto WG-1,3,6. Configuration management NetConf YANG specification derived from info model aligned w/ 3GPP RM & existing 3GPP info-model. Papyrus. Which 5G U/C good candidates verification w/ evolving model. PNF PnP/OOF?

Near Real Time RIC. WG-4 open Front Haul.

In PCI/SON U/C - the SDN-R Interaction w/ RAN simulator is Netconf/YANG based. In R5 we could see what parts of the model would come from ORAN

May 15 2019 Update:

Early stage information model that pre-dates O-RAN and was used for PCI use case with ONAP rel 2 Beijing is being carried forward to O-RAN O1 CM interface specification; refer to https://wiki.onap.org/download/attachments/28382769/RAN_Info_Model_Rel_0.pptx?api=v2

Attributes similar with LTE. 5G Architecture evolution.


New Use Case in 5G for RAN 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).

Use Case WIKI: MOBILITY STANDARDS HARMONIZATION WITH ONAP


New Use Case in 5G for Licensing ManagementTimo Perala

New U/C added to the 5G Use Cases for Licensing Management

Use case Wiki: LICENSING MANAGEMENT


OOF/PCI

PoC U/C will happen in WinLab. to meet time lines do those parts in Wind river focusing on DCAE, Policy and OOF.

Jira SDN-C (Dan Timoney) pushed El Alto (the Maintenance Release).


Developers Forum (R5/R6) Sweden
https://wiki.lfnetworking.org/display/LN/June+2019+LFN+DDF+Schedule


SUPPORTING DOCUMENTATION

DocumentFile
R6 Use Case Analysis & Cross-Interaction Matrix

RECORDING

RecordingFILE
Zoom Video & Audio (MP4)

Audio Only (M4A)

Playback (M3U)

Chat (Txt)

Action items

  •  
  • No labels