Page Comparison

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.

Apr 18, TSC called a Vote for resolution of R5 release

R4/Dublin (

RC0)

April 25, 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

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

• 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 R5 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://

lf-onap.

atlassian.

net/wiki/download/attachments/

16362101/BBS_R5_v1.pptx?version=1&modificationDate=1554180715000&api=v2

USE CASES/5G:

PM Dictionary/FM MD GUI

USE CASES/5G:

Preonboarding/Onboarding

USE CASES:

Splitting up PNF & 5G U/Cs

R5 El Alto Use Case Page:

Release 5 (El Alto) 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:

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

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

Modeling S/C decompose the A&AI data model

A&AI developer Model Browser

NEXT / UPCOMING Presentation (Mid-May)

Edge Deployment

Ramki will be presenting on Edge Deployments in upcoming meetings (contacted)

Mid-May after Arch presentation

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.

Attributes similar with LTE. 5G Architecture evolution.

Modeling Harmonization Discussion

(Audio Only M4A)

Apr 23, 2019

Modeling Harmonization Discussion

(Audio Only M4A)

Apr 23, 2019

Modeling Harmonization Discussion

(Playback M3U)

Apr 23, 2019