Attachments (including meeting recording)
| Status | OPEN | IN PROGRESS | ON HOLD | DONE | CANCELLED |
|---|
Agenda Items
START RECORDING
| Title | Raised By | Status | Last discussed | Notes | |
|---|---|---|---|---|---|
| 1 | AAF autocert | IN PROGRESS | 2019-09-12 | ||
| 2 | No free nodeports in the 302XX range | OPEN | 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). | ||
| 3 | Schema validation tool | IN PROGRESS | 2019-08-29 | Ongoing progress to flash out possible validation rules for the schema AAI Schema and EdgeRule Audit rules Rules 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=HEADAAI-2583 - Getting issue details... STATUS | |
| 4 | Helm Chart Common Templates | IN PROGRESS | 2019-08-29 |
OOM-1936
-
Getting issue details...
STATUS
https://gerrit.onap.org/r/c/oom/+/91553 https://gerrit.onap.org/r/c/aai/oom/+/91550 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. | |
| 5 | AAI Use Cases | ||||
| 6 | BYOQ DSL wiki | DONE | 2019-08-29 | Referring to https://wiki.onap.org/display/DW/cloud-region-fromVnf Wiki page says that output is: vserver vnfc tenant cloud-region but stored-queries.json definition includes: .createEdgeTraversal(EdgeType.COUSIN, 'vserver', 'pserver').store('x')
So the output should also include "pserver"? Also, the wiki page shows The formatting of the traversal suggests that only cloud-region would be returned, which is inconsistent with the sections above on the same page. Which one is correct for this case? This is my attempt at a translation of the Gremlin query into DSL query: {
"dsl":"generic-vnf*('vnf-id',‘id number') > [
vnfc* > vserver* > [ pserver*, tenant* > cloud-region* ] ,
vserver* > [ pserver*, tenant* > cloud-region* ] ]"
}
Please confirm whether this is accurate and correct.
Update 9/11/19 Original custom query was supposed to return vserver, vnfc, tenant, cloud-region but there was an enhancement to that story to include pserver, generic-vnf. The DSL looks correct. | |
| 7 | AAI-EVENT configuration | DONE | 2019-08-29 | While investigating and responding to https://lists.onap.org/g/onap-discuss/topic/32651336 discovered that topic name "AAI-EVENT" appears in some configuration property files but also hard-coded into some Java files. Is this topic name intended to be fully configurable or not? e.g.
| |
| 8 | 2 Types of logging in A&AI WS | ON HOLD | 1st Nov 2018 | There are 2 types of logging in the services
Is that correct? Shouldn't there be just 1 type? 1st Nov: 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 29th Nov: how does this fit with LOG-877 - Getting issue details... STATUS ? 28th May: Stela Stoykova is fixing AAI-2462 - Getting issue details... STATUS . Are there more that should be done for El Alto? https://gerrit.onap.org/r/c/aai/cacher/+/85319
| |
| 9 | Return codes and messages for WS | ON HOLD | 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?
| |
| 10 | range query | DONE | 2019-08-29 |
| |
| 11 | New AAF Certificates at startup | Jimmy Forsyth | ON HOLD | 24th Jan 2019 | AAI-2476 - Getting issue details... STATUS AAF will generate certificates to the be used by the containers at startup; AAI services should use the run-time generated certs instead of the ones that are in the repos or oom charts. In dublin the services will mount a volume with certificates. This is on the roadmap for Dublin as a feature.
12th June 2019: Jonathan Gathman demonstrated aaf-hello functionality at DDF event
|
| 12 | AAI HAProxy and 2-way-TLS | ON HOLD | 2019-08-29 | Technical solution to either decommission the proxy or make design changes to AAF to enable client side certificates. After VF2F we will know if this is a requirement in Dublin. We discuss after this date. question raised: MSB - would client authentication be supported?
James Forsyth - please update if this agenda item is still relevant | |
| 13 | AAI Impact in R6 - MDONS Use Case | Xin Miao (Unlicensed) | 2019-9-19 | Introduce MDONS Use Case Multi-domain Optical Network Services and its impact on AAI in Frankfort AAI MDONS Proposal for Frankfort Release |