Attachments (including meeting recording)
|Title||Raised By||Status||Last discussed||Notes|
1) We need a repo strategy
a) No new repos
b) Existing empty repos should be locked (gap, eis, tabular-data-service, gap, etc) - Giulio Graziani please comment if there is an immediate plan to contribute into those repos
James Forsyth: At this time, there are no immediate plans to contribute these.
c) Consolidating existing repos - probably not
2) We need a maintenance strategy
3) We need a versioning strategy
a) Parent POM just for AAI that sets versions for common dependencies (including aai-common deps). Inherits oparent, and inherited by all components
4) We need responsible parties for each repo / component
5) Strategy for oparent dependency management
|2||ui_view role in AAF|
|3||AAI Impact in R6 - MDONS Use Case||Xin Miao|
The above is also mentioned in the gerrit comments
|5||No free nodeports in the 302XX range|
The aai-oom template forces all aai components to use 302XX port range, but it seems that this range is fully allocated OOM NodePort List (except 2 instances where the port allocation is striked through - not sure what that means).
We should discuss how to enable aai components nodeport allocation in aai-oom or circumvent nodeport usage via HAproxy (as suggested by Venkata Harish Kajur).
|6||Schema validation tool|
Ongoing progress to flash out possible validation rules for the schema AAI Schema and EdgeRule Audit rulesRules from a JUnit test https://gerrit.onap.org/r/gitweb?p=aai/schema-service.git;a=blob;f=aai-schema/src/test/java/org/onap/aai/schema/ValidateOXMTest.java;h=0dcf1b3abf1830a2d70cffe574877d4690c14fe0;hb=HEAD
|7||Helm Chart Common Templates|
- OOM-1936Getting issue details... STATUS
Use of common templates in the helm charts and have it driven from the values.yaml since all the helm charts are identical except the following things such as volumes, volume mounts, ConfigMap and secrets.
The goal is to extract all that information in the values.yaml file and use common templates to enable more consistency.
In each of the individual helm charts, we have a filebeat sidecar container, when creating a new helm chart, they just have to say if their chart should enable it or not in the values.yaml.
|8||AAI Use Cases|
|9||2 Types of logging in A&AI WS|
|1st Nov 2018|
There are 2 types of logging in the services
Is that correct? Shouldn't there be just 1 type?
After Casablanca release investigate logging guidelines and figure out what library to use in order to unify logging within A&AI
26th Nov: See also ONAP Application Logging Specification - Post Dublin
28th May: Stela Stoykova is fixing - AAI-2462Getting issue details... STATUS . Are there more that should be done for El Alto?
|10||Return codes and messages for WS|
|25th Apr 2019|
Is there a guide for the description of the error message and the error codes? How are new error states (message + code) added?