Page Comparison

...

BlockerDocumentation requestschema-service has v16 filesAAI

Saw this change https://gerrit.onap.org/r/#/c/81867

which configures the AAI URL path "aai.serviceInstanceQuery=

1

Dublin Status 1

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,

James Forsyth will request Keong Lim access to Zoom 10

CSIT on OOM needs to cover more of the services - See
Jira Legacy
server System Jira
serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
key AAI-2208

2

Dublin Status 2 / OOM helm charts

James Forsyth

Venkata Harish Kajur

Moving Helm charts into AAI repos

Former user (Deleted) is the AAI contact for doing the helm chart migration, info passed along to Mike Elliot

Migration of the oom / aai charts to an new repo that we will have commit access to. Harish tried to preserve the history on the existing set of files, but there was no way to do it because the commit messages would violate the 50 character limit. So we will lose history on the commits and do the push as a new code drop.
Jessica found a way to do it
Not sure if this would be pushed into El Alto release

3

Dublin Status 3

James Forsyth

Volumed run-time generated certificates are possible

James Forsyth Our AAF-issued certificate expires at the end of May.
subject=/C=US/O=ONAP/OU=aai@aai.onap.org/OU=OSAAF/CN=aai
issuer=/C=US/O=ONAP/OU=OSAAF/CN=intermediateCA_1
notAfter=May 31 12:19:59 2019 GMT
Need to generate new cert that expires in June 2021 and publish in the Casablanca emergency maintenance release.
Jira Legacy
server System Jira
columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
key TSC-120

https://onap.readthedocs.io/en/latest/submodules/aaf/authz.git/docs/sections/configuration/AAF_4.1_config.html
Will need to add the file for the haproxy in values.yaml since a limit on secrets meant we had to bake it into the haproxy container previously

GraphGraph is coming, depends on expanding schema-service API
RestClient updates are potentially being contributed by community members

4

Dublin Status 4

James Forsyth

code coverage to 55% for Dublin
Jira Legacy
server System Jira
serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
key AAI-2219

Champ slipped below 55% with latest commit.

Tian Lee will do babel, model-loader, champ, gizmo, event-client, spike, rest-client, validation
Arul Nambi will do sparky-be, search-data-service, data-router, logging-service, router-core
Venkata Harish Kajur will check aai-common, resources, traversal, graphadmin, cacher, schema-service (which probably already have the setting)
Add thresholds to all repos that are above 55% so it doesn't happen again
For setting the threshold on each repo, set it to the current percentage, so if it's is at 62.7%, set the threshold to 0.62

<jacoco.line.coverage.limit>0.68</jacoco.line.coverage.limit>

Code Block

  <execution>
                        <id>default-check</id>
                        <goals>
                            <goal>check</goal>
                        </goals>
                        <configuration>
                            <dataFile>${project.build.directory}/coverage-reports/jacoco.exec</dataFile>
                            <rules>
                                <!--  implementation is needed only for Maven 2  -->
                                <rule implementation="org.jacoco.maven.RuleConfiguration">
                                    <element>BUNDLE</element>
                                    <limits>
                                        <limit implementation="org.jacoco.report.check.Limit">
                                            <counter>LINE</counter>
                                            <value>COVEREDRATIO</value>
                                            <minimum>${jacoco.line.coverage.limit}</minimum>
                                        </limit>
                                    </limits>
                                </rule>
                            </rules>
                        </configuration>
                    </execution>

5

Dublin Use Cases

James Forsyth

Epic-of-epics:

Jira Legacy

server	System Jira
serverId	4733707d-2057-3a0f-ae5e-4fd8aff50176
key	AAI-2107

