Skip to end of metadata
Go to start of metadata
You are viewing an old version of this content. View the current version.
Compare with Current
View Version History
« Previous
Version 18
Next »
Agenda
START RECORDING
| Duration | Agenda Item | Requested by | Notes / Links |
|---|
| 1 hour | Cross-project discussions | | New Policy API - SO/SDNC - OK? |
LF IT Support | Jessica Gonzalez | - Review unused Jenkins Jobs <Jess to add the list>
CIMAN-339
-
Getting issue details...
STATUS
- Two area affected: storage and builders
- Task is to reduce costs
- Teams running a combination of old and new jobs. Need to make sure that all old jobs are deprecated.
- All changes to be documented in JIRA ^^
|
Testing Improvement | cl664y@att.com | - ONAP "Use Case/Requirement" Integration Lead
- these will be the people for each usecase/requirement that will be reporting to the integration team - usecase/requirement-by-usecase/requirement
- Integration leads are listed on the Frankfurt Release Requirements wiki: Frankfurt Release Requirements
- Integration leads will be reporting their test results on the Integration Weather Board for Frankfurt Release that will be created by the Integration Team
ACTION (Integration Team): Create Integration Weather Board for Frankfurt Release |
CSIT Review | | - Currently few failing jobs - please direct attention to getting these tests functioning correctly.
- Will continue to review here (ptl mtg)
- Brian Freeman notes that the usecase master verify job has not run successfully for a month
- Useless CSIT test elimination
|
ToolChain Improvement | cl664y@att.com | - Impact Assessment on the tool-chain i.e. JJB jobs using some Python 2 scripts
- David McBride notes that there is a milestone task to identify python in use
- Request to add pylint as part of our toolchain to improve code quality. Pylint is a source-code, bug and quality checker for the Python programming language
- No feedback from the PTL on the call so let's move to the implementation.
- ACTION (LF IT): Share the roadmap of the pylint implementation
|
Other Improvement suggestion Release Improvement | | Any feedback regarding #1 Frankfurt Documentation #2 Release Planning Template #3 Mx Milestone - Frankfurt Deliverables by Milestone #4 Code Impact View per Component - Frankfurt Code Impact View per Component
El-Alto Retrospective - please submit your feedback by Nov 15th - these will be reviewed during the PTL Call on 11/18.
Would you like to get the PTL agenda every Friday through "onap-release" mailing list |
Subcommittee Updates for PTLs | Paweł Pawlak | S3P Security maturity update proposal: Add at least 2 sections: vulnerabilities remediation (OJSIs management + known vulnerabilities) and increased tests code coverage (example could be increase by 5% for each project). Rationale: 3 security maturity KPIs: - fixed OJSIs tickets
- CII Badging
- known vulnerabilities management
Known vulnerabilities management - PLEASE complete your analysis, respond to comments for El Alto release. |
Sharing Best Practices | cl664y@att.com | TSC El-Alto Demo Contest - DEMOS - R5 El-Alto Demos- Submission open till Nov. 8th, 2019
- EAUG/TSC review/vote: from Nov. 11th to Dec 4th, 2019
|
| IF TIME ALLOWS .... |
| 20 min | Release status | | El-Alto: - Follow-up on the remaining El Alto Sign-off conditions: Release note updates and Vulnerability tables
- OOM Tagging
Frankfurt: - Collect questions/concerns from the teams
- Any clarification required regarding Use Cases/Requirements
- Security requirements demystification - Paweł Pawlak , Amy Zwarico
- S3P Frankfurt requirements - same as Dublin
- Anything else?
- Any Resource gap identified
- Call for Technical Support Expertise for the Documentation project
- Call for Testers to validate Security requirements related to Portal SDK
- Anything else?
|
| 5 mins | Incoming Events | | ONAP/CNTT F2F Event in January 13-16th, 2020 - Prague - Registration is open: reg link |
| 5 mins | Remaining Action Items | | PTL Weekly ONAP12, Mon UTC 13:00 |
Zoom Chat Log
Action Items