2019-08-07 AAI Meeting Notes

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 - Getting issue details... STATUS

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

AAI-2548 - Getting issue details... STATUS

AAI-2549 - Getting issue details... STATUS

JIRA Epic/Story count: Getting issues...

Keong Lim

James Forsyth

AAI-2420 - Getting issue details... STATUS

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

James Forsyth

Brian Freeman 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?

AAI-2111 - Getting issue details... STATUS

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.

James Forsyth

James Forsyth Francis Paquette

Global JJB transition Complete!

Manisha Aggarwal

William Reehil

3rd July: raised AAI-2507 - Getting issue details... STATUS based on Ankit's analysis that found the change in EdgeRules.

James Forsyth

William Reehil

Manisha Aggarwal

James Forsyth

Taranjit Singh

Understanding the architecture of AAI is not easy - hard to understand how the code is laid out and how things flow. Need documention which will describe how the microservices are connected, which repos support which functions, etc. Pavel Paroulek says that he had to reverse engineer the dependencies to see how the repos are connected. Recommended to focus on the resources repo for understanding the core function of AAI.

(bumped up, is it still relevant?)

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.

AAI-2172 - Getting issue details... STATUS

James Forsyth

Container Image Minimization Guidelines

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

JIRA Issue Count (in AAI project): Getting issues...

JIRA Issue Count (talking about AAI): Getting issues...

Pavel Paroulek

• code coverage to 55% for Dublin AAI-2219 - Getting issue details... STATUS

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.

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