Versions Compared

Key

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

Attachments (including meeting recording): <insert recording here>

...

Multi-tenancy Neil Derraugh



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
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. 

3
Guilin requirements
OPEN

AAI R7 Guilin Release: Functional Use Cases 


4
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

5
Document AAI repo and microservice descriptionsOndrejOPEN

Put the link here for the document; we will share with the community and solicit feedback from repo/mS owners about the document.

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

6
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

7
SOTNNI use case

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


8
Security Requirements for podsJames Forsyth

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

9

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.  

10
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
11
Looking for volunteer to fix papyrus issue
OPEN

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

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

12
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


13Collab effortsIN PROGRESS
14Java 11ON 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?)

1514
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

1615
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"}

1716
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.

1817
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://wiki.onap.org/display/DW/Self+Repo+Creation+via+INFO.yaml

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

...