2020-08-05 AAI Meeting Notes
- Shirley Morgan
- William Reehil
Attachments (including meeting recording): 20200805 AAI Weekly Meeting.mp4
Attendees:
@William Reehil
@Igor Dysko
@Neil Derraugh
@Venkata Harish Kajur
@rodrigo lima
@Starec Vlastimil
Agenda Items:
@Igor Dysko asked about a use case and the least amount of mS to support it for aai (resources, traversal, graphadmin, schema-service, cassandra backend)
@Neil Derraugh asked about contributing a dupe issue fix in Frankfurt on a single instance
Is there any other window for a maintenance release on the Frankfurt branch? @William Reehil to ask on PTL call
@Neil Derraugh asked about automated load testing in the pipeline, we do not have this currently. We do have some extensive testing internally to AT&T, but have not had the resources to deliver it to ONAP (load testing with gatling, functional testing with robot)
Status | OPEN | IN PROGRESS | ON HOLD | DONE | CANCELLED |
|---|
START RECORDING
| 1 | AAI CNF Modeling | OPEN | AAI ← link to the AAI weekly CNF call. This team will be doing modeling work to decide how CNFs will be modelled in AAI | ||||||||||||||
| 2 | aai/oom chart | Currently AAI manages our own helm chart as a submodule of oom, at Frankfurt release sign-off, the oom team will pull the aai charts back into the main repo. We will still have to maintain the aai/oom repo in case a patch is needed for elalto or frankfurt. Jimmy contacted Sylvain on this topic, requesting they (oom team) handle this work and we support, awaiting response. | |||||||||||||||
| 3 | Guilin requirements | OPEN | AAI R7 Guilin Release: TSC must have requirements AAI R7 Guilin Release: Functional Use Cases | ||||||||||||||
| 4 | Requirements for inclusion of GraphGraph in Guilin release | OPEN | List goes here Open Jira tickets as tasks for G release https://lf-onap.atlassian.net/browse/AAI-2910 https://lf-onap.atlassian.net/browse/AAI-2911 | ||||||||||||||
| 5 | Document AAI repo and microservice descriptions | Ondrej | OPEN | Put the link here for the document; we will share with the community and solicit feedback from repo/mS owners about the document. | |||||||||||||
| 6 | Frankfurt Defects | ||||||||||||||||
| 7 | SOTNNI use case | @shashikanth.vh | https://gerrit.onap.org/r/c/aai/schema-service/+/102298 | ||||||||||||||
| 8 | Security Requirements for pods | @James Forsyth | |||||||||||||||
| 9 | @Ondrej F | OPEN | Graphgraph not included in OOM deployment. How can we make it an essential part of the ONAP deployment. Step 0: Make it stable. Fix the docker build Jenkins jobs for graphgraph, may need to upgrade to a version of npm to be acceptable to graphgraph. Needs to fit into the LF global-job jobs. | ||||||||||||||
| 10 | Brownfield / deployed / embedded inventory systems and AAI | Fred from Verizon | OPEN | How do we accelerate migration using A&AI and the RunTime DB solution Proposed a topic to be explored by AI&I and other ONAP WGs. High impact, common interest among most CSPs Status Quo: Most operators have multiple, siloed, possibly overlapping topology and inventory (domain specific) databases Goal is to integrate ALL Inventory, and Topology databases into a Unified AI&I Architecture modeled DB which would contain ALL VNFs (VMs/Containers), PNFs, plus support easy expansion for future Inventory & Topology constructs/technologies. May take considerable time/investment (both are short).
Targeted Objectives
How to accelerate the migration to Unified Database?
| |||||||||||||
| 11 | Looking for volunteer to fix papyrus issue | OPEN | https://lf-onap.atlassian.net/browse/AAI-2771 Graphgraph doesn't parse the latest AAI schema correctly. Need someone to investigate | ||||||||||||||
| 12 | sparky and data-router certificate issue | @Francis Paquette | IN PROGRESS | Sparky is using the AAF certificate interaction with Portal but a self-signed certificate to talk to search-data-service. The search-data-service key story was removed. https://lf-onap.atlassian.net/browse/AAI-2765 https://lf-onap.atlassian.net/browse/AAI-2766 | |||||||||||||
| 13 | Collab efforts | @James Forsyth @Giulio Graziani @Kuldeep Singh Negi @Former user (Deleted) | IN PROGRESS | ||||||||||||||
| 14 | Java 11 | @James Forsyth | ON HOLD | @Venkata Harish Kajur tried schema service, a couple of dependency changes were required to get it to start. Eclipselink that is currently configured is incompatible. <groupId>javax.activation</groupId> is also incompatible Needs more investigation for other repos Need new common image (which Alpine image would we pick?) | |||||||||||||
| 15 | AAI Bugs | @James Forsyth | IN PROGRESS |
| |||||||||||||
| 16 | Performance Issue | @James Forsyth | OPEN | @FREEMAN, BRIAN D reported that when there are ~2400 vservers returned in a closed loop custom query, AAI takes minutes to respond. We've discussed paging previously, any other ways to optimize this? PUT 'https://aai.onap:8443/aai/v16/query?format=resource' {"query":"query/closed-loop","start":"/cloud-infrastructure/cloud-regions/cloud-region/CloudOwner/RegionOne/tenants/tenant/28481f6939614cfd83e6767a0e039bcc/vservers/vserver/6ad9eb6b-d7fc-46d6-8617-4c9b46e7308b"} | |||||||||||||
| 17 | Spring Boot 2 | @James Forsyth | IN PROGRESS | https://lf-onap.atlassian.net/browse/AAI-2111 aai-common:1.5.2 (not released yet) will be the el-alto library for springboot 1.5.x microservices. There needs to be some urgency to migrate the microservices to spring boot 2, since 1.5.3+ will not be backward compatible and so dependent applications might not have security updates if they stay on 1.5.2. 1.6.0 (Frankfort, currently master branch) aai-common will be springboot 2 so microservices must be updated by Frankfurt. Springboot 1.5.21 is the latest (and last) version in the 1.5.x spring boot train. | |||||||||||||
| 18 | New UI Features / Historical Tracking | @William Reehil @Manisha Aggarwal | OPEN | The AT&T team has done an exciting POC at a sprint-a-thon event that they would like to share with the community. ATT wants to contribute additional UI views to ONAP, want to discuss path forward Link for self repo creation: https://lf-onap.atlassian.net/wiki/display/DW/Self+Repo+Creation+via+INFO.yaml William/Jimmy will look into this for creating the new sparky extensions repository |