Instructions:
Use this page to record your review of the Dublin release - the PTLs will review and summarize prior to review at the TSC meeting after
- RC0 attempt to integrate and test was not successful - no CI/CD and a large set of changes integrated at once negatively impacted system stability
- Early start of integration testing helps issue resolution earlier than the tail end of the release
- Project team engaging in the integration process accelerated the process of integration - zoom shared debug sessions (much faster than jira)
- Addition of OJSI Jira has been useful to create more focus on security issues - vulnerabilities are easier to track
- Nexus vulnerabilities analysis still is very difficult - need some innovation
- AAF underestimated the difficulty of changing the service locator
- Infrastructure changes need to start very early in the release
- Plan for backward compatibility up front
- SECCOM TTL for test certificates doesn't impact the security - probably longer than a year
- OOM verify job was very helpful - finding defects before merged into the charts
- Need to do installation testing in other places than just Windriver to catch environment assumptions
- Diverse lab test envs (Orange) was helpful
- Many versions of OpenStack
- Need to start with keystone V3 install in El Alto - installation jobs will be changed (authentication)
- Lack of available lab resources
- Need devops CI/CD to get more end2end visibility from developer perspective
- 72 hr (longevity) stability runs should be reviewed by the PTLs - monthly review in the PTL meeting
- Delay in Dublin - issues not found until the very end
- Testing started earlier in the release
- Functional deployments exposed more defects and happen late in the release
- Intersystem testing should start sooner
- Instantiate vFW as a step in the CI/CD process - fully automated testing and very stable
- Requirements came too late in the process
- Need to begin the testing of Functional requirements earlier
- Teams need to be transparent into the actual status of the milestones - example: projects marked as code complete were not complete
- Retrospectives best done in person
- Off-line installation finding new issues - could be done earlier to find issues