To be updated.
The IEC Type3 Android Cloud native applications on ARM arm servers in edge blueprint is requesting maturity review review for Akraino release 36.
This page references the requirements in BP Graduation Review Processes and Criteria specifically specifically the table cell for Incubation -> (Mature) on the second row from the bottom of the page.
- Validation lab check Zhigang Xiao (Deactivated) hanyu dingfirst lab CD lab check
1.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.
2.first lab CD
logs: https://nexus.akraino.org/content/sites/logs/
...
...
- xxx
- Multiple Jenkins jobs exist for deploying IEC type3 to multiple clusters and for RIC 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
...
...
- Release inclusion check
- SW quality/functional check
- REC is passing the blueprint validation tests vipin rathi
- REC 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
- REC has passed security scanning by a number of Open Source and proprietary tools used by AT&T’s security organization. thorking
- 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.
- Akraino Blueprint Validation Framework
- Meeting Recording for release 6:
- Meetings of IEC Type 3: Android cloud native applications on Arm servers in edge - Akraino - Akraino Confluence
- HW definition check (@ARM）
- A reference platform is documented for the primary validation lab：
- Additional hardware information for non-reference platforms is available in the installation guide https://lf-akraino.atlassian.net/wiki/display/AK/Release+6+Installation+Document+of+IEC+Type+3%3A+Android+cloud+native+applications+on+Arm+servers+in+edge
- Upstream dependency check (@Davy zhang)
- The upstream dependencies are enumerated in non-machine-readable form on the wiki R6 Release Notes of IEC Type 3: Android cloud native applications on Arm servers in edge
- Documentation check
- Documentation was created for Akraino Release 6：https://lf-akraino.atlassian.net/wiki/display/AK/Release+6+Documentation+for+IEC+Type+3%3A+Android+cloud+native+applications+on+Arm+servers+in+edge
- Community Health and Stability check ( Davy Zhang )
- Meeting are held weekly and minutes are published with a list of attendees；
- Meeting content includes welcoming new participants and providing introduction to the projects as well as discussing ongoing progress；
- Contributions from ysemi, Bytedance, ARM, Ampere, China Mobile are working on adding BP lab support and code contributions;
------------------------------------------------------------------------------------------------------------------------------------------
-------------------------previous release 3 maturity review self certification checklist------------------------------------------
The IEC Type3 Android Cloud native applications on arm servers in edge blueprint is requesting maturity review for Akraino release 3.
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
1.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.
2.first lab CD logs: https://nexus.akraino.org/content/sites/logs/ampere/job/akraino_arm_anbox_test/6/
- Release inclusion check hanyu ding
- Release 3 Planning: Release 3 Documentation for IEC Type 3: Android cloud native applications on Arm servers in edge
- SW quality/functional check
10 Bluval- Blueprint Validation
- HW definition check (@ARM）
- A reference platform is documented for the primary validation lab https://wiki.akraino.org/display/AK/Radio+Edge+Cloud+Validation+Lab (check)lab：
- Additional hardware information for non-reference platforms (REC/TA targets broad hardware support) is available in the installation guidehttps://wikilf-akraino.akrainoatlassian.orgnet/wiki/display/AK/RECR3+Installation+Guide#RECInstallationGuide-HardwareRequirements:Support for ARM hardware is being actively developed but may not be complete in time for Akraino release 2 https://wiki.akraino.org/display/AK/Porting+REC+on+aarch64+Document+of+IEC+Type+3%3A+Android+cloud+native+applications+on+Arm+servers+in+edge:
- Upstream dependency check ( hanyu ding )
- The upstream dependencies are enumerated in non-machine-readable form on the wiki R3 Release Notes of IEC Type 3: Android cloud native applications on Arm servers in edge
- Documentation check
- Documentation was created for Akraino Release 3：Release 3 Documentation for IEC Type 3: Android cloud native applications on Arm servers in edge
- Community Health and Stability check ( hanyu ding )
- Meetings Meeting are held weekly and minutes are published with a list of attendeesMeetingattendees；
- Meeting content includes welcoming new participants and providing introduction to the projects as well as discussing ongoing progressprogress；
- Contributions from TencentBytedance, ARM, Ampere, Inwinstack, Arm, are China Mobile are working on adding ARM support to the previously x86-only code https://gerrit.akraino.org/r/#/q/topic:aarch64-support+(status:open+OR+status:merged)BP lab support and code contributions;