Vipin Rathi
To be updated.
The Connected Vehicle Bluprint is requesting maturity review for Akraino release 2.
This page references the requirements in BP Graduation Review Processes and Criteria specifically the table cell for Incubation -> (Mature) on the second row from the bottom of the page.
- Validation lab check
- Release inclusion check
- was included in Akraino Release 2 and 3
- SW quality/functional check yarg yang
- The va;idation tests are done in the bare-metal server, and they also can be done in the VMs. Container mode will be supported in the future.
- CVB is passing the blueprint validation tests Vipin Rathi
- CVB uses the TA “Cloud Test Automation Framework” which mostly passes but is under continuous development so new tests continue to be added on an ongoing basis, so it is not expected to be 100% passing at every point in time
- CVB has passed security scanning by a number of Open Source and proprietary tools used by AT&T’s security organization. Thor Chin
- Sonarqube is only scanning ta-caas-install, but not the rest of the repositories. Need to investigate why.
- The Akraino security requirements don’t provide documentation on how to configure Lynis (i.e. is “lynis audit system --quick” sufficient or is specific configuration and tuning expected) but we have CVB clusters available to run the tool if instructions are provided. In the absence of step by step instructions, our security organization has scanned with the tools that they routinely use and have expertise in. We did run lynis and we're satisfied with the results.
- HW definition check (Fei Fei, yarg yang)
- Upstream dependency check (Vipin Rathi )
- Documentation check
- Documentation was created for Akraino Release 2 and 3 and some minor updates have been made but we are not aware of any significant documentation issues
- Community Health and Stability check (Vipin Rathi )