2019-09-11 AAI Meeting Notes

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?

See also AAI-CCVPN-Extension-SOTN Proposals for Frankfurt Release and https://lf-onap.atlassian.net/browse/AAI-2593

El Alto Issues

@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 https://lf-onap.atlassian.net/browse/AAI-2595

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.

https://lf-onap.atlassian.net/browse/AAI-2574

https://lf-onap.atlassian.net/browse/AAI-2580

ONAP Use Cases

@Former user (Deleted)

GlowRoot

@James Forsyth

@Venkata Harish Kajur

Consider adding glow root profiling for AAI Microservices 

https://glowroot.org

Microservices enabled by default in aai/oom

@James Forsyth

The ones in bold will be turned "off" by default:

aai-babel               aai-elasticsearch       aai-modelloader         aai-search-data         aai-traversal

aai-champ               aai-gizmo               aai-resources           aai-sparky-be

aai-data-router         aai-graphadmin          aai-schema-service      aai-spike

We will add are release note about how to turn off the ones in italics for users that want a true minimum set without the UI

https://lf-onap.atlassian.net/browse/AAI-2548

https://lf-onap.atlassian.net/browse/AAI-2549

El Alto Review

@James Forsyth

JIRA Epic/Story count:

Janusgraph 0.2.3

@James Forsyth

https://lf-onap.atlassian.net/browse/AAI-2420

@James Forsyth is going to merge updates to JanusGraph, 0.2.0 → 0.2.3 in master, should be a drop in replacement.

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

https://lf-onap.atlassian.net/browse/AAI-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.

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

Build styles

@James Forsyth

We have too many ways to build and deploy artifacts, which makes it difficult and time-consuming.  Some of our artifacts are not backward compatible and we need to move everything up to released versions.

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

Run AAI containers as non-root user

@James Forsyth

https://wiki.onap.org/display/DW/Best+Practices

• The Docker and Kubernetes engines may run as root until such time as the products support non-root execution.

• Applications may run as root within a container.

• The process ID of a container must not run as the root ID with the exception of containers supporting ONAP features that require the container to run as the root ID.

• Containers may run with root privileges.

• Project containers that run as the root ID must document this in the release notes along with the functionality that requires the container to run as the root ID.

https://lf-onap.atlassian.net/browse/AAI-2172

Container Images

@James Forsyth

Container Image Minimization Guidelines

@James Forsyth will ask integration team if we can use the AAI tenant space in windriver environment

Code Coverage Status

@James Forsyth

• code coverage to 55% for Dublin https://lf-onap.atlassian.net/browse/AAI-2219

Champ slipped below 55% with latest commit.