PTL 2019-08-05

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

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%?
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:

5 mins

OOM Strategy

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

5 mins

JIRA priority definitions

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.

Zoom Chat Log