zoom bridge: https://zoom.us/j/283628617
...
| Duration | Agenda Item | Requested by | Notes / Links | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| START RECORDING | |||||||||||
| 5min | Casablanca 3.0.2 | Complete? Source tags on only the changed projects - all other projects should be tagged 3.0.1 Teams can tag their own sources OR file a helpdesk ticket and LFN will help. Tag format: 3.0.2-ONAP | |||||||||
| 15min | Dublin end game plans RC0 - May 2nd RC1 - May 16th RC2 - May 30th (Euro holiday) Sign-off - June 6th | RC0 templates due - 2019-04-30 COB Mountain time
Yellow status Release Requirements - move to POC by 2019-04-22 COB Critical defects - please stay on top of the merges | |||||||||
| 10min | nexus-staging-maven-plugin deprecation | CCSDK using global-jjb - this is the correct solution to the deprecated module. Snapshot dependencies will be broken using global-jjb Would prefer to perform this change AFTER Dublin and before El Alto (recommend : June 6-June 20). Can perform parallel build processes while the global-jjb work is completed. Do we need a full integration test cycle to prove out the new build process? YES! AI: create a detailed plan for the global-jjb switch over Former user (Deleted) AI: update the wiki on the release process image tag pageBrian Freeman | |||||||||
| 10min | CII Badges clarifications |
| |||||||||
| 5min | Adding jobs for multi-arch vFW POC Review work with CCSDK | Multi-architecture support in Dublin - enabled via process changes | |||||||||
| 10min | El Alto release plans | Feel free to provide any feedback under
| |||||||||
| 5min | SECCOM ideas for consultatation with PTLs | 0. Waiting for final updates from projects for known vulnerabilities. 1. HTTP vs. HTTPS - scripts, deadlines. 2. Selection of the most impacting known vulnerabilities to be fixed. 3. Process of releasing pen test report - jiras opened under OJSI - dedicated call with LFN to be done on 7th of May. 4. Whitesoftware results benchmarking with Nexus-IQ - any volunteers? | |||||||||
...
- 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
<2019-04-08: global-jjb progress report: start on DCAE soon - focus on El Alto delivery (precursor to Dockerhub)<2019-04-22 - Using mvn staging plugins to deploy - unfort many of the changes need to be in the source code to insure the job is running> - 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
20190318: discussed discrepancy with Orange in OOM call last week - manifest is still in use to manage versions until merges come into OOM from the teams and we finish the architecture of the merged manifest in oomOOM Meeting Notes - 2019-03-13
- Review Sylvain Desbureaux's detailed docker version/size/state status page at Reduction effort between Casablanca and Dublin
<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 ><2019-04-08 New process defined - needs to be documented on the wiki Brian Freeman
<2019-04-15>: Wiki pag: Managing Container Image Tags - Tlab persistent storage IO architecture Rich Bennett
Request from Rich Bennett about Storage/Persistent Data Architecture Plan/PTLs - Single NFS server?
<2019-04-22: performance issues with old config - have bare metal cluster - - want to bring in more realistic operational aspects to the testing - network storage vs direct, would like to place modules in isolation into the environment. Evaluating the utility of testing this way. - How to consume Alpine? Adolfo Perez-Duran (Deactivated)
Meeting organized in May - https://wiki.onap.org/display/DW/TSC+2019-05-16
...