2020-09-02 AAI Meeting Notes
Attachments (including meeting recording): 20200902 AAI Weekly Meeting.mp4
Attendees:
@William Reehil
@Venkata Harish Kajur
@Igor Dysko
@Ondrej Frindrich
@rodrigo lima
@Sam Huang
@Neil Derraugh
@Starec Vlastimil
@Yoonsoon Chang
@Shirley Morgan
Agenda Items:
Guilin Timeframe Reminder
SonarCloud IO Ticket
GUI Demo (What all could come to ONAP with retiring of Current Sparky)
Bugs
Status | OPEN | IN PROGRESS | ON HOLD | DONE | CANCELLED |
---|
START RECORDING
1 | 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 | ||||||||||||||
2 | Guilin requirements | OPEN | AAI R7 Guilin Release: TSC must have requirements AAI R7 Guilin Release: Functional Use Cases | ||||||||||||||
3 | Requirements for inclusion of GraphGraph in Guilin release | OPEN | List goes here Open Jira tickets as tasks for G release AAI-2910: Add graphgraph sonar job to ci-managementClosed AAI-2911: Add graphgraph CLM job to ci-managementClosed | ||||||||||||||
4 | Frankfurt Defects | ||||||||||||||||
5 | Security Requirements for pods | @James Forsyth | REQ-215: Containers configured per secure recommendationTo Do | ||||||||||||||
6 | 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
How to accelerate the migration to Unified Database?
| |||||||||||||
7 | Papyrus Enhancements | OPEN | Papyrus modeling (reverse engineering) @Jacqueline Beaulac [Ericsson] AAI Information Model Reverse Engineering Meeting https://jira.onap.org/browse/AAI-2441 Is there an automated publishing mechanism we should look into? | ||||||||||||||
8 | 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. AAI-2765: Sparky cannot communicate with search-data-service (certificate issue)Closed AAI-2766: Data-Router cannot communicate with dmaap (certificate issue)Closed | |||||||||||||
9 | AAI Bugs | @James Forsyth | IN PROGRESS |
| |||||||||||||
10 | 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"} | |||||||||||||
11 | Spring Boot 2 | @James Forsyth | IN PROGRESS | AAI-2111: Upgrade to spring boot 2 (Set 1)Closed 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. | |||||||||||||
12 | 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 |