Recording:
...
Attachments (including meeting recording):
Attachments |
---|
Attendees:
Dmitry Puzikov Former user (DeactivatedDeleted)
Former user (Deleted)William Reehil
CLEAN UP OLD RECORDINGS IN ATTACHMENTS
START RECORDING
1 | v17 schema for Frankfurt | Since the CCVPN SOTN proposal is in progress already, could we have the v17 schema introduced into master branch to receive the updates for Frankfurt release? See also AAI-CCVPN-Extension-SOTN Proposals for Frankfurt Release and
| |||||||||||||||||||||||||||||||||
2 | El Alto Issues |
| |||||||||||||||||||||||||||||||||
23 | Docker images not pushing | James Forsyth | docker pull nexus3.onap.org:10003/onap/babel:1.5.0 - 1.5.1 pushed, will be release version docker pull nexus3.onap.org:10003/onap/aai-gizmo:1.5.0 - 1.5.2 pushed, will be release version docker pull nexus3.onap.org:10003/onap/aai-data-router:1.5.0 - 1.5.1, will be release version docker pull nexus3.onap.org:10003/onap/aai-search-data-service:1.5.0 - 1.5-STAGING-latest available, no tagged images
docker pull nexus3.onap.org:10003/onap/elasticsearch-sg:1.5.0 - same as search data service docker pull nexus3.onap.org:10003/onap/aai-model-loader:1.5.0 - 1.5.1 will be release version docker pull nexus3.onap.org:10003/onap/aai-spike:1.5.0 - 1.5.1 will be release version docker pull nexus3.onap.org:10003/onap/aai-sparky-be:1.5.0 - 1.5-STAGING-latest, no tagged images Want to migrate to an actively support maven docker plugin since Spotify docker plugin. Consider fabric.io - an example is aai/resources | ||||||||||||||||||||||||||||||||
34 | 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.
| 4 | CCVPN use case in Frankfurt | shashikanth.vh
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
Consider adding glow root profiling for AAI Microservices
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
Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key AAI-2548
Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key AAI-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
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:
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
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 | ||||||||
---|---|---|---|---|---|---|---|---|
|
JIRA Issue Count (talking about AAI):
Jira Legacy | ||||||||
---|---|---|---|---|---|---|---|---|
|
- 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
...