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

Compare with Current View Page History

« Previous Version 3 Next »

Date

Attendees

Goals

Discussion items

TimeItemWhoNotes
R5 El Alto Use Case DiscussionBenjamin Cheung
 A&AI Schema Changes for R5 El Alto (ESR, Complex, PNFid/PNFname) James Forsyth

ESR (external NMS) - EMS/NMS + ONAP.

Complex (Cloud Region ID/Home) - (verify with Jimmy)

PNFid/PNFname

New A&AI parameters for xNF.

Physical Location, Location within system (Cloud location)

Complex Wiki:

https://wiki.onap.org/pages/viewpage.action?pageId=25431491


BBS U/C Platform evolution

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

Slide set linked in R5 proposed U/C.

List of proposals & functional requirements.

https://wiki.onap.org/download/attachments/60887504/BBS_R5_v1.pptx?version=1&modificationDate=1554180715000&api=v2


San Jose DF Discussion

https://wiki.onap.org/display/DW/2019+Silicon+Valley+Meeting+Proposals


M4 R4 Milestone discussion

TSC M4 Score Card

R4 Dublin M4 Milestone April 11, 2019 (Tomorrow)

Release Planning


Platform Evolution for Data Persistency (R-future)

N.K. Shankaranarayanan

Controller to NF Association (R-future)Benjamin Cheung

Firewall U/C in R4/R5Bharath Thiruveedula

PM Dictionary, FM Meta Data GUI evolution

R4 FM Initial GUI will be available, that work is underway. Only able to present fields are defined in VES events. Will need evolution in a future release and updates in the next releases.

3GPP release which integrates VES events into 3GPP.

PM - change structure of defined VES event provided working discussions to talk about modifying to have each measurement be its own record in the VES file. Better organized information for GUI to pull into a policy engine. Modify and create a proposal.

Requirements for PM / FM are completed.

FM META DATA & PM DICTIONARY in R5


PNF S/W Upgrade U/C R5

Netconf focused.

PNF SOFTWARE UPGRADE in R5


ETSI SOL001...SOL007 Modeling

PNF Pre-onboarding/Onboarding U/C in R5PNF PREONBOARDING / ONBOARDING in R5

Network Slicing in R5

LCM PNF API evolutionOskar Malm

(1) Evolution of LCM APIs.

A single LCM API definition YANG and implementation in CCSDK.

Usable by APPC SDNC and future CCSDK controller personas

Backwards compatible for API clients

Implementation & API handler is different, and to converge to a single implementation.

Avoid duplication of Effort.

Converge in CCSDK and different controllers would import modules and their APIs would have consistent behavior.

Consistent way of indicating PNF as target in API requests for applicable LCM operations.

Full support for PNFs throughout LCM implementation in CCSDK.

(2) CDS Blueprint Processor

Customize operations. Run-time component. Used for pre/post instantiation. Generic component which capabilities for LCM U/C.

SO / CDS blueprint Processor

NB API (Validate, Lock/Transactions, Dispatch) > CDS Blueprint Processor (W/F & Scripts, Component Functions)


R5 El Alto Cadence Proposal (EUAG / End-User Advisory Group)


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.









Action items

  •  
  • No labels