2019-02-27 AAI Meeting Notes

NFVO added to ESR

@t

can we discuss in this meeting on NFVO as new node in esr system info for the SOL 005 usecase: Support ETSI NFV-SOL 005 (Os-Ma-Nfvo ref point ) between SO & VF-C/NFVO

AAI-2194: Support ETSI NFV-SOL 005 (Os-Ma-Nfvo ref point ) between SO & VF-C/NFVOClosed

Container Images

@James Forsyth

Container Image Minimization Guidelines

schema-service has v16 files

@Keong Lim

Is v15 API for Dublin release? AAI-1811: Add support for v15 version of APIsClosed

Why does schema-service now have v16 files? AAI-2161: Add support for v16 version of APIsClosed

Dublin: circular dependency between aai-common and schema-service causes build failure

@Keong Lim

While building aai-common, aai-common/aai-core has dependency on schema-service (build fails).

While building schema-service, schema-service/aai-schema-gen has dependency on aai-common/aai-schema-ingest (build fails).

Seems like a circular dependency between aai-common and schema-service, with both builds broken on the first pass.

On the second or subsequent passes, there might be enough libraries built to make it work again, but that's very unclean.

Currently, it might be passing when downloading artifacts because it's actually pulling older versions from maven repositories, similar to the "second or subsequent passes" described above.

Pulling from maven repositories is no good for testing changes to schemas in local dev environments (won't see the new schemas in the microservices, see also step 7 of AAI Tutorial-Making and Testing a Schema Change - Dublin messing around with "mvn versions:set -DnewVersion=0.0.1-TEST-SNAPSHOT" etc).

The build should be a DAG (directed acyclic graph) and work on a single-pass.

These really should not be separate repositories. There's too much coupling between the microservices to sensibly keep them as separate repositories. A single repository can already have multiple microservices/libraries/etc as artifacts.

https://gerrit.onap.org/r/#/c/79238/

Run AAI containers as non-root user

@James Forsyth

https://wiki.onap.org/display/DW/Best+Practices

• The Docker and Kubernetes engines may run as root until such time as the products support non-root execution.

• Applications may run as root within a container.

• The process ID of a container must not run as the root ID with the exception of containers supporting ONAP features that require the container to run as the root ID.

• Containers may run with root privileges.

• Project containers that run as the root ID must document this in the release notes along with the functionality that requires the container to run as the root ID.

AAI-2172: Change to use non-root user for containersClosed

Dublin Status

@James Forsyth

Encourage our clients to migrate off named query

Trying for Silver badge and Level 2 on Security; 50% code coverage on repos

Resiliency and fault tolerance; meeting notice never published,

CSIT on OOM needs to cover more of the services - no volunteers to look at this

Moving Helm charts into AAI repos

Volumed run-time generated certificates are possible

GraphGraph is coming

RestClient updates are potentially being contributed by community members

CSIT Robot Integration Sanity Test Cases

Need to maintain these for Dublin, and expand to include things like MSB integration. Establish a working group to develop CSIT test cases for Dublin and document them on the wiki. @James Forsyth will create the page and solicit ideas.

AAI R4 Integration Sanity Test Plans

See also Contributing To AAI Best Practise

AAI data model principles document

Looking to bring in SME who would document rules for A&AI schema principles, define design principles for data model. Document will serve as reference during code reviews for A&AI data model. @Chandra Cinthala is identified as the resource who will co-ordinate the activity

See also AAI Data Model Principles

AAI Dublin wiki updates

@Keong Lim

Added pages to AAI in Dublin Release

• AAI Developer Environment Setup - Dublin

• AAI Tutorial-Making and Testing a Schema Change - Dublin

@Venkata Harish Kajur could you please update procedures for schema-service implementation?

Will need this to work on Dublin schema changes (e.g. BBS use case)

Custom query design

@James Forsyth

MSB Configs

AAI-1964: Update AAI chart to include v14 URIs for MSB discoveryClosed

AAI-1965: Create wiki page documenting AAI MSB discovery config Closed

AAI-1966: Include v15 URIs in MSB config in AAI chartClosed

8th Jan: This one could be a problem: MSB-198: MSB GUI can not register a service mapped to an HTTPS endpoint Closed

Dublin Use Cases

@James Forsyth

5G Use Case (R4 Dublin)

BBS Broadband Service Use Case (Dublin)

CCVPN Use Case (Dublin)

Change Management Dublin Extensions

Fine Grain Placement Service (F-GPS) Edge Automation (Dublin)

OpenSource Access Manager (OSAM) Use Case

K8S based Cloud Region Support

Tony Noori from AT&T will identify the ONAP POC for system engineering for AAI modelling. This person will coordinate schema changes, watch the use case wiki, jira, perform gerrit reviews, etc.

Analysis: AAI R4 Use Case and Functional Requirements Impacts

SONAR

@James Forsyth

@Keong Lim and @James Forsyth will develop a strategy for the SONAR TD to allow for new devs to make productive use of their time; Suggestion of one task per repo with subtasks of items that need to be fixed.

Started wiki page Contributing To AAI By Assisting with Sonar Reports / AAI-2125: Sonar Report EnhancementsClosed

Also a similar one for Contributing To AAI By Assisting with Maven Warnings / AAI-2133: Contributing To AAI By Assisting with Maven warningsClosed

Dublin 5G Use Case

@Benjamin Cheung

Go to [usecase] Platform Evolution for Use Case Realization w/ SO, AAI, DCAE, SDC, VID, SDNC