Versions Compared

Old Version 5

changes.mady.by.user James Forsyth

Saved on

compared with

New Version Current

changes.mady.by.user Keong Lim

Saved on

Key

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

...

3rd July: raised

1
Docker images not pushingJames Forsyth

docker pull nexus3.onap.org:10003/onap/babel:1.5.0
docker pull nexus3.onap.org:10003/onap/aai-champ:1.5.1

docker pull nexus3.onap.org:10003/onap/aai-gizmo:1.5.0

docker pull nexus3.onap.org:10003/onap/aai-data-router:1.5.0

docker pull nexus3.onap.org:10003/onap/aai-search-data-service:1.5.0

docker pull nexus3.onap.org:10003/onap/elasticsearch-sg:1.5.0

docker pull nexus3.onap.org:10003/onap/aai-model-loader:1.5.0

docker pull nexus3.onap.org:10003/onap/aai-spike:1.5.0

docker pull nexus3.onap.org:10003/onap/aai-sparky-be:1.5.0

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

2
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

3
GlowRoot

James Forsyth

Venkata Harish Kajur

Consider adding glow root profiling for AAI Microservices 

https://glowroot.org

4
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

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

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

5
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

6
Janusgraph 0.2.3

James Forsyth

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.

7
AAI Dev Setup@ranvijay
8
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"}

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

10
Upcoming R6 Functional RequirementsBenjamin Cheung

Release 6 (Frankfurt) proposed use cases and functional requirements

Use Case Realization Call: July 24, 2019


11
Round trip reverse engineering of the AAI data model

James Forsyth

Moved to new meeting:

AAI Information Model Reverse Engineering Meeting

12
Vetting DSL Queries

Manisha Aggarwal

William Reehil

Will discuss strategies AAI will employ to protect itself from rogue queries. 
13
AAI HistoryPhilip BlackwoodDiscuss and review Scenarios for using historical inventory and topology
14Casablanca to Dublin MigrationAnkit Bhatt
Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyAAI-2507
based on Ankit's analysis that found the change in EdgeRules.


15Build 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.1615
Alternative meeting system

Just in case Zoom problems continue, try this instead:

https://meet.jit.si/onapaai

1716
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

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

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

1918
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

2019
Bug 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

2120
Gerrit Review
https://gerrit.onap.org/r/#/q/projects:aai2221
Sonar Review
https://sonar.onap.org/projects?search=aai&sort=coverage2322
Jenkins CLM Review
https://jenkins.onap.org/view/CLM/2423
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>


2524



Open Action Items

...