PTL 2019-08-05

zoom bridge: https://zoom.us/j/283628617

05 Aug 2019	PTL Recordings	Zoom Chat Log

Duration 60 minutes

Duration

Agenda Item

Requested by

Notes / Links

START RECORDING

Review agenda

15 mins

El-Alto Release

Former user (Deleted)

Early Drop:

Today is the final due date to release your container Nexus3 repo (docker.release)
Below goal - PTL to provide their commitments

Module	Without jScript	With jScript
ccsdk-dashboard	66.6	18.4 - what can be achievable? 25%? Dan T. to confirm
aaf-authz	40	40 -> 50%?
sdc master	48.3	48.4 → 55%?
ccsdk-sli-adaptors	49.4	49.3 → 55%?
policy-engine	57.7	49.7 → 55%?
portal	67.3	24.6 → ? Angular upgrade in Typescript code, so planning not to add JS tests in old code. more details at El-Alto Risks
ccsdk-sli-northbound	50.8	49.9 → 55%?
aai-graphadmin	53.1	53.1 -> to be reviewed based on Jimmy's inputs
aai-data-router	53.2	53.2 -> to be reviewed based on Jimmy's inputs
aai-schema-service	53.4	53.4 -> to be reviewed based on Jimmy's inputs
ccsdk-sli-core	53.4	53.4 → 55%?
sdc-jtosca dublin	53.7	53.7 → 55%?
aai-sparky-be	53.8	53.8 -> to be reviewed based on Jimmy's inputs
sndc-northbound	54.5	54.5 → 55%?

Others:

OOM Team to ensure Staging is at 5.0.0

5 mins

OOM Strategy

FREEMAN, BRIAN D

Mike Elliott

We are no more using the Manifest but the OOM strategy while releasing our container

5 mins

JIRA priority definitions

Steven wright

The definitions of priority in JIRA https://jira.onap.org/plugins/servlet/project-config/VNFRQTS/priorities do not match the definitions of priority in the Wiki https://wiki.onap.org/display/DW/Tracking+Issues+with+JIRA#TrackingIssueswithJIRA-JIRAPriorityDefinitionforBugs. It would be good to have them in sync.
Neither of those definitions mentions documentation. I prefer the more verbose definitions on the Wiki, but would like to see some mention of how to prioritize documentation. I would expect documentation tickets should never get higher than a medium priority – but it would be good to have agreement on that from PTLs/ TSC.

10 mins

Issues with testing staging artifacts

Dan Timoney

The 'Staging Repositories' group in Nexus has a bug which causes it to always return the OLDEST instance of a staged maven artifact as opposed to the most recent. Thus, it is not practical to create docker artifacts based on 'staging' versions of maven artifacts. It is more reliable to use SNAPSHOTs, begging the question of whether it is useful to automatically create daily staging versions.

An alternative to consider would be to change our daily build process to build SNAPSHOT versions instead of staging versions, and then to only build the staging version when we are ready to create a release version.

PTL 2019-08-05

Zoom Chat Log

Action Items