2019-07-24 AAI Meeting Notes
Recording:
Recorded Session - 2019-07-24.mp4
Attendees:
@James Forsyth
@William LaMont
@Keong Lim
@Ondrej F
@Benjamin Cheung
@Manisha Aggarwal
@Venkata Harish Kajur
@Hitesh Vaghani
@Francis Paquette
@Kuldeep Singh Negi (Deactivated)
@Shirley Morgan
START RECORDING
| 1 | Why is the resources pod trying to clone aai-config? | @James Forsyth @Reshmasree c | @Keong Lim and @FREEMAN, BRIAN D have both responded on mailing list, we need more info to be able to to troubleshoot this, it seems like its referencing repos that have not been in use Release 1 (Amsterdam) in Oct 2017. | |
| 2 | Janusgraph 0.2.3 | @James Forsyth | https://lf-onap.atlassian.net/browse/AAI-2420 @James Forsyth is going to merge updates to JanusGraph, 0.2.0 → 0.2.3 in master, should be a drop in replacement. | |
| 3 | Performance Issue | @James Forsyth | @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"} | |
| 4 | Spring Boot 2 | @James Forsyth | 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. | |
| 5 | Upcoming R6 Functional Requirements | @Benjamin Cheung | Release 6 (Frankfurt) proposed use cases and functional requirements | |
| 6 | Round trip reverse engineering of the AAI data model | @James Forsyth @Keong Lim @William LaMont | We provided a parseable JSON schema. Team wants follow up meeting, @James Forsyth will set it up. | |
| 7 | Alpine images | @Dmitry Puzikov (Deactivated) | Jenkins jobs needed to create / push the common alpine image that the AAI containers will use, still need this completed before we merge the outstanding commits. | |
| 8 | Microservices enabled by default in aai/oom | @James Forsyth | The ones in bold will be turned "off" by default: aai-babel aai-elasticsearch aai-modelloader aai-search-data aai-traversal aai-champ aai-gizmo aai-resources aai-sparky-be aai-data-router aai-graphadmin aai-schema-service aai-spike We will add are release note about how to turn off the ones in italics for users that want a true minimum set without the UI | |
| 9 | Global JJB Status | @James Forsyth @Francis Paquette | Global JJB transition Complete! | |
| 10 | Vetting DSL Queries | @Manisha Aggarwal @William Reehil | Will discuss strategies AAI will employ to protect itself from rogue queries. | |
| 11 | AAI History | @Philip Blackwood | Discuss and review Scenarios for using historical inventory and topology | |
| 12 | Casablanca to Dublin Migration | @Ankit Bhatt | 3rd July: raised https://lf-onap.atlassian.net/browse/AAI-2507 based on Ankit's analysis that found the change in EdgeRules. | |
| 13 | Build styles | @James Forsyth | We have too many ways to build and deploy artifacts, which makes it difficult and time-consuming. Some of our artifacts are not backward compatible and we need to move everything up to released versions. | |
| 14 | Alternative meeting system | Just in case Zoom problems continue, try this instead: | ||
| 15 | New UI Features / Historical Tracking | @William Reehil @Manisha Aggarwal | 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 | |
| 16 | New support ticketing for LF | @James Forsyth | ||
| 17 | Dublin Issue | @Reneal Rogers | sparky-be expired certificate - status @James Forsyth will add note to known issues using info provided by @Reneal Rogersand @Francis Paquette and make sure dublin docs branch is synced. https://lf-onap.atlassian.net/browse/AAI-2489 https://lf-onap.atlassian.net/browse/DOC-486- opened because the docs are not syncing even though dublin matches master @Francis Paquette will work https://lf-onap.atlassian.net/browse/AAI-2490 | |
| 18 | Dublin Issue | https://lf-onap.atlassian.net/browse/PORTAL-596 - In future, AAI team needs to open Jira bugs against systems that are misconfigured or missing data when we become aware of the issue. | ||
| 19 | Global JJB | @James Forsyth | Sonatype's maven-staging-plugin will be disabled and we need to implement new LF jenkins jobs before mid-July
| |
| 20 | Dublin Blockers | @James Forsyth | https://lf-onap.atlassian.net/browse/AAI-2406 | |
| 21 | El Alto Review | @James Forsyth | JIRA Epic/Story count: | |
| 22 | El Alto Status | @James Forsyth |
| |
| 23 | Selenium Tests in Sparky | @Arul Nambi | Want to share in the community potential selenium changes for the sparky UI (bumped up, is it still relevant?) | |
| 24 | 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. (bumped up, is it still relevant?) | |
| 25 | Run AAI containers as non-root user | @James Forsyth | https://wiki.onap.org/display/DW/Best+Practices
| |
| 26 | Container Images | @James Forsyth | Container Image Minimization Guidelines @James Forsyth will ask integration team if we can use the AAI tenant space in windriver environment | |
| 27 | Bug Review | JIRA Issue Count (in AAI project): JIRA Issue Count (talking about AAI): | ||
| 28 | Dublin branching | @James Forsyth | Dublin artifacts are released and jjb jobs are updated to drop casablanca jobs and replace with dublin We will change the sonar and clm jobs to use the dublin branch @James Forsyth will see how other teams manage merging release bug/security/late feature change back to master | |
| 29 | Gerrit Review | |||
| 30 | Sonar Review | |||
| 31 | Jenkins CLM Review | |||
| 32 | Status of ARC documentation | @Former user (Deleted) | When is this going to be finished ARC AAI Component Description - Dublin ? Note: I have no idea what it is, I just was asked to inquire | |
| 33 | Dublin Status 1 | @James Forsyth |
| |
| 34 | Dublin Status 3 | @James Forsyth |
@James Forsyth will open Jira tickets to update the keystores in the master branches of the mS that use https @Arul Nambi will do sparky-be, search-data-service, data-router, logging-service, router-core
| |
| 35 | Code Coverage Status | @James Forsyth |
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> Sonar job for Dublin has been changed to using line coverage. | |
| 36 |