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

« Previous Version 6 Current »

Date

Attendees

Goals

Table of Key Presentations/Overviews

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

Former user (Deleted)

Visualizer for A&AI Model Layout

Use Case Realization Call: May 1, 2019

May 8, 2019A&AI Model Browser, Sparky
James Forsyth

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)
Giulio Graziani
A&AI Run-Time Browser
May 22, 2019Edge Automation Overview

Ramki Krishnan

Analytics focus. 5G place RAN CU in specific locations. Low-latency application. Specific Edge Data Center. Management portion. Task for distributed Management components. Onboarding. Distributed Management. Instantiation. Cloud Native Eco system. Central Management system. K8S Based. Leverage same W/F. Distributed Edge with different capabilities & capacities. Different categories. An "umbrella/Core" ONAP consolidate view component Micro-service in all Edge locations. Analytics application distributed across all location, want consolidated view.

Onboarding/Instantiation Resources - Design Flow integration. Config Sync Mechanism (Cloud K8S operator framework). Offloading process: dimensioning exercise. Topology defined. Application delivery. Instantiation association bind to an existing offload application on the edge. Management components are dynamic. Deploy dynamically.

Edge Orchestrator. Heirarchical orchestration. Edge Cache. Edge offload component. Central repository = primary source of truth. SYNC.

A&AI - dependent on the U/C. e.g. analytics off-load on edge. CLAMP may need edge A&AI. Craft persona. K8S design.

URLLC - Closed Loop on the Edge. 5G.

ARCHITECTURE: converging on multiple proposal. Day1 backward compatible. staring Cloud native w/ backward compatible.

W/F - Multicloud Effort. Cloud native deployment of management workloads. central & edge coordination.

Multi-Tenancy - Automatically factored in. Not driving new multi-tenancy req hold true for Edge.

Edge Automation through ONAP Arch. Task Force - Distributed Management (ONAP etc.) components


May 29, 2019Modeling S/C , Use Case Project Teams, Architecture S/C Way of WorkingBenjamin Cheung
Jun 5, 2019


Jun 19, 2019IoT Creation OverviewAtul Purohit




Discussion items


TimeItemWhoNotes

Modeling S/C , Use Case Project Teams, Architecture S/C Way of WorkingBenjamin CheungPresentation

Business Drivers
Benjamin Cheung

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


R5 El Alto Cadence Release Proposal

(EUAG / End-User Advisory Group)

Benjamin Cheung

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.


R4/Dublin (RC2)

May 29, 2019

Benjamin Cheung

Release Candidate 2 - 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


PLATFORM TOPICS:

Controller to NF Association

Benjamin Cheung

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

N.K. Shankaranarayanan

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

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:

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

PM Dictionary/FM MD GUI

marge.hillis
FM META DATA & PM DICTIONARY in R5

USE CASES/5G:

Preonboarding/Onboarding

Benjamin Cheung

Zu Qiang

Michela Bevilacqua

PNF PREONBOARDING / ONBOARDING in R5

USE CASES:

Splitting up PNF & 5G U/Cs

Benjamin Cheung

R5 El Alto Use Case Page:

Release 6 (Frankfurt) proposed use cases and functional requirements

A new General PNF Use Case Page was created

https://wiki.onap.org/pages/resumedraft.action?draftId=60892496&draftShareId=8c48e706-ad4f-464d-84a9-273af806571f

Alla will discuss creating new pages for

Mobile Service Chaining (KDDI): MOBILE SERVICE CHAINING

IoT Service Creation


USE CASES:

Modeling gNB/5G RAN

Thinh Nguyenphu (Unlicensed)

Benjamin Cheung

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.

Follow-up Call Tue Apr 30, 2019


Arch 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


IoT Service Creation
Atul Purohit

IoT Create Services on 5G

5G Use Cases in R6 Frankfurt

Jun 19, 2019


O-RAN Modeling & alignment with ONAP

Tracy Van Brakle

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.

Discussion to add a "gold standard" for 5G. Augmenting data within the information model.


OOF/PCI
N.K. Shankaranarayanan

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

Code still need to be integrated. Jira SDN-C (Dan Timoney) pushed El Alto (the Maintenance Release).

3rd party operational domain manager.

Action items

  •  
  • No labels