The Integrated Edge Cloud Type 1 and Type 2 blueprints are 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
- Multiple Jenkins jobs exist for deploying IEC Type 1 and Type 2 to multiple clusters and for IEC 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
- Type1
- Release inclusion check
- IEC Type 1 and Type 2 were included in Akraino Release 1
- IEC Type1&2 Release 1 Milestone Certification
- SW quality/functional check
- IEC does the blueprint validation tests daily. The validation daily job could be found at: ( ... to be added)
- IEC has passed security scanning by a number of Open Source and proprietary tools used by Coala when committing the code everytime ( ... the job link to check the code to be added)
- Sonarcloud code check integrated in ci-management: ( ... to be added)
- 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 ...
- HW definition check
- A reference platform is documented in detail for the IEC Validation Lab with 2 labs (Enea lab and Arm lab).
- Additional hardware information for non-reference platforms is available in the IEC Hardware Requirement and blueprint species of Type1 and Type2.
- Upstream dependency check
- The upstream dependencies are enumerated in non-machine-readable form on the wiki ( ... to be added) and in machine readable form in the Gerrit repos as described in IEC Code Repository Overview
- Documentation check
- Documentation was created for Akraino Release 1 documentation and Release 2 documentation 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 ( to be added ...)
- Meeting content includes welcoming new participants and providing introduction to the projects as well as discussing ongoing progress
- Contributions from ENEA are working on adding CentOS support to the previously ubuntu-only code , providing validation lab for Arkaino Jenkins IEC jobs