2019-09-18 AAI Meeting Notes

Search guard issue

AAI-2617: Search guard is no longer availableClosed

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

v17 schema for Frankfurt

@Keong Lim

@shashikanth.vh

Since the CCVPN SOTN proposal is in progress already, could we have the v17 schema introduced into master branch to receive the updates for Frankfurt release? AAI-2607: Add v17/v18/v19 schema oxm and edge rule files Closed

See also AAI-CCVPN-Extension-SOTN Proposals for Frankfurt Release and AAI-2593: Support CCVPN use case SOTN NNI Proposal in AAIClosed

AAI-2594: AAI: Store orchestration-type parameter as part of model-ver:objectClosed already added some v17 files but needs more work to be complete.

El Alto Bugs

@James Forsyth

Docker images not pushing

@James Forsyth

docker pull nexus3.onap.org:10003/onap/babel:1.5.0 - 1.5.1 pushed, will be release version
docker pull nexus3.onap.org:10003/onap/aai-champ:1.5.1 - 1.5-STAGING-latest available, no tagged images

docker pull nexus3.onap.org:10003/onap/aai-gizmo:1.5.0 - 1.5.2 pushed, will be release version

docker pull nexus3.onap.org:10003/onap/aai-data-router:1.5.0 - 1.5.1, will be release version

docker pull nexus3.onap.org:10003/onap/aai-search-data-service:1.5.0 - 1.5-STAGING-latest available, no tagged images AAI-2595: search-data-service is not producing a docker imageClosed

docker pull nexus3.onap.org:10003/onap/elasticsearch-sg:1.5.0 - same as search data service

docker pull nexus3.onap.org:10003/onap/aai-model-loader:1.5.0  - 1.5.1 will be release version

docker pull nexus3.onap.org:10003/onap/aai-spike:1.5.0  - 1.5.1 will be release version

docker pull nexus3.onap.org:10003/onap/aai-sparky-be:1.5.0 - 1.5-STAGING-latest, no tagged images

Want to migrate to an actively support maven docker plugin since Spotify docker plugin.  Consider fabric.io - an example is aai/resources

Alpine images

@Dmitry Puzikov (Deactivated)

Jenkins jobs needed to create / push the common alpine image that the AAI containers will use, still need this completed before we merge the outstanding commits.

AAI-2574: Submit ci-management update for docker stage on common images and sparky-fe centos issueClosed

AAI-2580: Request LF release of docker imagesClosed

GlowRoot

@James Forsyth

@Venkata Harish Kajur

Consider adding glow root profiling for AAI Microservices 

https://glowroot.org

Performance Issue

@James Forsyth

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

Spring Boot 2

@James Forsyth

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.

Upcoming R6 Functional Requirements

@Benjamin Cheung

Release 6 (Frankfurt) proposed use cases and functional requirements

Use Case Realization Call: July 24, 2019


Vetting DSL Queries

@Manisha Aggarwal

@William Reehil

Will discuss strategies AAI will employ to protect itself from rogue queries. 

AAI History

@Philip Blackwood

Discuss and review Scenarios for using historical inventory and topology

New UI Features / Historical Tracking

@William Reehil

@Manisha Aggarwal

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