Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Recording:


Attendees:



START RECORDING

1
sparky shows sonar failingJames Forsyth

AAI-2354 - Getting issue details... STATUS

2
Bug Review

JIRA Issue Count: Getting issues...

3
Dublin Status 1James Forsyth
  • Encourage our clients to migrate off named query
    • To support Policy code change to custom queries POLICY-1266 - Getting issue details... STATUS , could this be fixed? AAI-2351 - Getting issue details... STATUS
  • Trying for Silver badge and Level 2 on Security; 50% code coverage on repos
  • Resiliency and fault tolerance; meeting notice never published,
4
Dublin Status 2 / OOM helm charts
  • 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
5
Dublin Status 3James Forsyth
  • Volumed run-time generated certificates are possible
  • GraphGraph is coming, depends on expanding schema-service API
  • RestClient updates are potentially being contributed by community members
6
Dublin Status 4James Forsyth
  • code coverage to 55% for Dublin AAI-2219 - Getting issue details... STATUS

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
  • James Forsyth create ticket for El Alto for sparky, rolling back because of sonar failure
  • 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>

      <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>
7
Dublin Use Cases

Epic-of-epics: AAI-2107 - Getting issue details... STATUS

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

JIRA Epics count: Getting issues...

8
El Alto StatusJames Forsyth
  • No 2 way TLS in Dublin; James Forsyth will socialize early in El Alto, Due
  • 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
    • needs a checklist of things to be updated, including yang classes AAI-2351 - Getting issue details... STATUS


JIRA Epics count: Getting issues...

9
New business
Please add new items below
10
Selenium Tests in SparkyArul NambiWant to share in the community potential selenium changes for the sparky UI
11
Container Images

Container Image Minimization Guidelines

James Forsyth will ask integration team if we can use the AAI tenant space in windriver environment

12
Run AAI containers as non-root user

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 - Getting issue details... STATUS

13
Dublin 5G Use Case

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

14

Traversal Nodes query documentation

J. Ram Balasubramanian

AAI-2202 - Getting issue details... STATUS

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

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.

16
API version documentation

Is v15 API for Dublin release? AAI-1811 - Getting issue details... STATUS

Why does schema-service now have v16 files? AAI-2161 - Getting issue details... STATUS

  • James Forsyth Document nodes wiki and add explanation about presence of the v15 file. Should add v14-v15 changes to release notes.
17
Resources Nodes query documentation incomplete

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

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

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


18
AAI Dublin wiki updates

Added pages to AAI in Dublin Release

Please keep these procedures up-to-date with latest Dublin code.


19



Open Action Items



  • No labels