To be updated.
The Connected Vehicle Blueprintis 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
- The CVB has passed the Akraino the Akraino Validation Framework Validation feature project (Akraino Blueprint Validation Framework) (after TSC approval).
- The CVB has passed the security scanning include Lynis and Vuls : https://nexus.akraino.org/content/sites/logs/inwinstack/R3/logs/cvb/
- HW definition check:
- Precise HW requirements and descriptions are defined and included in the BP's documentation (as used in both lab validations)
- CVB Release 3 Installation Doc#HardwareRequirements
- Upstream dependencies check:
- Tars
- MySQL
- Nodejs
...