Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

...

...

...

...

...

...

...

Attachments (including meeting recording):

...

 20200819 AAI Weekly Meeting.mp4

Attendees: William Reehil

@Shirley Morgan

Byung-Woo Jun

rodrigo lima

Chris Andre

Jacqueline Beaulac [Ericsson]

Fiachra Corcoran

@David Whitney

Fernando Oliveira

guochuyi

Kamel Idir

Venkata Harish Kajur

@Tanya Polavarapu

Gerard Nugent

Igor Dysko

@James Cuddy

Zu Qiang

@Ondrej Frindrich

Michela Bevilacqua


Agenda Items:

M4 milestone

...

Multi-tenancy Chris Andrerodrigo lima 



StatusOPENIN PROGRESSON HOLDDONECANCELLED

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 


3
Requirements for inclusion of GraphGraph in Guilin release
OPEN

List goes here

Open Jira tickets as tasks for G release

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyAAI-2910

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyAAI-2911

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyAAI-2912

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyAAI-2913

4
Frankfurt Defects

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQueryproject = AAI and type = Bug and status != closed and fixVersion = "Frankfurt Release"
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176

5
Security Requirements for podsJames Forsyth

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyREQ-215

6
Brownfield / deployed / embedded inventory systems and AAIFred from VerizonOPEN

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
7
Papyrus Enhancements
OPEN

Papyrus modeling (reverse engineering) Jacqueline Beaulac [Ericsson] 

AAI Information Model Reverse Engineering Meeting 

https://jira.onap.org/browse/AAI-2441
Need attribute descriptions story for graphgraph, any other requirements?

Is there an automated publishing mechanism we should look into?

8
sparky and data-router certificate issueFrancis PaquetteIN 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.  

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyAAI-2765

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyAAI-2766


9
AAI BugsIN PROGRESS

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution,fixversions
maximumIssues30
jqlQueryproject = AAI and type = Bug and status != closed
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176

10
Performance IssueOPEN

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 2James ForsythIN PROGRESS

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyAAI-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.

12
New UI Features / Historical TrackingOPEN

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

...