Attachments (including meeting recording):
Attendees:
@Ondrej Frindrich
@Sam Huang
@Yoonsoon Chang
Agenda Items:
Endpoint/IpAddress Discussion with Henry Yu
Prudence Au (concurrency fix) AAI-3100
Rodrigo Lima (multi-tenancy)
Guilin Timeframe Reminder
...
Guilin Open Issues
| Status | OPEN | IN PROGRESS | ON HOLD | DONE | CANCELLED |
|---|
START RECORDING
| 1 | AAI CNF Modeling | OPENAAI ← 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: Functional Use Cases | |||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 32 | Requirements for inclusion of GraphGraph in Guilin release | OPEN | List goes here Open Jira tickets as tasks for G release
| 4Frankfurt Defects |
| 5
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 3 | Security Requirements for pods | James Forsyth |
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 64 | 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?
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 75 | 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 |
| Jira Legacy | ||||||||
|---|---|---|---|---|---|---|---|---|
|
| Jira Legacy | ||||||||
|---|---|---|---|---|---|---|---|---|
|
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
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"}
| Jira Legacy | ||||||||
|---|---|---|---|---|---|---|---|---|
|
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.
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://wikilf-onap.onapatlassian.orgnet/wiki/display/DW/Self+Repo+Creation+via+INFO.yaml
William/Jimmy will look into this for creating the new sparky extensions repository
...