...
| Duration | Agenda Item | Requested by | Notes / Links | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| START RECORDING | |||||||||||||
Emergency Maintenance Release - Tag: 3.0.2
|
| ||||||||||||
| M3 follow up topics | Former user (Deleted) | Use case YELLOW - blocking defects? Alla.Goldner Component & Global Optimizations Eric Debeau S3P djhunt Additional functional tests OOM Morgan Richomme xNF communication security enhancements Linda Horn Amy Zwarico Locale/Internationalization Tao Shen | |||||||||||
M4 Preparation
| |||||||||||||
| 10min | Documentation process overview Hack a thon days | Process overview, PTL 2019-01-21 | |||||||||||
| 2min | WindRiver Clean-Up checkpoint | Yang Xu | Jim sent the delete list to WR on 2019-03-19 - Cleanup complete 2019-03-20 Reduced: 40 vCPUs, .9TB RAM, 7TB Disk | ||||||||||
| 5min | Consistent Java code style using maven plugins | Regarding instructions under Setting Up Your Development Environment Instead of starting with Google style and Setting Up Your Development Environment Suggest using Setting Up Your Development Environment as the ONAP style formatter file is committed to the repo In
Plugins can do batch re-formatting of Java code in the repository and run the audit, e.g.:
Example of batch re-formatting: https://gerrit.onap.org/r/#/c/82887/ Suggest that the formatter file and plugin config be adopted into oparent for all to share. Otherwise individual projects can copy the configuration and adopt it for their own local usage as per Contributing To AAI Best Practise and Setting Up Your Development Environment | |||||||||||
| 5min | Security related defects needing immediate attention | Amy Zwarico | JDWP, | ||||||||||
| 5 min | Production repos vs. preprod repos -different helm charts | Paweł Pawlak | The idea to be discussed is to use different help charts for differentiating repos used for tests from the ones used for production environment where some tests tools are not allowed as could bring some vulnerabilities. | ||||||||||
| 5 min | PTLs readiness for M4 known vulnerabilities analysis by SECCOM | Paweł Pawlak | We would like to propose opening a Jira ticket for each PTLs - for the first time we could open it,to save time on projects side. The goal is to allow demonstrate each project readiness for the analysis (all critical and severe vulnerabilities are analyzed, appropriate Jira tickets are created), It should save soem time for both PTls and SECCOM team members performing the analysis. For R5 release, each PTL would have to open a ticket for that during M0 milestone. | ||||||||||
Action Items
- 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
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 >
...