but it contains some links to internal att.com. Keong Limthe initial doc did, but I cleaned them up, can you point to the spots I missed? - Jimmy
James Forsyth I still see it in: "AID page", related-link in "resource" format example, url in resource_and_url example, simple example, syntax example.
Aha - the hyperlinks didn't update.
Looking forward to further discussion and experimentation!
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. user-b8310 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.
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
425b2b0a-557c-3c0c-b515-579789cceedb
JIRA Issue Count (talking about AAI):
Jira
server
ONAP 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