Page Comparison

19 Feb 2019	PTL Recordings	Zoom Chat Log

...

Duration

Agenda Item

Requested by

Notes / Links

START RECORDING

15min

Dublin M2 Preparation

M2 Date: 2019-02-21

Missing wksheets:

AAI, AAF, CCSDK, DMaaP, Doc, ExtAPI, Holmes, Integration, Logging, MSB, MultiCloud, MUSIC, CLI, OOM, SDNC, SDC, SO, VID, VNFSDK, VNFRQTS, VVP

Former user (Deleted)

Complete the Dublin status page
Take the latest template including Security Checklist
Don't forget to articulate your known risks

Since Feb 15th 1pm EST, we have also reworded the following item to reflect the Dublin non functional requirement about Additional functional tests delivered per project on OOM - See Yang/Morgan's presentation below

Modeling Checklist: M2 will not be part of this release since TSC/Modeling team are still under discussion. Target is to get Modeling M3 Checklist as part of Dublin

15min

Version management enhancement - Long term vision

Dublin Expectations:

Additional functional tests delivered per project on OOM
Add integration basic sanity test (pod deployment, healthcheck, model distribution, vFWCL) to milestone checklist
POC Gating Project (Morgan's presentation)

Yang Xu / Morgan Richomme

cl664y@att.com

View file

name	oom_version_tests.pdf
height	150

View file

name	Dev Testing_Enhancement for Dublin_V2.pptx
height	250

10min

Review previous action items from 1/21 till today

Former user (Deleted)

Helm Chart Transfer: 4 projects have been identified for trial: A&AI, Log, Policy, APPC, CLAMP and ONAP CLI. Mike Elliott will work with PTL to gather/transfer knowledge and create training materials. Training to be done the week of Jan 14 and PTL to provide their commitment or not by M1 on Jan 24.

<1-7/2019>: Work in progress. Schedule might shift to another week. Michael will follow-up with Mike. Training will be open to everybody. The objective is that each team will take over the management of their Helm Charts.
<1-28/2019>: Meeting is organized on 1/29 with LF. Training will be organized early in February. Additional information on the next PTL call (2/4)

<2019-2-19: Meeting today - review the process - develop training material. OOM subcharts complete - A&AI this week>

Oom values.yaml or integration repo manifest ( TSC-86 - Lock down docker image tag name source of truth - oom values.yaml or integration repo manifest - A: both but manifest is the source Submitted ) Michael O'Brien
if not covered - see TSC 2019-01-10
Quick discussion on nailing down whether we need a yaml override of the deployable
docker image tags in the oom repo (understanding is no) - with the integration docker manifest
(manifest is currently a copy of the oom values.yaml tags - not the reverse)
If not - then we need a documented procedure wiki/RTD on running a derived values.yaml override for the entire system before deployment
AAF is only an example here
https://git.onap.org/oom/tree/kubernetes/aaf/charts/aaf-service/values.yaml?h=casablanca#n28
```
image: onap/aaf/aaf_service:2.1.8
```
drives
https://git.onap.org/integration/tree/version-manifest/src/main/resources/docker-manifest.csv?h=casablanca#n11
```
onap/aaf/aaf_service,2.1.8
```
<1-7/2019> Integration team to document the procedure.<01/13/2019> Answer from Integration team: docker manifest under integration repo is the source of truth, and is used by Integration team to override OOM values.yaml when deploying ONAP in Openlab. See the instructions at the bottom of page https://onap.readthedocs.io/en/casablanca/submodules/integration.git/docs/onap-oom-heat.html#onap-oom-heat-template
<1-21/2019> Procedure should include Timers, dependencies, etc.
just need to define all the --set and -f overrides like the following

sudo helm deploy onap local/onap --namespace $ENVIRON -f $DISABLE_CHARTS_YAML -f $DEV0_YAML $APPENDABLE_ENABLED_FLAGS --verbose 
<1-28-2019>: Document how to handle the latest 3rd party image from github.
<2019-02-19>: One over-ride that will be shared, parent over-ride for docker versions, Michael O'Brien to modify TSC-86 to reflect process. Still looking at tool to institute changes for all projects (single commit). Mike Elliott FREEMAN, BRIAN D Gary Wu Sylvain Desbureaux to follow up offline.
It should also consider the problem identified with the Casablanca Maintenance Release: https://lists.onap.org/g/onap-tsc/message/4641

(PTLs): Review ONAP codebase license scan, Feb. 2019 sent by Steve Winslow on 2/18. (reminder)

2/11: Migrate Docker image releases from Nexus3 into Docker Hub (Architecture Independence) by Dublin M4.
<2-15-2019> Preparing a preso for review of all known infrastructure change requests for review at PTL meeting 2-25-2019
(Mike Elliott) will work with PTL to gather/transfer knowledge and create training materials. Targeted projects: A&AI, Log, Policy, APPC, CLAMP and ONAP CLI.
(Jimmy Forsyth): Identify projects impacted by AAI-1989
<2019-02-19>: Clients that cannot migrate in the Dublin timeframe can continue to use the old method - but all are urged to adopt new method. Closed loop merged this week.
Projects potentially impacted: APPC, CCSDK, VID?

5min

Samsung ONAP penetration test ongoing results

Krzysztof Opasiak

Requested outcome: Scheduling of a sponsored ONAP code base third party audit

10min

Using non-root user in containers

Jonathan Gathman

Best practice review in prep for M2

5 min

Breaking change on pnf object in AAI

James Forsyth

The Pnf object will be changed to use the pnf-id as the key instead of the pnf-name. pnf-name will still be indexed and can be searched for with ?pnf-name={pnf-name}

Since it's a breaking change that impacts the graph, all versions of the API back to v11 have to changed. Clients who use a previous version will have to update in Dublin

See: pnf-id change

Jira Legacy

server	System Jira
serverId	4733707d-2057-3a0f-ae5e-4fd8aff50176
key	AAI-2148

2min

ONS NA

Former user (Deleted)

Register here

Propose topics for an unconference here!

...

Versions Compared

Old Version 42

New Version 43

Key