Page Comparison

We are not able to view any node data on AAI UI. We need to understand the flow by which nodes are getting displayed over UI. We have understood that the flow is like sparky-be-->search-data-->elastic-search→Cassandra. However; we fail to understand why default installation did not enabled elastic search to retrieve data from Cassandra? Any other config verification/enablement required for AAI UI to work would be helpful.

http://<IP>:30220/rest/search/querysearch/

{

"processingTimeInMs" : 65,

"totalFound" : 0,

"suggestions" : [ ]

}

22nd May: Made suggestion on https://lists.onap.org/g/onap-discuss/message/17162

2

False positives in Sonar reports

Keong Lim

Comment on flagging Sonar reports as "false positives":

Jira Legacy

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

Do we have access to do this ourselves or should we report these to Jess?

3

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

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

4

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

5

GraphGraph demo

Former user (Deleted)

A 5-10 minute demo of GraphGraph.

Feedback needed!

6

Bug Review

JIRA Issue Count (in AAI project):

Jira Legacy

server	System Jira
jqlQuery	project = AAI AND issuetype = Bug and status not in (Closed, Delivered) ORDER BY fixVersion ASC, priority DESC, updated ASC
count	true
serverId	4733707d-2057-3a0f-ae5e-4fd8aff50176

JIRA Issue Count (talking about AAI):

Jira Legacy

server	System Jira
jqlQuery	project != 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
count	true
serverId	4733707d-2057-3a0f-ae5e-4fd8aff50176

7

Dublin branching

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

8

Gerrit Review

https://gerrit.onap.org/r/#/q/projects:aai

9

Sonar Review

https://sonar.onap.org/projects?search=aai&sort=coverage

10

Jenkins CLM Review

https://jenkins.onap.org/view/CLM/

11

Blockers

James Forsyth

Jira Legacy

server	System Jira
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	4733707d-2057-3a0f-ae5e-4fd8aff50176
key	AAI-2406

Jira Legacy

server	System Jira
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	4733707d-2057-3a0f-ae5e-4fd8aff50176
key	AAI-2411

Jira Legacy

server	System Jira
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	4733707d-2057-3a0f-ae5e-4fd8aff50176
key	AAI-2402

12

Helm Chart Transfer

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

13

Status of ARC documentation

Former user (Deleted)

When is this going to be finished ARC AAI Component Description - Dublin ?

Note: I have no idea what it is, I just was asked to inquire

14

Dublin Status 1

James Forsyth

Encourage our clients to migrate off named query
- To support Policy code change to custom queries
  Jira Legacy
  server System Jira
  serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
  key POLICY-1266
  , could this be fixed?
  Jira Legacy
  server System Jira
  serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
  key AAI-2351
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

15

Dublin Status 2 / OOM helm charts

James Forsyth

Venkata Harish Kajur

Moving Helm charts into AAI repos

Former user (Deleted) is the AAI contact for doing the helm chart migration, info passed along to Mike Elliot

Migration of the oom / aai charts to an new repo that we will have commit access to. Harish tried to preserve the history on the existing set of files, but there was no way to do it because the commit messages would violate the 50 character limit. So we will lose history on the commits and do the push as a new code drop.
Jessica found a way to do it
Not sure if this would be pushed into El Alto release

16

Dublin Status 3

James Forsyth

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

17

Dublin Status 4

James Forsyth

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>

18

Dublin Use Cases

James Forsyth

Epic-of-epics:

Jira Legacy

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

5G Use Case (R4 Dublin)

BBS Broadband Service Use Case (Dublin)

CCVPN Use Case (Dublin)

Change Management Dublin Extensions

Fine Grain Placement Service (F-GPS) Edge Automation (Dublin)

OpenSource Access Manager (OSAM) Use Case

K8S based Cloud Region Support

Tony Noori from AT&T will identify the ONAP POC for system engineering for AAI modelling. This person will coordinate schema changes, watch the use case wiki, jira, perform gerrit reviews, etc.

Analysis: AAI R4 Use Case and Functional Requirements Impacts

JIRA Epics count:

Jira Legacy

server	System Jira
jqlQuery	project = AAI AND issuetype = Epic AND fixVersion = "Dublin Release" ORDER BY created DESC
count	true
serverId	4733707d-2057-3a0f-ae5e-4fd8aff50176

19

El Alto Status

James Forsyth

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

JIRA Epics count:

Jira Legacy

server	System Jira
jqlQuery	project = AAI AND issuetype = Epic AND fixVersion = "El Alto Release" ORDER BY created DESC
count	true
serverId	4733707d-2057-3a0f-ae5e-4fd8aff50176

20

Selenium Tests in Sparky

Arul Nambi

Want to share in the community potential selenium changes for the sparky UI

21

Traversal Nodes query documentation

J. Ram Balasubramanian

Jira Legacy

server	System Jira
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	4733707d-2057-3a0f-ae5e-4fd8aff50176
key	AAI-2202

Jira Legacy

server	System Jira
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	4733707d-2057-3a0f-ae5e-4fd8aff50176
key	AAI-2383

Documentation on the search/nodes-query API is missing. James Forsyth needs to find it and publish it.

22

AAI achitecture documentation

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.

23

API version documentation

Keong Lim

Is v15 API for Dublin release?

Jira Legacy

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

Why does schema-service now have v16 files?

Jira Legacy

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

James Forsyth Document nodes wiki and add explanation about presence of the v15 file. Should add v14-v15 changes to release notes.

24

Resources Nodes query documentation incomplete

Keong Lim

Jira Legacy

server	System Jira
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	4733707d-2057-3a0f-ae5e-4fd8aff50176
key	AAI-2384

API Documentation needs update, as both of these URL paths are equally valid:

/aai/v13/nodes/{plural}/{singular}
/aai/v13/nodes/{singular}

Add to the Dublin Release for the documentation of the singular nodes query

25

AAI Dublin wiki updates

Team

Added pages to AAI in Dublin Release

Please keep these procedures up-to-date with latest Dublin code.

26

...

Versions Compared

Old Version 5

New Version 6

Key

Attendees: