Versions Compared

Key

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

Vipin Rathi

To be updated.

The Radio Edge Cloud blueprint IEC Type 4 AR/VR Oriented Edge Stackis requesting maturity review for Akraino release 24.

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 IEC Type 4 AR/VR 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. 

  • Release inclusion check:

IEC Type 4 AR/VR Oriented Edge Stack successfully participated in Akraino release R2, R3 and R4's  incubation stage.


...

...


  • HW definition check:
    • Wearable Glass (Optional)
    • Teacher Client-Side — Personal Computer with Camera
    • Student Client-Side — Personal Computer with Camera  
    • Server Side — 8 Core 16G Virtual Machine on ARM or x86 Platform 


  • Upstream dependencies check:
    • Teacher Side:  Windows 10 with a Web Browser that supports WebSockets.
    • Student Side:  Windows 10 with a Web Browser that supports WebSockets.
    • Server Side:  CentOS 7.8 and CentOS 7.9
    • Virtual Classroom Application      Version:  Master Branch of https://github.com/qiuxin/openvidu-vr
    • 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 4,

...

...

  • REC is passing the blueprint validation tests
    • 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 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.
  • 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.

...

...

...


  • Community Health and Stability check: