Skip to end of metadata
Go to start of metadata

Attachments (including meeting recording)

No files shared here yet.



Status

OPEN

IN PROGRESS

ON HOLD

DONE

CANCELLED

Agenda Items

START RECORDING


TitleRaised ByStatusLast discussedNotes
1



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

Jimmy 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

2ui_view role in AAF

IN PROGRESS


AAI-2475 - Getting issue details... STATUS

AAF-986 - Getting issue details... STATUS

3 AAI Impact in R6 - MDONS Use Case Xin Miao

IN PROGRESS

 2019-09-19

 Introduce MDONS Use Case  Multi-domain Optical Network Services

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

AAI-2623 - Getting issue details... STATUS

4AAF autocert

ON HOLD

2019-09-12

Work-in-progress https://gerrit.onap.org/r/c/aai/oom/+/96156 

TODO: 

  • restclient should support reading AAF passwords
  • AAF should expose passwords in .password file
  • application.properties needs to be updated 

The above is also mentioned in the gerrit comments

5No free nodeports in the 302XX range

ON HOLD

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

AAI-2624 - Getting issue details... STATUS

6Helm Chart Common Templates

ON HOLD

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.

7AAI Use Cases


8Return 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?

  • William LaMont will send Jimmy Forsyth the output of a script that formats the error.properties file to make a wiki page and readthedocs
  • Jimmy Forsyth should commit that script and create a wiki for the error properties

Page viewed times