Recording:
Attendees:
START RECORDING
1 | Dublin Status 1 | James Forsyth |
| |
2 | Dublin Status 2 / OOM helm charts |
| ||
3 | Dublin Status 3 | James Forsyth |
| |
4 | Dublin Status 4 | James Forsyth | Champ slipped below 55% with latest commit.
| |
5 | Dublin Use Cases | Epic-of-epics: - AAI-2107Getting 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 | ||
6 | El Alto Status | James Forsyth |
| |
7 | New business | Please add new items below | ||
8 | 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 | ||
9 | Container Images | Container Image Minimization Guidelines | ||
10 | Strange dependency in ESR | |||
11 | Blocker | J. Ram Balasubramanian | - AAI-2202Getting issue details... STATUS
| |
12 | 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. user-b8310 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 | schema-service has v16 files | Is v15 API for Dublin release? - AAI-1811Getting issue details... STATUS Why does schema-service now have v16 files? - AAI-2161Getting issue details... STATUS
| ||
14 | Run AAI containers as non-root user | https://wiki.onap.org/display/DW/Best+Practices
| ||
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 | Dublin 5G Use Case | Go to [usecase] Platform Evolution for Use Case Realization w/ SO, AAI, DCAE, SDC, VID, SDNC | ||
17 | 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? | ||
18 | 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-2154Getting 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 ? | ||
19 |
Open Action Items
New Action items
- 2019-03-27 AAI Meeting Notes Tian Lee will do babel, model-loader, champ, gizmo, event-client, spike, rest-client, validation
- 2019-03-27 AAI Meeting Notes Arul Nambi will do sparky-be, search-data-service, data-router, logging-service, router-core
- 2019-03-27 AAI Meeting Notes Venkata Harish Kajur will check aai-common, resources, traversal, graphadmin, cacher, schema-service (which probably already have the setting)
- 2019-03-27 AAI Meeting Notes James Forsyth will request 2019-03-27 AAI Meeting Notes access to Zoom 10
- 2019-03-27 AAI Meeting Notes Venkata Harish Kajur could you please update procedures for schema-service implementation?
- Documentation on the search/nodes-query API is missing. 2019-03-27 AAI Meeting Notes James Forsyth needs to find it and publish it.
- 2019-03-27 AAI Meeting Notes James Forsyth Document nodes wiki and add explanation about presence of the v15 file. Should add v14-v15 changes to release notes.