Versions Compared

Old Version 7

changes.mady.by.user Yanjun Chen

Saved on

compared with

New Version Current

changes.mady.by.user Davy Zhang

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


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.


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/

...

ysemi/job/v1/

...

  • xxx

ak_results/

https://wiki.akraino.org/display/AK/IEC+Type+3%3A+Android+cloud+native+applications+on+Arm+servers+in+edge+for+Integrated+Edge+Cloud+%28IEC%29+Blueprint+Family

  • 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

...

...

  • 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 :-)
    • 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. Thor Chin
    • 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

Image Added


------------------------------------------------------------------------------------------------------------------------------------------

-------------------------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/