Recording:
Attendees:
START RECORDING
| 1 | 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,
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 code coverage to 55% for Dublin AAI-2219 - Getting issue details... STATUSCSIT on OOM needs to cover more of the services - See
AAI-2208
-
Getting issue details...
STATUS
| |
| 2 | New business | Please add new items below | ||
| 3 | Documentation incomplete or code bug? | Saw this change https://gerrit.onap.org/r/#/c/81867 which configures the AAI URL path "aai.serviceInstanceQuery=/aai/v13/nodes/service-instance/{0}" According to documentation: 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? | ||
| 4 | AAI Dublin wiki updates | 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 AAI-2154 - Getting issue details... STATUS . 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 ? | ||
| 5 | Strange dependency in ESR | Can anyone look at this one? AAI-1970 - Getting issue details... STATUS | ||
| 6 | Blocker | J. Ram Balasubramanian | AAI-2202 - Getting issue details... STATUS
| |
| 7 | Documentation request | 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. | ||
| 8 | OOM helm charts | 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 existingn 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. | ||
| 9 | PNF object in Dublin | James Forsyth | Status of Architecture review AAI R4 Architecture Review - 5 Mar 2019 | |
| 10 | Dublin Use Cases | Epic-of-epics: AAI-2107 - Getting issue details... STATUS BBS Broadband Service 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 | ||
| 11 | NFVO added to ESR | 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 | ||
| 12 | Container Images | Container Image Minimization Guidelines | ||
| 13 | schema-service has v16 files | 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
| ||
| 14 | Run AAI containers as non-root user | https://wiki.onap.org/display/DW/Best+Practices
AAI-2172 - Getting issue details... STATUS | ||
| 15 | 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 | ||
| 16 | Custom query design | James Forsyth | ||
| 17 | Dublin 5G Use Case | Go to [usecase] Platform Evolution for Use Case Realization w/ SO, AAI, DCAE, SDC, VID, SDNC |