Vipin Rathi
To be updated.
The IEC Type 4 AR/VR Oriented Edge Stack 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
- The BP project contributors have deployed and validated the BP in at least 2 community member validation labs or 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 required to connect with Akraino LF CI. Logs on the LF CI servers pushed from each validation lab's CD testing would be used to verify this check.
- Multiple Jenkins jobs exist for deploying IEC Type 4 AR/VR to multiple clusters and for 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 Thor Chin https://nexus.akraino.org/content/sites/logs/inwinstack/R3/logs/iec-type4/
- UNH Vipin Rathi
- Release inclusion check
- SW quality/functional check
- There are some validation tests that are currently flawed (e.g. Redfish) or not applicable (e.g. OpenStack) so this statement of passing validation tests only applies to the valid validation :-)
- IEC Type 4 AR/VR is passing the blueprint validation tests
- IEC Type 4 AR/VR 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
- IEC Type 4 AR/VR has passed security scanning by a number of Open Source.
- 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 REC 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
- Upstream dependency check
- 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