Page History

 Introduce MDONS Use Case  Multi-domain Optical Network Services

  and its impact on AAI in Frankfort AAI MDONS Proposal for Frankfort Release

Pavel Paroulek

Pavel Paroulek Venkata Harish Kajur

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).

Pavel Paroulek

Ongoing progress to flash out possible validation rules for the schema AAI Schema and EdgeRule Audit rules

Venkata Harish Kajur

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.

Ranvijay Singh

Pavel Paroulek

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

28th May: Stela Stoykova is fixing

https://gerrit.onap.org/r/c/aai/cacher/+/85319

•  Pavel Paroulek 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 12 Sep 2019 

Pavel Paroulek

Is there a guide for the description of the error message and the error codes? How are new error states (message + code) added?

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?

15th Dec: https://wiki.onap.org/display/DW/Pluggable+Security#PluggableSecurity-7.10Identifiedandsupportedpatternsandfeatures

•  James Forsythcreates a task for encryption of communication between A&AI services and Cassandra 12 Sep 2019
  
•  Tian Lee and Steven Blimkie to report on the Amdocs managed A&AI microservice wheter they support criteria from the Dublin S3P requirements 31 Jan 2019 
  

•  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
  

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 12 Sep 2019