zoom bridge: https://zoom.us/j/283628617
Duration 60 minutes
| Duration | Agenda Item | Requested by | Notes / Links |
|---|---|---|---|
| START RECORDING | |||
| 5min | Review Action Items | ||
| 5min | Review M3 checklist | ||
| offline? | Dublin M2 risks followup #11: The new lifecycle Policy API definition being introduced for Dublin are under draft and having frequent churn; this is blocking DCAE Policy Handler evaluation/enhancement required to support this API. Based on current assessment of draft versions - new proposed updates impacts existing client (PH) handling of policy data in significant manner. #12 & #14: Lab Space & S3P- Geo-Redundancy - Lab Environment to be available by M4 | ||
| Gooch OOO til Mar 12. Defer | Windriver lab resource capacity and allocation | Dev and Integration teams are running into resource constraints in Windriver lab, and we expect the situation will get worse when approaching integration testing phase. Stephen will review the lab resource capacity and where the resource is allocated currently, and we will collect lab resource requirements from Dev teams | |
| 30min | Self-release objective - Review for TSC approval 2019-03-07
| Review the plans with PTLs Desired outcome: Seek agreement from PTLs on process changes and timeframes Defer DockerHub until next week | |
| 5min | Follow-up from Footprint Optimization call | ||
| 5min | Where to find the containers to be certified by the Integration Team? | ||
| 10min | Proposal: Modifying the Dublin M3 checklist: Data models and swagger requirement (from TSC meeting) | Our proposal is for M3 to please include a single modeling item: "Has the Project team provided links to Data Models (e.g., JSON, YANG, Swagger, etc.) for all Shared Information (e.g., APIs, API Payload, Shared Design Model)?" | |
| 5min | oParent contents and delivery plan | Please review the plan to provide the oParent contents BEFORE M3 | |
| 5min | Daylight savings time adjustment |
Daylight saving time 2019
No Clock change in China, India Desired outcome: Gain agreement of how to schedule the PTL weekly meeting. | |
Action Items:
- Revise LF infrastructure roadmap to include the timeline and TSC-58 content in advance of TSC meeting Kenny Paul Former user (Deleted)
- Krzysztof Opasiakto provide vulnerability procedure overview next week 2019-02-25
/* Vulnerability Management Procedure is being updated so I'd like to delay this till the procedure is approved by TSC to avoid confusion. Hopefully the overview will be delivered next week. */ - Yang Xu add integration sanity passing in milestone checklist
(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 - 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
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
<2019-03-01 - Need a date for the delivery of the procedure > - 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 on this topic today - review the process - develop training material. OOM subcharts complete - A&AI this week> - What is the plan for the June ONAP Developers Forum - dates/location/etc Kenny Paul Former user (Deleted)