2020-06-10 AAI Meeting Notes

Attachments (including meeting recording):

AAI Weekly Session - 2020-06-10.mp4

Attendees:   

James Forsyth

William Reehil

William LaMont

Chris Andre

Venkata Harish Kajur

Igor Dysko

Neil Derraugh

@Ondrej Frindrich

@Rodrigo Lima

@Santosh Bayas

Starec Vlastimil

@Yoonsoon Chang

@Harshit Gupta

@Nagendra Kumar

Shirley Morgan


StatusOPENIN PROGRESSON HOLDDONECANCELLED

START RECORDING

1
Brownfield / deployed / embedded inventory systems and AAI
OPEN

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


Ultimate goal is to integrate ALL CSP inventory, and Topology databases into a Unified AI&I DB for ALL VNFs (VMs/Containers), PNFs, plus future inventory 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
2
AAI CNF Modeling

aai ← link to the AAI weekly CNF call. This team will be doing modeling work to decide how CNFs will be modelled in AAI
3
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. 
4
AAI PTL ElectionJames ForsythOPENElection season is underway and the AAI team will be accepting nominations for PTL.  Eligible votes on PTL are AAI committers.
5
New Committer on AAI

James Forsyth  is nominating William Reehil as an A&AI committer.  There will be a vote on this by the A&AI committers and then approval from TSC.  

Bill was approved by the TSC and is officially a committer!  Congrats Bill

6
Guilin non-functional proposals

  • No root user in the docker - use integration team guidance for setting a USER in the Dockerfile rather than gosu (see aai-resources) and fix haproxy. We might consider adding aaiadmin to the base image, and then just set USER aaiadmin in Dockerfile
  • AAI-2822 - Getting issue details... STATUS
  • Move haproxy functionality into k8 (question)
  • Move aai/oom chart back to oom AAI-2914 - Getting issue details... STATUS
  • Move to Spring boot 2 (aai-parent inherits oparent:2.1.0)
  • Java 11 (oparent 3) - need to consider downstream dependencies on ONAP carrier partners
  • Use AAF certificate manager
  • Remove all hardcoded secrets
  • AAI needs to be able to run without AAF (means no HTTPS)
  • Upgrade to latest versions of 3rd party dependencies - EclipseLink and gremlin
  • Better coverage on javascript repos (graphgraph and sparky-fe)
  • Commit to a % increase in code coverage
  • SONAR bugs / security / code smells
  • Platform maturity - performance testing (Bell Canada has interest; if test suites could be upstreamed there could be resources to help us move our PM metrics up)
  • Security assurance document for CII badging

Guilin release - non-functional requirements proposed list



7
Guilin Functional requirements proposals

Use Case Realization Meeting Register MoM

Guilin release - functional requirements proposed list - pay special attention to the "Documenting ONAP APIs" section by Andy Mayer.  The team from Orange might be interested in developing tooling around generating a more user-friendly AAI API documentation section on readthedocs.

8
Requirements for inclusion of GraphGraph in Guilin release

List goes here

Open Jira tickets as tasks for G release

AAI-2910 - Getting issue details... STATUS

AAI-2911 - Getting issue details... STATUS

AAI-2912 - Getting issue details... STATUS

AAI-2913 - Getting issue details... STATUS

9
Document AAI repo and microservice descriptionsOndrej
Put the link here for the document; we will share with the community and solicit feedback from repo/mS owners about the document.
10
Frankfurt Defects

key summary type created updated due assignee reporter priority status resolution
Loading...
Refresh

11
SOTNNI use case

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


12
Service model and schema impactBenjamin Cheung

13
Security Requirements for podsJames Forsyth

REQ-215 - Getting issue details... STATUS

14

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.  

15

Fred 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
16
SONAR coverage reportDONE

https://sonarcloud.io/organizations/onap/projects

AAI-2793 - Getting issue details... STATUS

James Forsyth, the main reason behind these discrepancies is the fact that SonarQube is based on version 6.7.1 and SonarCoud is version 8+ 


