| Attachments |
|---|
Recording:
Attendees:
START RECORDING
...
...
...
...
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.
31st Jul: Discussion on https://lists.onap.org/g/onap-users/topic/32571389 says it was resolved after tweaking the repository values in values.yaml
...
...
Himesh
ranvijay.s
START RECORDING
| 1 | 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.
| 24203 | Performance Issue | 4 | Spring Boot 2 | James Forsyth | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Jira Legacy | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| server | System Jira | columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 2 | Microservices enabled by default in aai/oom | 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
| 21115 | 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 |
| 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 | 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 | 10 | Vetting DSL Queries | 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 |
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
Just in case Zoom problems continue, try this instead:
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
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.
Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key AAI-2489
- opened because the docs are not syncing even though dublin matches masterJira Legacy server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key DOC-486 - Francis Paquette will work
Jira Legacy server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key AAI-2490
| Jira Legacy | ||||||||
|---|---|---|---|---|---|---|---|---|
|
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:
./model-loader/pom.xml true ./graphgraph/pom.xml false ./graphadmin/pom.xml true ./esr-server/pom.xml true ./sparky-be/pom.xml true ./rest-client/pom.xml true ./aai-common/pom.xml true ./data-router/pom.xml false ./chameleon/pom.xml false ./sparky-fe/pom.xml false ./event-client/pom.xml true ./gallifrey/pom.xml false ./resources/pom.xml true ./router-core/pom.xml true ./gizmo/pom.xml true ./logging-service/pom.xml true ./babel/pom.xml true ./champ/pom.xml true ./traversal/pom.xml true ./spike/pom.xml true ./esr-gui/pom.xml true ./search-data-service/pom.xml false ./cacher/pom.xml true ./schema-service/pom.xml true ./validation/pom.xml true
| Jira Legacy | ||||||||
|---|---|---|---|---|---|---|---|---|
|
| Jira Legacy | ||||||||
|---|---|---|---|---|---|---|---|---|
|
2549
JIRA Epic/Story count: Jira Legacy server System Jira jqlQuery project = AAI AND issuetype in (Epic,Story) AND fixVersion = "El Alto Release" ORDER BY created DESC count true serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
Seeking comments and reviews on OOM Repository for Release and Staging Environments Proposal
Will have impact on how the aai/oom repository is managed as well.
| Jira Legacy | ||||||||
|---|---|---|---|---|---|---|---|---|
|
James Forsyth is going to merge updates to JanusGraph, 0.2.0 → 0.2.3 in master, should be a drop in replacement.
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"}
| Jira Legacy | ||||||||
|---|---|---|---|---|---|---|---|---|
|
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.
Release 6 (Frankfurt) proposed use cases and functional requirements
Moved to new meeting:
Global JJB transition Complete!
3rd July: raised
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
JIRA Epic/Story count: Jira Legacy server System Jira jqlQuery project = AAI AND issuetype in (Epic,Story) AND fixVersion = "El Alto Release" ORDER BY created DESC count true serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
|
Just in case Zoom problems continue, try this instead:
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
Want to share in the community potential selenium changes for the sparky UI
(bumped up, is it still relevant?)
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?)
https://wiki.onap.org/display/DW/Best+Practices
- The Docker and Kubernetes engines may run as root until such time as the products support non-root execution.
- Applications may run as root within a container.
- The process ID of a container must not run as the root ID with the exception of containers supporting ONAP features that require the container to run as the root ID.
- Containers may run with root privileges.
- Project containers that run as the root ID must document this in the release notes along with the functionality that requires the container to run as the root ID.
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
Container Image Minimization Guidelines
James Forsyth will ask integration team if we can use the AAI tenant space in windriver environment
JIRA Issue Count (in AAI project):
| Jira Legacy | ||||||||
|---|---|---|---|---|---|---|---|---|
|
space in windriver environment
JIRA Issue Count (talking about in AAI project):
| Jira Legacy | ||||||||
|---|---|---|---|---|---|---|---|---|
|
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
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
- 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,
- CSIT on OOM needs to cover more of the services
- Volumed run-time generated certificates are possible
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
- GraphGraph is coming, depends on expanding schema-service API
- RestClient updates are potentially being contributed by community members
JIRA Issue Count (talking about AAI):
| Jira Legacy | ||||||||
|---|---|---|---|---|---|---|---|---|
|
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
- code coverage to 55% for Dublin
Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key AAI-2219
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.
Code Block <execution> <id>default-check</id> <goals> <goal>check</goal> </goals> <configuration> <dataFile>${project.build.directory}/coverage-reports/jacoco.exec</dataFile> <rules> <!-- implementation is needed only for Maven 2 --> <rule implementation="org.jacoco.maven.RuleConfiguration"> <element>BUNDLE</element> <limits> <limit implementation="org.jacoco.report.check.Limit"> <counter>LINE</counter> <value>COVEREDRATIO</value> <minimum>${jacoco.line.coverage.limit}</minimum> </limit> </limits> </rule> </rules> </configuration> </execution>
Open Action Items
New Action items
...