Page Comparison

...

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

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

• Release inclusion check  Davy Zhang 
• Release 6 Planning:

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

• SW quality/functional check   
• Akraino Blueprint Validation Framework

Image Added

• 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://wiki.akraino.org/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://wiki.akraino.org/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 3maturity 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   

• Akraino Blueprint Validation Framework

  

  
  

• Meeting Recording: https://zoom.us/rec/play/tZN7f-z-pzI3HtCStgSDVP5xW47oJvisgSAa__QKmEeyAXIBZAH1NLQaZOKKJ7tJOQfWgQ6WHaoN3xbM?autoplay=true&continueMode=true&startTime=1585663546000

  
  

  10

  Bluval- Blueprint Validation

  Tapio Tallgren

  Akraino Bluval.pdf Running bluva

  
  

• 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://wiki.akraino.org/display/AK/R3+Installation+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 )
• 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 Bytedance, ARM, Ampere, China Mobile are working on adding BP lab support and code contributions;

...