Content Comparison

• No 2 way TLS in Dublin; James Forsyth will socialize early in El Alto, Due 03 Jun 2019
• pnf-id change pushed to El Alto during Architecture review AAI R4 Architecture Review - 5 Mar 2019API version update for El Alto should be co-ordinated for earlier in the cycleneeds a checklist of things to be updated, including yang classes

  Jira Legacy
  server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key AAI-2351

• 2019
• API version update for El Alto should be co-ordinated for earlier in the cycle
  • needs a checklist of things to be updated, including yang classes

    Jira Legacy
    server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176

• • key AAI-2351

    
    

Taranjit Singh (Deactivated)

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. Former user (Deleted) 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.

James Forsyth

Container Image Minimization Guidelines

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

Former user (Deleted)

JIRA Issue Count (in AAI project):

JIRA Issue Count (talking about AAI):

James Forsyth

Dublin artifacts are released and jjb jobs are updated to drop casablanca jobs and replace with dublin

We will change the sonar and clm jobs to use the dublin branch

•  James Forsyth will see how other teams manage merging release bug/security/late feature change back to master

James Forsyth

•  James Forsythwill start a document with best practices and requirements for merging changes to the aai/oom submodule
•  Team needs to document (perhaps change the AAI guide for OOM setup) the change to use the submodule in OOM

Former user (Deleted)

• Encourage our clients to migrate off named query
• Trying for Silver badge and Level 2 on Security; 50% code coverage on repos
• Resiliency and fault tolerance; meeting notice never published,

• CSIT on OOM needs to cover more of the services
  

• Volumed run-time generated certificates are possible

•  

  James Forsyth will open Jira tickets to update the keystores in the master branches of the mS that use https

•  

  Arul Nambi will do sparky-be, search-data-service, data-router, logging-service, router-core
  

• GraphGraph is coming, depends on expanding schema-service API
• RestClient updates are potentially being contributed by community members

• code coverage to 55% for Dublin

  Jira Legacy
  server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key AAI-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>