To be updated.
The Connected Vehicle Blueprint is requesting maturity review for Akraino release 2.
- Validation lab check:
The Connected Vehicle Oriented Edge Stack project contributors have deployed and validated the BP with a community member validation lab and LF CD lab with the exact HW and SW configuration for which the maturity review is being requested. All validation labs are connected with Akraino LF CI Logs on the LF CI servers. The logs are pushed from each validation lab's CD testing, and the logs verifies the validation lab check.
- Multiple Jenkins jobs exist for deploying CVB to multiple clusters and for CVB installation and various testing. The jobs listed below are the primary CD jobs. Additional job logs can be viewed on Nexus, but these listed here are the relevant ones for Akraino maturity review
- Inwinstack https://nexus.akraino.org/content/sites/logs/inwinstack/R3/logs/cvb/
- UNH https://nexus.akraino.org/content/sites/logs/parserlabs/job/R3/cvb/
- Release inclusion check:
- Release 2 Planning
- Release 3 Planning
- CVB was included in Akraino Release 2 and 3
- SW quality/functional check:
- The validation 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 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
- 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:
- Precise HW requirements and descriptions are defined and included in the BP's documentation (as used in both lab validations)
- Upstream dependencies check:
- The upstream dependencies are enumerated in non-machine-readable form on the wiki R3 Architecture Document#Licensing
- Documentation check:
- Documentation is 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:
- Meetings are held weekly and minutes are published with a list of attendees https://wiki.akraino.org/display/AK/Connected+Vehicle+Blueprint+Project+Meetings
- Meeting content includes welcoming new participants and providing introduction to the projects as well as discussing ongoing progress
- Contributions from Tencent, Ampere, Inwinstack, Arm, L&T Technology Services, supporting multi architectures including Arm and x86 https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/concepts.html