USE CASE REALIZATION MEETING (Notes 2019-02-20)

PNF Software Upgrade U/C

@Ulas Kozat

• SA5 (3GPP TS32.532) -

• AUTOMATED SW Mgmt (ASWM) (Operations) listSwMCapabilities, listSwMProfiles, createSwMProfile changeSwMProfile deleteSwMProfile listSwMProcesses resumeSwMProcess terminateSwMProcess swFallback (Notifications)

• Non-Automated SW Mgmt (NASWM): (Operations) downloadNEsw activate NESw installNESw listSwmProcess, CancelNaswmprocesses (Notifications)

• Supported LCM:upgrade-pre-check, LCM:upgrade-software LCM:upgrade-post-check

• R4: Rollback API support for xNF

• API and playbook enhancements for S/W upgrade based on 3GPP S/W management API enhanements

• PNF S/W upgrade workflow design and test (Stretch goal)

PNF A&AI Schema Change

@James Forsyth

Raised at PTL call and onap-release & discuss list.

Large change that goes back to Amsterdam to PTLs need to be coordinate

This is a non backward compatible and breaking change.

Proposal to Change AAI PNF Entity to use PNF-ID as key

MIGRATION STRATEGY: Embedded objects that already exist between casa/dublin.

Currently A&AI team looked at this other migrations that have been done in ecomp.

RISK R4: Migration

Can we get community support around dev. effort on migration piece

Aligning PNFs & VNFs both use "ID" as their indexing key. Today VNF are using IDs. PNFs are using "names"

BBS A&AI Update

@James Forsyth

AAI-BBS Proposals for Dublin Release#BBSProposalsforDublinRelease-Item3.ExtrafieldinPNFtoassistnomadicONTscenario

AAI-2151 - Add attachmentPoint attribute to PNF to support BBS use case

Chandra suggested a node relationship instead of keeping a string value in A&AI. Model it as another vertex. create edge & other vertex to represent link. Create Edge.

Stavros: this might work, need to discuss w/ BBS U/C team. String to keep attachment point information. might not need an A&AI schema change.

M2 Milestone

(General)

Functionality freeze, no new visible functionality is to be added to the current ONAP release.

Each Project team has defined and documented their Functional Test Cases.

The vendor equipments have been delivered.

A stable document describing the API is documented and available in wiki.

Base set of impacts to VNF Requirements identified by use case/ project.

Feb 21, 2019 - might be delayed by a week because M1 milestone

Upcoming Presentations

FM MetaData GUI R4

PM Dictionary GUI R4

Scaling U/C (Overview, Platform & U/C Interactions) 10:30 AM

A&AI Schema change to pnf-ID

Proposal to Change AAI PNF Entity to use PNF-ID as key

Zoom file (MP4)

Audio Only (M4A)

Chat (Txt)

Playback (M3U)