5G Use Case (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

6

El Alto Status

James Forsyth

No 2 way TLS in Dublin; James Forsyth will socialize early in El Alto, Due 03 Jun 2019
pnf-id change pushed to El Alto during Architecture review AAI R4 Architecture Review - 5 Mar 2019
API version update for El Alto should be co-ordinated for earlier in the cycle

7

New business

Please add new items below

8

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

9

Container Images

James Forsyth

Container Image Minimization Guidelines

10

Strange dependency in ESR

James Forsyth

Can anyone look at this one?

Jira Legacy

server	System Jira
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	4733707d-2057-3a0f-ae5e-4fd8aff50176
key	AAI-1970

11

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.

Jira Legacy

server	System Jira
serverId	4733707d-2057-3a0f-ae5e-4fd8aff50176
key	AAI-2172

12

Dublin 5G Use Case

Benjamin Cheung

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

13

Traversal Nodes query documentation

J. Ram Balasubramanian

Jira Legacy

server	System Jira
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	4733707d-2057-3a0f-ae5e-4fd8aff50176
key	AAI-2202

Documentation on the search/nodes-query API is missing. James Forsyth needs to find it and publish it.

12

14

AAI achitecture documentation

Taranjit Singh (Deactivated)

Understanding the architecture of AAI is not easy - hard to understand how the code is laid out and how things flow. Need documention which will describe how the microservices are connected, which repos support which functions, etc. Former user (Deleted) says that he had to reverse engineer the dependencies to see how the repos are connected. Recommended to focus on the resources repo for understanding the core function of AAI.

13

15

API version documentation

Keong Lim

Is v15 API for Dublin release?

Jira Legacy

server	System Jira
serverId	4733707d-2057-3a0f-ae5e-4fd8aff50176
key	AAI-1811

Why does schema-service now have v16 files?

Jira Legacy

server	System Jira
serverId	4733707d-2057-3a0f-ae5e-4fd8aff50176
key	AAI-2161

James Forsyth Document nodes wiki and add explanation about presence of the v15 file. Should add v14-v15 changes to release notes.

14

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.

Jira Legacy

server	System Jira
serverId	4733707d-2057-3a0f-ae5e-4fd8aff50176
key	AAI-2172

15

16

AAI data model principles document

James Forsyth will set up a separate session to provide ideas on what should be in the 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

16

Dublin 5G Use Case

Benjamin Cheung

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

17

Documentation incomplete or code bug?

Keong Lim

17

Resources Nodes query documentation incomplete

Keong Lim

API Documentation needs update, as both of these URL paths are equally valid:

/aai/v13/nodes/{plural}/{singular}
/aai/v13/nodes/

service-instance/

{

0

singular}

"

According to documentationSee also: https://onap.readthedocs.io/en/casablanca/submodules/aai/aai-common.git/docs/AAI%20REST%20API%20Documentation/nodesQuery.html#api-uri

The URL path should have been "/aai/v13/nodes/service-instances/service-instance/{0}" but tests show that both URL paths work equally well.

Is the documentation incomplete? or is there a code bug letting it pass through?

18

AAI Dublin wiki updates

Keong Lim

Venkata Harish Kajur

Added pages to AAI in Dublin Release

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)

12th Mar: messages from onap-discuss list and wiki comments show that there is still confusion and/or missing steps for the Dublin tutorial, need to sync with current code

18th Mar: David Perez Caparros had problems with v16 in

Jira Legacy

server	System Jira
serverId	4733707d-2057-3a0f-ae5e-4fd8aff50176
key	AAI-2154

.

Noticed several gerrit reviews for API v16 support:

Either it was premature to make v16 known during Dublin development or they should be co-ordinated for earlier in the cycle.

Note that these changes also include deprecation of v8 and v9. Is that new change or catching up on old changes?

Again, reinforces a sentiment from previous meeting "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."

Related to "rolling upgrades", I would rather see a system where old versions can be disabled by stopping pods/containers and new versions can be enabled by starting pods/containers, with the haproxy or MSB directing requests to appropriate api-version-based servers for processing.

Is that a future that should be discussed with Stephen terrill in ONAPARC e.g. ARC AAI Component Description - Dublin ?Please keep these procedures up-to-date with latest Dublin code.

19

Open Action Items

New Action items

...

Versions Compared

Old Version 2

New Version 3

Key

Open Action Items

New Action items