2020-07-29 AAI Meeting Notes

AAI CNF Modeling

OPEN

AAI ← link to the AAI weekly CNF call. This team will be doing modeling work to decide how CNFs will be modelled in AAI

aai/oom chart

Currently AAI manages our own helm chart as a submodule of oom, at Frankfurt release sign-off, the oom team will pull the aai charts back into the main repo.  We will still have to maintain the aai/oom repo in case a patch is needed for elalto or frankfurt. 

Jimmy contacted Sylvain on this topic, requesting they (oom team) handle this work and we support, awaiting response. 

Guilin requirements

OPEN

AAI R7 Guilin Release: TSC must have requirements

AAI R7 Guilin Release: Functional Use Cases 

Requirements for inclusion of GraphGraph in Guilin release

OPEN

List goes here

Open Jira tickets as tasks for G release

https://lf-onap.atlassian.net/browse/AAI-2910

https://lf-onap.atlassian.net/browse/AAI-2911

https://lf-onap.atlassian.net/browse/AAI-2912

https://lf-onap.atlassian.net/browse/AAI-2913

Document AAI repo and microservice descriptions

Ondrej

OPEN

Put the link here for the document; we will share with the community and solicit feedback from repo/mS owners about the document.
https://lf-onap.atlassian.net/browse/AAI-2924

Frankfurt Defects

SOTNNI use case

@shashikanth.vh

https://gerrit.onap.org/r/c/aai/schema-service/+/102298

Security Requirements for pods

@James Forsyth

https://lf-onap.atlassian.net/browse/REQ-215

@Ondrej F

OPEN

Graphgraph not included in OOM deployment. How can we make it an essential part of the ONAP deployment.

Step 0: Make it stable.  Fix the docker build Jenkins jobs for graphgraph, may need to upgrade to a version of npm to be acceptable to graphgraph.  Needs to fit into the LF global-job jobs.  

Brownfield / deployed / embedded inventory systems and AAI

Fred from Verizon

OPEN

How do we accelerate migration using A&AI and the RunTime DB solution

Proposed a topic to be explored by AI&I and other ONAP WGs.

High impact, common interest among most CSPs 

Status Quo:

Most operators have multiple, siloed, possibly overlapping topology and inventory (domain specific) databases

Goal is to integrate ALL Inventory, and Topology databases into a Unified AI&I Architecture modeled DB which would contain ALL VNFs (VMs/Containers), PNFs, plus support easy expansion for future Inventory & Topology constructs/technologies.  

May take considerable time/investment (both are short).

Targeted Objectives

• Fast integration/consolidation time

• Minimize impact to business systems during migration

• Reduce throw away code

• Reduce throw away integration work

• Improve Service/Resource LCM & SA, especially for 5G

How to accelerate the migration to Unified Database?

• Phased Externalization of key PNF/VNF/CNF attributes currently stored in multiple inventory and topology silos.

• Simplify the eventual consolidation of Inventory and Topology DBs using proposed automation tools and advanced discovery capabilities supporting the above

• Leverage AI&I and possibly the ONAP Runtime Config DB and other ONAP WGs to help solve the problem

• Proposed topic can be explored by the AI&I and other ONAP WGs.

• Need to expand this preliminary list

Looking for volunteer to fix papyrus issue

OPEN

https://lf-onap.atlassian.net/browse/AAI-2771

Graphgraph doesn't parse the latest AAI schema correctly.  Need someone to investigate

sparky and data-router certificate issue

@Francis Paquette

IN PROGRESS

Sparky is using the AAF certificate interaction with Portal but a self-signed certificate to talk to search-data-service.  The search-data-service key story was removed.  

https://lf-onap.atlassian.net/browse/AAI-2765

https://lf-onap.atlassian.net/browse/AAI-2766

Collab efforts

@James Forsyth

@Giulio Graziani

@Kuldeep Singh Negi

@Former user (Deleted)

IN PROGRESS

Java 11

@James Forsyth

ON HOLD

@Venkata Harish Kajur tried schema service, a couple of dependency changes were required to get it to start. Eclipselink that is currently configured is incompatible.  

<groupId>javax.activation</groupId>
<artifactId>activation</artifactId>

is also incompatible

Needs more investigation for other repos

Need new common image (which Alpine image would we pick?)

AAI Bugs

@James Forsyth

IN PROGRESS

Performance Issue

@James Forsyth

OPEN

@FREEMAN, BRIAN D reported that when there are ~2400 vservers returned in a closed loop custom query, AAI takes minutes to respond.  We've discussed paging previously, any other ways to optimize this?

PUT 'https://aai.onap:8443/aai/v16/query?format=resource'

{"query":"query/closed-loop","start":"/cloud-infrastructure/cloud-regions/cloud-region/CloudOwner/RegionOne/tenants/tenant/28481f6939614cfd83e6767a0e039bcc/vservers/vserver/6ad9eb6b-d7fc-46d6-8617-4c9b46e7308b"}

Spring Boot 2

@James Forsyth

IN PROGRESS

https://lf-onap.atlassian.net/browse/AAI-2111

aai-common:1.5.2 (not released yet) will be the el-alto library for springboot 1.5.x microservices.  There needs to be some urgency to migrate the microservices to spring boot 2, since 1.5.3+ will not be backward compatible and so dependent applications might not have security updates if they stay on 1.5.2.  1.6.0 (Frankfort, currently master branch) aai-common will be springboot 2 so microservices must be updated by Frankfurt.  Springboot 1.5.21 is the latest (and last) version in the 1.5.x spring boot train.

New UI Features / Historical Tracking

@William Reehil

@Manisha Aggarwal

OPEN

The AT&T team has done an exciting POC at a sprint-a-thon event that they would like to share with the community.

ATT wants to contribute additional UI views to ONAP, want to discuss path forward

Link for self repo creation: https://lf-onap.atlassian.net/wiki/display/DW/Self+Repo+Creation+via+INFO.yaml

William/Jimmy will look into this for creating the new sparky extensions repository