13 Mar 2019

Attendees

START RECORDING

Discussion items

Time

Item

Who

Notes

15 min

A&AI Platform Evolution Items

James Forsyth

A&AI Schema Change

PNFid

-PNF-id vs PNF-name

PUSH TO R5 EL ALTO. Discussion Will be loaded to Mar 6, 2019 U/CR call.

AAI-2148 - Change key on PNF object from pnf-name to pnf-id Open

(0) ARCHITECTURE - Review with Architecture Sub-Committee. Recommendation to implement in R5. Start early in R5.

(1) RELEASE NOTES - to follow new rules , give clients notice that a breaking change comes in the next release. Add a release note to R4/Dublin Release to call out. So people mitigate need for migration.

(2) MIGRATION STRATEGY - will in R5, all the objects will have the key as the name. Id will have to be vetted, detect duplicates. Migrate the URIs. Warn, Migration strategy. If there are more "regular" LARGE A&AI Schema changes need a process to introduce changes. Names vs UUIDs, there might be others that would also require migration.

(3) SOCIALIZE - Socialize as breaking change as far back as it goes. Jimmy has contacted key players to inform that this has been delayed.

(4) MODELING & U/C COMMITTEE - Modeling sub-committee. Produce UML based on A&AI data model with papyrus model that modeling sub-committee can use, way we can talk about it so committee can. Widespread understanding of how A&AI is modeled and how keys work.

15 min

BBS U/C Platform evolution

BBS Use Case in R4.

A&AI SCHEMA CHANGE - (Resolved with BBS U/C, it will use an Edge to Logical Link instead of a A&AI Schema change)
PnP WIKI - Plug and Play Wiki needs to be updated. Update PnP-6230
Requirements impacts
REQUIREMENTS UPDATES - CP authenticated, triggers registration of PNF & tunnels. PNF sends confirmation notification/message. additional event from state change. Review VNFRQTS to see if there are updates. VNFRQTS - Vendor interfaces to Vendor products. 1. VNF 2. PNF. (none to 3rd party controllers). Focused on mainly how the VNFs should be orchestrated (HEAT templates, resources, #ports, IP, VM). From VNF RQTS intent what are the proper scripts to orchestrate and what are resources needed to assign to VNF. This is addressed by PNF registration. Identified gaps in PNF registration was implemented new requirements not specific to BBS.
3RD PARTY CONTROLLERS - PNF requirements that are "must" requirements that don't make sense for a 3rd party controller. Section to specify the type of controller a PNF is using.
STANDARD FORMAT - BBS first U/C. "standard format of the flow", set of sequences & interaction to execute a U/C. Req insures ONAP can run on an ONAP structure. Domain specific controllers interacting w/ PNFs.

PNF Software Upgrade

Use Case (Scope Change)

Ulas Kozat

Huawei is leading the new (re-scoped) PNF Software Upgrade with Ansible.

Created new Jira tickets in SDN-C. PTL Ajay has committed.

API defined, Req, Integration. Roll-back testing. Reuse of Casablanca Tests.

Platform Evolution for

Data Persistency

N.K. Shankaranarayanan

MariaDB and platform evolution for run-time persistent configuration information. Used in the OOF/PCI U/C. DCAE Post-gress DB. Primary inventory in A&AI. Base another database off of that. ConfigDB doesn't publish updates. PCI U/C if SDN-R knows of a config change it updates. SDN-R publishes changes on DMaaP. Network Maps & Topology & History. Timestamp. Controllers keeping state of network.

Firewall U/C carry-over to R4R3

t

SOL005

I opened epic

Image RemovedAAI-2194 - Support ETSI NFV-SOL 005 (Os-Ma-Nfvo ref point ) between SO & VF-C/NFVO Open to start tracking the SOL 005 Fw U/C

The A&AI Jira is

Jira Legacy

server	System Jira
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	4733707d-2057-3a0f-ae5e-4fd8aff50176
key	AAI-2204

PM Dictionary Schema GUI display

marge.hillis

Benjamin Cheung

Focus is on making the FM Meta-Data GUI work first. PM dictionary "stretch goal".

Scope Change:

SDC-2095 - R4 5G U/C SDC: PM Dictionary GUI Display from PNF Onboarded Package Open

PNF Pre-Onboarding & Onboarding Use Case

Zu Qiang

Michela Bevilacqua

Benjamin Cheung

ETSI SOL001/SOL004 extension PNF

Modeling PNFD.

Mapping onboarding PNFD and ONAP "Platform" info/data model

Requirements work. Package requirements Section 7.2.

NFV meeting introduced not-backward compatible change in SOL004 2.6.1, adding delay to the project. Updates to the TOSCA Meta and the Manifest File, NFV CR NFVSOL(18)000746r3 CR review will be held Mar 14, 2019.

VNF-SDK Development Updates.

SO (Service Orchestrator) Service Instantiation Flow

Developing a SO Service Instantiation Flow

RAN Network Slicing Examples

Borislav Glozman

guochuyi

Discussion RAN Network Slicing Examples

PNF Plug and Play Requirements Work