...
- 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( ##To be removed)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.( ##To be removed)
- HW definition check:
- Precise HW requirements and descriptions are defined and included in the BP's documentation (as used in both lab validations)
- To be updated properly.
- Reference platform for HW req from release doc.
- Upstream dependencies check:
- The upstream dependencies are enumerated in non-machine-readable form on the wiki R3 Architecture Document#LicensingTo be updated. ##TARS dependencies
- 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
...