...
| Duration | Agenda Item | Requested by | Notes / Links | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| START RECORDING | |||||||||||||||||||||
Emergency Maintenance Release - Tag: 3.0.2
|
All participants in the 3.0.2 release must link a Jira to the above ticket. Known participants: A&AI, Dmaap, CLAMP, VID, Policy Possible security patches from: Non certif: SDNC (python lib), APPC, CCSDK Integration needs 5 working days to complete the sanity and verify use cases. | ||||||||||||||||||||
| M3 follow up topics | Former user (Deleted) | Use case YELLOW - blocking defects? Alla.Goldner <the 4 yellow use cases are due to integration blockers - all known issues being worked> Component & Global Optimizations Eric Debeau <on track> S3P djhunt <No update giving; contact via email> Additional functional tests OOM Morgan Richomme <on track> xNF communication security enhancements Linda Horn Amy Zwarico <DCAE complete, other projects get update from Linda. Amy to get update> Locale/Internationalization Tao Shen <Implementation complete; in test now> | |||||||||||||||||||
M4 Preparation
| TSC moved M4 to 2019-04-11 Please update M4 checklist by April 10th, 2019 noon - thank you | ||||||||||||||||||||
| 10min | Documentation process overview Hack a thon days | Process overview, PTL 2019-01-21 <Sofia will consider adjusting the date based on Dublin M4 milestone change> | |||||||||||||||||||
| 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 | Following on from comments on
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 - projects need to create their own Jira tickets for these vulnerabilities | ||||||||||||||||||
| 5 min | Production repos vs. preprod repos -different helm charts | Paweł Pawlak | The idea to be discussed is to use different helm 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. | ||||||||||||||||||
...