Versions Compared

Key

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

Recording:

...

Attachments (including meeting recording):

Attachments

Attendees:

James Forsyth

Keong Lim

Former user (Deleted)

Keong Lim

William LaMont

Dmitry Puzikov Former user (DeactivatedDeleted)

Ondrej F

shashikanth.vh

Tian Lee

Manisha Aggarwal

Venkata Harish Kajur

Former user (Deleted)William Reehil

Benjamin Cheung

Borislav Glozman

Giulio Graziani

Steve BlimkieBenjamin Cheung

shashikanth.vh

Shirley Morgan


CLEAN UP OLD RECORDINGS IN ATTACHMENTS

START RECORDING

Keong Lim

shashikanth.vh

Introduction of schema change proposals.

See also AAI-CCVPN-Extension-SOTN Proposals for Frankfurt Release and

1
v17 schema for Frankfurt

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

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

2
El Alto Issues

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

23
Docker images not pushingJames 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 

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

34
Alpine imagesDmitry 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.

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

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

4CCVPN use case in Frankfurt

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

5AAI 5
ONAP Use Cases
6
GlowRoot

Consider adding glow root profiling for AAI Microservices 

https://glowroot.org

7
Microservices enabled by default in aai/oom

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

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

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

8
El Alto ReviewJames Forsyth

JIRA Epic/Story count:

Jira Legacy
serverSystem Jira
jqlQueryproject = AAI AND issuetype in (Epic,Story) AND fixVersion = "El Alto Release" ORDER BY created DESC
counttrue
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176

9
Janusgraph 0.2.3

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

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

10AAI Dev Setup@ranvijayWatching ranvijay editing the files identified problems in the text of AAI Developer Environment Setup - Dublin that were subsequently fixed.11
Performance Issue

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

1211
Spring Boot 2James Forsyth

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.

1312
Upcoming R6 Functional RequirementsBenjamin Cheung

Release 6 (Frankfurt) proposed use cases and functional requirements

Use Case Realization Call: July 24, 2019

14Round trip reverse engineering of the AAI data model

Moved to new meeting:

AAI Information Model Reverse Engineering Meeting

1513
Vetting DSL QueriesWill discuss strategies AAI will employ to protect itself from rogue queries. 1614
AAI HistoryPhilip BlackwoodDiscuss and review Scenarios for using historical inventory and topology1715
Build stylesWe 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.18Alternative meeting system

Just in case Zoom problems continue, try this instead:

https://meet.jit.si/onapaai

1916
New UI Features / Historical Tracking

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

2017
Run AAI containers as non-root user

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.

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

2118
Container Images

Container Image Minimization Guidelines

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

22Bug Review

JIRA Issue Count (in AAI project):

Jira Legacy
serverSystem Jira
jqlQueryproject = AAI AND issuetype = Bug and status not in (Closed, Delivered) ORDER BY fixVersion ASC, priority DESC, updated ASC
counttrue
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176

JIRA Issue Count (talking about AAI):

Jira Legacy
serverSystem Jira
jqlQueryproject != AAI AND (text ~ "AAI" OR text ~ "A?AI" OR text ~ "A??AI" OR text ~ "A???AI") AND issuetype = Bug and status not in (Closed,Delivered,Done) ORDER BY priority DESC, updated ASC
counttrue
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176

23Gerrit Reviewhttps://gerrit.onap.org/r/#/q/projects:aai24Sonar Reviewhttps://sonar.onap.org/projects?search=aai&sort=coverage25Jenkins CLM Reviewhttps://jenkins.onap.org/view/CLM/2619
Code Coverage StatusJames Forsyth
  • code coverage to 55% for Dublin
    Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyAAI-2219

Champ slipped below 55% with latest commit.

  •  Tian Lee will do babel, model-loader, champ, gizmo, event-client, spike, rest-client, validation
  •  Arul Nambi will do sparky-be, search-data-service, data-router, logging-service, router-core
  •  James Forsyth create ticket for El Alto for sparky, rolling back because of sonar failure
  •  Venkata Harish Kajur will check aai-common, resources, traversal, graphadmin, cacher, schema-service (which probably already have the setting)
  •  Add thresholds to all repos that are above 55% so it doesn't happen again
  •  For setting the threshold on each repo, set it to the current percentage, so if it's is at 62.7%, set the threshold to 0.62
  •  

     <jacoco.line.coverage.limit>0.68</jacoco.line.coverage.limit>

    Sonar job for Dublin has been changed to using line coverage.

    Code Block
      <execution>
                            <id>default-check</id>
                            <goals>
                                <goal>check</goal>
                            </goals>
                            <configuration>
                                <dataFile>${project.build.directory}/coverage-reports/jacoco.exec</dataFile>
                                <rules>
                                    <!--  implementation is needed only for Maven 2  -->
                                    <rule implementation="org.jacoco.maven.RuleConfiguration">
                                        <element>BUNDLE</element>
                                        <limits>
                                            <limit implementation="org.jacoco.report.check.Limit">
                                                <counter>LINE</counter>
                                                <value>COVEREDRATIO</value>
                                                <minimum>${jacoco.line.coverage.limit}</minimum>
                                            </limit>
                                        </limits>
                                    </rule>
                                </rules>
                            </configuration>
                        </execution>


2720



Open Action Items

...