Page Comparison

N.K. Shankaranarayanan

Joanne Liu Rudel

Benjamin Cheung

marge.hillis

Vimal Begwani

fred feisullin

Timo Perala

Samuli Kuusela

David Perez Caparros

Tim Carey

Chaker Al-Hakim

Zu Qiang

wangyaoguang

Benjamin Cheung

Zu Qiang

Michela Bevilacqua

Thinh Nguyenphu (Unlicensed)

Benjamin Cheung

Melanie Sater

Tracy Van Brakle

Martin Skorupski

Benjamin Cheung

Benjamin Cheung

Alla.Goldner

Benjamin Cheung

Alla.Goldner

James Forsyth

Former user (Deleted)

VID: Service Models browser - display orchestration type (macro / a`la carte) use-case.

This use-case requires us to extend the AAI data-model, with an additional field, related to Service Model.

This field will be used later on to indicate in VID the Service Model orchestration type.

A&AI Epic 2594

Modeling a 5G Service may require expansion of A&AI fields for PNF.

Benjamin Cheung looking at 3GPP TS28.540 and 3GPP TS28.541 model & network resource model (NRM) will analyze the model and present to Modeling Subcommittee & 5G U/C subcommittee ... possibly A&AI schema impacting?

SUMMARY: No S/W A&AI impact in R6 only Modeling work in R6.

Wiki Page: 5G Bulk PM in Frankfurt/R6

Ensure A&AI can generate necessary events related to xNF instantiation and removal

SUMMARY: Needs investigation. Mark Scott

Wiki Page: OOF (SON) in R5 El Alto, OOF (SON) in R6 Frankfurt

OOF/SON/PCI Enhancements.

Models & relationship between Config, Operational DB & AAI

(Spreadsheet/Use Case Team): Cell Addition Management.

(Oct 10 2019 discussion): Cross dependency with RunTime DB Use Case. Add info into PNFName & PNFID in A&AI. Will this just be "usage" of A&AI or will there be additional schema changes or A&AI code changes or is this just Test Only? Reuse of Existing Objects. New objects related automatically flow to A&AI event topic on DMaaP.  Where is the topic & Payload.

CONTACTS: N.K. Shankaranarayanan ,  Swaminathan Seetharaman

SUMMARY: (Oct 10, 2019) No A&AI schema change or A&AI code change for R6. CLOSED

Wiki Page: NETWORK SLICING PoC in R6 Frankfurt (Obsolete)

Update A&AI schema with Network Slicing model. Merged proposal presentation (CMCC & AmDocs) have been given at Architecture S/C ( 29 Oct 2019 ) and at Alla's call 28 Oct 2019 

UPDATE: 30 Oct 2019 : For the E2E Network Slicing use case for Frankfurt Release, we intend to leverage the nested service model work that has been going on since Dublin release. From A&AI perspective, we foresee that the schemas would have to be enhanced to cover network slicing models. We have considered A&AI to be a stretch goal for Frankfurt, though we are committing resources. So, we would like to start the discussion in the coming weeks, and subsequently implementation work to try our best to complete the implementation for Frankfurt. AAI-2600 has been created just to indicate the SDC impacts, we will update it with more details, and also join the A&AI weekly call during the next 1-2 weeks to discuss further.

It is also noted in the release requirements page as A&AI: Code Change. Frankfurt Release Requirements

SUMMARY: Tracked by A&AI 2600. Presentation: Use Case Realization Call: November 20, 2019

Wiki Page: 5G CONFIGURATION (RunTime DB) CONFIGURATION PERSISTENCE SERVICE R6

Epic #1 Run Time DB introduction

E1: INITIAL SETUP - A&AI Provides initial physical inventory info to RunTimeDB. Initial setup of physical inventory (PNFs) and initial configuration of RunTime DB should sync with A&AI. GetAllPNFs function from A&AI on startup. This function allows you to query for all of the elements currently in A&AI. This Get (all PNFs) API (Direct API call to A&AI). If there is a very large network, paging support (to get a set at a time). Produce an export of database (as a 1-time process).

Epic #2 Run Time DB Sync

E2: xNF OBJECT UPDATES - When a new xNF appears in the system, the RunTime DB needs to update its records to reflect the newly appearing or disappearing xNF. In theory A&AI posts a DMaaP notification that there is a change in xNF status and RunTime DB S/W subscribes to this topic and can update its records / database. Need to verify discuss with A&AI.

Discussion: No A&AI Jira ticket needed. To use the system properly: get credentials for AAF. Maybe onboarding from SDC. When you onboard the config changes to allow for a certain MAC id. This is all in AAF. on AAI side include them in AAI roles / traversal & resources. Bootstrap data in AAF to be updated. necessary to interact with any component; getting credentials into AAF is for general use across the systems.

SUMMARY: No A&AI S/W Impact.

•  James Forsyth 09 Oct 2019  ACTION: (CLOSED) Find some documentation on A&AI usage. 30 Oct 2019  Jimmy preparing the document. Met with the team: RunTime Config DB Meeting notes Nov 1, 2019
•  Joanne Liu Rudel 09 Oct 2019 ACTION:  will call a meeting to discussion with A&AI team. Ben has setup regular "team" meetings for this U/C. Fridays at 9 AM https://zoom.us/j/230322363

PNF State Transition management for BBS, description: https://wiki.onap.orglf-onap.atlassian.net/wiki/download/attachments/6088750416362101/BBS_R5_v1.pptx?version=1&modificationDate=1554180715000&api=v2

State Transition Diagram (Working Draft)

(Spreadsheet/Use Case Team): Indicates impact

Update 30 Oct 2019 Did not foresee requirement, but needs to review first. We are currently reviewing the list of items we found in the BBWF BBS testing and once we sort through them we will communicate the results back to ONAP community. Regarding AAI specifically, we do not foresee any new requirements for Frankfurt, but we would like to conclude the review first before jumping to final conclusions. Stavros Kanarakis

SUMMARY: Needs investigation (See update)

A&AI Schema changes

1. For "network-resource", add string "network-type" attribute.
   1. Has enumerated values e.g. ETH topology or OTN topology.
2. For "pnf", add boolean "is-abstract" attribute.
   1. Has "false" value by default.
   2. Set to "true" value to represent abstract node, i.e. group of PNFs abstracted and presented as a single node by domain controller.
3. For "logical-link", new enumerated values for "link-type" attribute, e.g. intra optical domain, inter optical domain, or inter operator domain.
   1. For "p-interface", add integer "inter-domain-plug-id" attributes.
4. Has discovered values based on IETF specifications, for correlation between related objects in ETH topology and OTN topology.
5. For "p-interface", new enumerated values for "interface-type" attribute, e.g. "Tunnel Termination Point".
6. Add new resource "uni".
   1. Has termination point and cvlan attributes.
   2. Add EdgeRule to represent uni to p-interface relationship.
7. Add new resource "label-restriction".
   1. Has discovered vlaues for label restriction attributes e.g. priority, range type, label start, label end.
   2. Add EdgeRule to represent te-link-attributes to label-restriction relationship.
8. Add new resource "te-link-attributes"
   1. Has discovered values for te link attributes, e.g. isAbstract, link protection type, access type.
   2. Add EdgeRule to represent logical link to te-link-attibutes relationship.
9. For "pnf", add new attribute "supporting-node" attribute.
   1. Has discovered value based on ETH topology and OTN topology
   2. Add EdgeRule to represent pnf to pnf relationship described by "supporting-node" attribute.
10. Add new resource "tunnel-termination-point"
    1. Has discovered values for TTP attributes, e.g. TTP-id, admin-status, oper-status, protection-type, inter-layer-lock-id.
    2. Add EdgeRule to represent tunnel-termination-point to p-interface relationship.

CCVPN Use Case in Frankfurt Release

SUMMARY: Needs Investigate (Huawei)

Have done some prototyping in to ingest topology from external controllers and show them in A&AI. Will need more work to act on notifications from controllers and keep the topology in sync.

Wiki: Multi-domain Optical Network Services

(Spreadsheet/Use Case Team): Indicates impact

SUMMARY: Needs investigation of AAI-2623 (Epic). Resource models changing. It will be A&AI schema changes only, no A&AI S/W impact.

According to Srinivasan Ramanathan he will be contributing a new custom query and schema changes

Base line: NFD (Node feature discovery) from K8S CNCF project. Discovery of hardware features,  creation of profiles and populating in A&AI of compute flavors.

From the Frankfurt Release Requirements page it lists as Test-Only and supported (tested) by Intel.

SUMMARY: Needs investigation. (No responses as of Oct 30).

•  04 Nov 2019 Ben will mention on Alla's Monday call. Alla's call resuming Mid-December

Wiki Page: K8S based Cloud region support (Continue from R4)

Does this impact A&AI? Continuous monitoring (using Kubernetes APIs) and updating the DB with latest status and resources allocated.

(Spreadsheet/Use Case Team): Indicates impact

SUMMARY: Needs investigation TEST ONLY (Confirmed). Assessment - Likely to use A&AI API not a code change.

No Impact to A&AI discussed 06 Nov 2019  Jira Ticket AAI-2673 will be closed.

A&AI Impact analysis underway via PoC

see Wiki Page: Third-party Operational Domain Manager

Gets CFS instance from SO and RFS instance update from 3rd party.

(Spreadsheet/Use Case Team): Indicates Test only impact

SUMMARY: Needs investigation Confirm Test Only.  Atif Husain no A&AI impact. Storing service instance details, reuse service instance object. No Schema change. CLOSE AAI-2674