After migrating to SonarCloud, we fetch updates they do automatically without the need of doing any manual upgrade. Since we migrated, few things have changed. For example:

  • LF does no longer mark warnings in the reports, only pass or fail
  • LF is no longer able to manage individual quality profiles per language. Whatever latest support is there, we fetch this automatically in our side.
  • Jacoco plugin has changed quite a bit, we need to make sure our reports are now xml based instead of exec. I think this can be the main reason why you are facing coverage drops. Can you please check? This is what Sonar mentioned to me in detail: 

You can find more info in the wiki :https://wiki.onap.org/display/DW/SonarCloud+migration+from+SonarQube

Update 19 Feb: All Fixed except: aai-sparky-be, aai-esr-server and aai-validation.  Jimmy is working on them.

17
Looking for volunteer to fix papyrus issue
OPEN

AAI-2771 - Getting issue details... STATUS

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

18
Spring boot upgrade issue
DONE

AAI-2528 - Getting issue details... STATUS

AAI-2769 - Getting issue details... STATUS

 2 Spring beans with the same name is disallowed in Spring boot 2


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

AAI-2765 - Getting issue details... STATUS

AAI-2766 - Getting issue details... STATUS


20
Collab effortsIN PROGRESS
21
Windriver Lab ChangeDONE

The Intel/Wind River lab was relocated into a new data center last week.   The only change required to connect to the new location is to update the VPN IP in the .ovpn file.  Here is the change:


[sgooch@atl-sgooch-lx ~]$ diff -u pod-onap-01.ovpn.org pod-onap-01.ovpn

--- pod-onap-01.ovpn.org   2020-01-13 13:03:03.960856010 -0500

+++ pod-onap-01.ovpn 2020-01-09 18:27:03.560549576 -0500

@@ -5,7 +5,7 @@

client

dev tun

proto tcp

-remote 192.55.48.241 443

+remote 146.152.204.133 443

resolv-retry infinite

auth-nocache

nobind

22
Discuss developers call timeDONETuesdays @ 9 AM US/Eastern, 19:30 India Standard Time
23
SO query in AAIDONE

NNI Use Case - discovering 2 topologies from the network

Use case is asking for the ability in AAI to link an underlay and overlay together by having a cousin relationship between 2 PNFs.  Asking Chandra Cinthalato verify if that edge rule can be added for the Frankfurt release.

Per Chandra: "I think pnf -> pnf edge is redundant and not needed as we can traverse (thru a logical or physical interface) from pnf -> p-interface/l-interface -> pnf."

Chandra Cinthala  please note: According to shashikanth.vh, the team requires a relationship from an overlay topology node to an underlay topology node; by using the p-interface in overlay we cannot traverse to underlay node.  Suggest to allow an edge for PNF→PNF, which is consistent with RFC 8345 model

24
Search guard issueGiulio Graziani ON HOLD

Merged and released yesterday; issue is closed. 

AAI-2617 - Getting issue details... STATUS

Tracking for Frankfurt:

AAI-2677 - Getting issue details... STATUS

Search guard container no longer available so elasticsearch-sg won't build.  Search guard allows us to secure the elastic communication, which in older versions was not available but newer versions have support for secure communication.

https://www.elastic.co/blog/dear-search-guard-users

Consider opendistro as replacement for search-guard

Can we consider this one:

https://docs.search-guard.com/latest/search-guard-community-edition

25
E2E Network SlicingLIN MENGDONEFor the E2E Network Slicing use case for Frankfurt Release, we intend to leverage the nested service model work that has been going on since Dublin release. From A&AI perspective, we foresee that the schemas would have to be enhanced to cover network slicing models. We have considered A&AI to be a stretch goal for Frankfurt, though we are committing resources. So, we would like to start the discussion in the coming weeks, and subsequently implementation work to try our best to complete the implementation for Frankfurt. AAI-2600 has been created just to indicate the SDC impacts, we will update it with more details, and also join the A&AI weekly call during the next 1-2 weeks to discuss further.
26
Portal SDK UpgradeIN PROGRESS

AAI-2726 - Getting issue details... STATUS

Francis Paquette  need evaluation of feasibility in Frankfurt for sparky

27
GraphGraph Image Missing in NexusVenkata Harish KajurOPEN

Graph Graph Images are missing from nexus and it needs to be resolved in order for elalto deployment to be successful.

OOM-2161

How did this docker image get pushed to nexus and why was it removed from nexus?  

Graphgraph was removed from the default helm chart, but we still need to get these jobs fixed.