Page Comparison

To be updated.

The Connected Vehicle Blueprintis 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:

      The Connected Vehicle Blueprint(CVB) 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  Tencent   https://nexus.akraino.org/content/sites/logs/inwinstacktencent/R3MR/logs/cvb/
• UNH UNH  https://nexus.akraino.org/content/sites/logs/parserlabs/jobr4/R3jobs/cvb/

  
  

• Release inclusion check:

  • Release 2 Planning
  • Release 3 PlanningCVB was
  • Release 4 Planning
  • CVB is included in Akraino Release 2 and 34 
  • The CVB related API info is accepted on 2020-12-21

• 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)The CVB has passed 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/parserlabs/r4/jobs/cvb/

• 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.
  • CVB Release 4 Installation Doc#HardwareRequirements

• Upstream dependencies check:
  • Tars
  • MySQL
  Nodejs
  • Server Side:  CentOS 7.8 and CentOS 7.9
  • Tars Framework                            Version:  v2.4.13
  • IEC                                                Version:  v3.0
  • Jenkins                                         Version:  2.263.3

• Documentation check:
  • Documentation is created for Akraino Release 2, 3 and 3 4, 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://wikilf-akraino.akrainoatlassian.orgnet/wiki/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

...