...
| Title | Raised By | Status | Last discussed | Notes | ||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | AAI Impact in R6 - MDONS Use Case | Xin Miao (Unlicensed) |
| 2019-909-19 | Introduce MDONS Use Case Multi-domain Optical Network Services and its impact on AAI in Frankfort AAI MDONS Proposal for Frankfort Release
| |||||||||||||||||||||||||||||||||||||||||||||||||||
| 2 | AAF autocert |
| 2019-09-12 | |||||||||||||||||||||||||||||||||||||||||||||||||||||
| 3 | No free nodeports in the 302XX range |
| 2019-09-10 | 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).
| ||||||||||||||||||||||||||||||||||||||||||||||||||||
| 4 | Schema validation tool |
| 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=HEAD
| ||||||||||||||||||||||||||||||||||||||||||||||||||||
| 5 | Helm Chart Common Templates |
| 2019-08-29 |
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. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
| 6 | AAI Use Cases | |||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 7 | BYOQ DSL wiki |
| 2019-08-29 |
| Code Block |
|---|
vserver
vnfc
tenant
cloud-region |
but stored-queries.json definition includes:
| Code Block |
|---|
.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:
| Code Block |
|---|
{
"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.
- Venkata Harish Kajurwill let this code block be reviewed.
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.
| Status | ||||
|---|---|---|---|---|
|
Is this topic name intended to be fully configurable or not?
e.g.
- We need to concentrate configuration (like event name) on one place and not have it spread throughout the properties/java classes
- A description of the payload, so that possible new consumers know what to expect. Maybe a light description would be good.
| Status | ||||
|---|---|---|---|---|
|
There are 2 types of logging in the services
- one read from EELFManager
- the other Logger log = Logger.getLogger( ...
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
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
28th May: Stela Stoykova is fixing
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
https://gerrit.onap.org/r/c/aai/cacher/+/85319
- Former user (Deleted) reach out to the logging enhancement team and ask if there is a ONAP-wide logging system which we should use as the A&AI microservicese use at least 2 different approaches
| Status | ||
|---|---|---|
|
Is there a guide for the description of the error message and the error codes? How are new error states (message + code) added?
| Status | ||
|---|---|---|
|
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 Forsythcreates a task for encryption of communication between A&AI services and Cassandra
- Tian Lee and Steve Blimkie to report on the Amdocs managed A&AI microservice wheter they support criteria from the Dublin S3P requirements
- William LaMont will send James Forsyth the output of a script that formats the error.properties file to make a wiki page and readthedocs
- James Forsyth should commit that script and create a wiki for the error properties
| Status | ||||
|---|---|---|---|---|
|
is there a way to do partial match? regex?
PUT /aai/v13/query?format=raw
| Code Block |
|---|
{"gremlin": "g.V().has('aai-ts', org.janusgraph.core.attribute.Text.textContains('URL'))"} |
- James Forsyth will invite Arul Nambi and CT Paterson to next week's dev call to talk about how sparky/elastic does partial/range matches
| Status | ||
|---|---|---|
|
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
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.
- is this for all service and/or HAProxy?
- Where are the certificates coming from (OOM/gerrit/generated by AAF)
12th June 2019: Jonathan Gathman demonstrated aaf-hello functionality at DDF event
- James Forsyth create JIRA task for this topic
| Viewtracker report |
|---|