2019-07-03 AAI Meeting Notes
Recording:
Recorded Session - 2019-07-03.mp4
Attendees:
START RECORDING
| 1 | Vetting DSL Queries | @Manisha Aggarwal @William Reehil | Will discuss strategies AAI will employ to protect itself from rogue queries. | |
| 2 | 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. | |
| 3 | 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. | |
| 4 | Alternative meeting system | Just in case Zoom problems continue, try this instead: | ||
| 5 | Global JJB issue | @James Forsyth | Hi Jimmy, aai common has one issue: When the job tries to sign the jar artifacts, it finds the m2repo empty which means there are no artifacts being prepared for deployment. @Jessica Gonzalez : I see some errors in the full log file: 09:59:26 ERROR: git-review 1.24 requires argparse, which is not installed.
09:59:26 ERROR: openstacksdk 0.31.1 has requirement ipaddress>=1.0.17; python_version < "3.3", but you'll have ipaddress 1.0.16 which is incompatible.
09:59:26 ERROR: openstacksdk 0.31.1 has requirement PyYAML>=3.12, but you'll have pyyaml 3.10 which is incompatible.
09:59:26 ERROR: pyasn1-modules 0.2.5 has requirement pyasn1<0.5.0,>=0.4.1, but you'll have pyasn1 0.1.9 which is incompatible.
09:59:26 ERROR: python-heatclient 1.16.2 has requirement PyYAML>=3.12, but you'll have pyyaml 3.10 which is incompatible.
09:59:26 ERROR: oslo-config 6.10.0 has requirement PyYAML>=3.12, but you'll have pyyaml 3.10 which is incompatible.
09:59:26 ERROR: yq 2.7.2 has requirement PyYAML>=3.11, but you'll have pyyaml 3.10 which is incompatible.
09:59:26 ERROR: requests 2.22.0 has requirement idna<2.9,>=2.5, but you'll have idna 2.4 which is incompatible.
09:59:26 ERROR: oslo-serialization 2.29.1 has requirement PyYAML>=3.12, but you'll have pyyaml 3.10 which is incompatible.
09:59:26 ERROR: cliff 2.15.0 has requirement PyYAML>=3.12, but you'll have pyyaml 3.10 which is incompatible.
...
09:59:57 [aai-aai-common-maven-stage-master] $ /w/tools/hudson.tasks.Maven_MavenInstallation/mvn35/bin/mvn -f -s /tmp/settings6002355141556927426.xml -gs /tmp/global-settings1115787293230334266.xml -DGERRIT_BRANCH=master -DPROJECT=aai/aai-common -DMVN=/w/tools/hudson.tasks.Maven_MavenInstallation/mvn35/bin/mvn -DSTREAM=master -DARCHIVE_ARTIFACTS= -DGERRIT_PROJECT=aai/aai-common -Dsha1=origin/master -DMAVEN_OPTS= -DGERRIT_REFSPEC=refs/heads/master -DM2_HOME=/w/tools/hudson.tasks.Maven_MavenInstallation/mvn35 -DSTAGING_PROFILE_ID=176c31dfe190a -DMAVEN_VERSIONS_PLUGIN=true -DMAVEN_PARAMS= -DnewVersion=1.5.2 versions:set versions:update-child-modules versions:commit -B
09:59:57 POM file specified with the -f/--file command line argument does not exist
...
10:00:11 [INFO] Downloading from EvoSuite: http://www.evosuite.org/m2/org/codehaus/mojo/maven-metadata.xml
10:00:11 [WARNING] Could not transfer metadata org.apache.maven.plugins/maven-metadata.xml from/to EvoSuite (http://www.evosuite.org/m2): Connect to www.evosuite.org:80 [www.evosuite.org/5.9.82.144] failed: Connection refused (Connection refused)
10:00:11 [WARNING] Could not transfer metadata org.codehaus.mojo/maven-metadata.xml from/to EvoSuite (http://www.evosuite.org/m2): Connect to www.evosuite.org:80 [www.evosuite.org/5.9.82.144] failed: Connection refused (Connection refused)
10:00:11 [INFO] Downloading from EvoSuite: http://www.evosuite.org/m2/org/codehaus/mojo/versions-maven-plugin/maven-metadata.xml
10:00:11 [WARNING] Could not transfer metadata org.codehaus.mojo:versions-maven-plugin/maven-metadata.xml from/to EvoSuite (http://www.evosuite.org/m2): Connect to www.evosuite.org:80 [www.evosuite.org/5.9.82.144] failed: Connection refused (Connection refused)
These seem relevant to a failed build. | |
| 6 | 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 | |
| 7 | New support ticketing for LF | @James Forsyth | ||
| 8 | 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 | |
| 9 | 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. | ||
| 10 | DSL documentation page | @Keong Lim | The new DSL documentation page looks good: DSL API (BYOQ - Bring Your Own Query) Looking forward to further discussion and experimentation! | |
| 11 | Global JJB | @James Forsyth | Sonatype's maven-staging-plugin will be disabled and we need to implement new LF jenkins jobs before mid-July Repos and do they use oparent: | |
| 12 | Dublin Blockers | @James Forsyth | https://lf-onap.atlassian.net/browse/AAI-2406 | |
| 13 | El Alto Review | @James Forsyth | JIRA Epic/Story count: | |
| 14 | El Alto Status | @James Forsyth |
| |
| 15 | 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?) | |
| 16 | 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?) | |
| 17 | Run AAI containers as non-root user | @James Forsyth | https://wiki.onap.org/display/DW/Best+Practices
| |
| 18 | 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 | |
| 19 | GraphGraph demo | @Former user (Deleted) | A 5-10 minute demo of GraphGraph. Feedback needed! | |
| 20 | Bug Review | JIRA Issue Count (in AAI project): JIRA Issue Count (talking about AAI): | ||
| 21 | 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 | |
| 22 | Gerrit Review | |||
| 23 | Sonar Review | |||
| 24 | Jenkins CLM Review | |||
| 25 | Helm Chart Transfer | @James Forsyth | @James Forsythwill start a document with best practices and requirements for merging changes to the aai/oom submodule Team needs to document (perhaps change the AAI guide for OOM setup) the change to use the submodule in OOM | |
| 26 | 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 | |
| 27 | Dublin Status 1 | @James Forsyth |
| |
| 28 | 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
| |
| 29 | 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. | |
| 30 |