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.
23rd May: was discussed at AAI Developers call. Is it OK now?
3
. Is it OK now?
We need to understand how to verify if all the indexes are created. The main problem is AAI instance not able to retrieve data within 100 secs. Jimmy, Could you please point to any documentation ?
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.
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
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
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.
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.