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 2 Next »

Date

Attendees

Goals

Discussion items

TimeItemWhoNotes

R5 El Alto Cadence Release Proposal

(EUAG / End-User Advisory Group)

cl664y@att.com

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

Summary: The El Alto release could be shortened

and focus on internal (tech) debt and defect backlogs.

A proposed release cycle is presented.

 

R4/Dublin (M4 Milestone/RC0)

April 25

 Benjamin Cheung

Release Candidate 0 - RCs are to ensure proper alignment and execution on End 2 End Release Test Cases and End 2 End functional Test Cases.

Project Team focused its effort on:

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

R4 Dublin Release Planning Wiki: Release Planning

Score Card: M4 Dublin Release Requirements


PLATFORM TOPICS:

Controller to NF Association

Benjamin Cheung

PLATFORM TOPICS:

Data Persistency

N.K. Shankaranarayanan

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

San Jose presented proposals for next release for R5/R6.

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

PNF PREONBOARDING / ONBOARDING in R5

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:

ETSI SOL001/004/007 with ONAP internal Model

PNFD modeling




Arch S/C

PNF POB/OB Flow


ARCHCOM: InfoFlow - Onboard Resource into SDC Flow





NEXT / UPCOMING Presentation

Edge Deployment







Action items

  •  
  • No labels