Release 6 target date is April 30th 2022.

Classes of release 6 Blueprints and the requirements to be included in Release 6

The requirements for the blueprints to be included in release 6 are as follows:

Depending upon the situation, the PTLs are suggested to meet the following criteria -

Class 1: The Blueprints moving from Release 5 to Release 6

If the blueprint is already part of release 5 and you want this to be included in release 6, please follow the following steps:

Did you make any improvements in release 6 - e.g. you fixed bugs or added additional features?
- If Yes:
  - Does it impact the APIs or Documentation?
    - If yes,
      - Please update ~~the APIs and~~ the documentation and send the email to respective sub-committee chairs.
      - For APIs, please see API Subcommittee Guidelines below
    - Run the security scans and upload the link in the table below next to your blueprint
    - Upload the latest CI/CD logs
    - Send an email to tsc@lists.akraino.org to notify the TSC
    - Put yourself on the TSC agenda and request for the approval
- If No:
  - No additional formalities are required
  - Send an email to tsc@lists.akraino.org to notify the TSC
  - Put yourself on the TSC agenda and request for the approval

Class 2: The Blueprints moving from Release 4 to Release 6

If the blueprint is already part of release 4 and not release 5 and you want this to be included in release 6, please follow the following steps:

Note that in release 5, a new requirement was introduced to expose all the API consumed and offered by your blueprint.

Please update the documentation to include new API section.
Follow the guidelines to submit API information as per the requirements specified in the API sub-committee
send the email to respective documentation and API sub-committee lists.
- If you require assistance with documentation ~~or APIs~~, please reach out the respective subcommittee to be included on their agenda and discuss with them otherwise you are done
- For APIs, please see API Subcommittee Guidelines below
Run the security scans and upload the link in the table below next to your blueprint
Upload the latest CI/CD logs
Send an email to tsc@lists.akraino.org to notify the TSC
Put yourself on the TSC agenda and request for the approval

Class 3: The Blueprints moving from Release 3 or earlier to Release 6

If the blueprint is already part of release 1 or 2 and not release 3 or 4 or 5 and you want this to be included in release 5, please follow the following steps described under Class 4 below.

Class 4: New Blueprints being introduced for the first time in Release 6

Please follow the requirements specified in release 6 with the following exceptions:

The sub-committee presentations are optional starting from release 5 and for your benefit only. If you require assistance on any of the areas such as ~~APIs,~~ documentation, Security scans or CI/CD logs, please schedule a meeting with appropriate subcommittee.
For APIs, please see API Subcommittee Guidelines below
Once you meet the requirements of respective subcommittee, please send them an email to notify them. Except for APIs, as noted in 2., if they require any clarification, they will either invite you to meet with them or they will approve your blueprint via email.
Send an email to tsc@lists.akraino.org to notify the TSC
Put yourself on the TSC agenda and request for the approval

API Subcommittee Guidelines

Please follow step-by-step instructions on the API Subcommittee API reporting wiki page. If after submitting your API info form (or an updated form, if you are in Class 1 and the form has changed since Release 4) and notifying the subcommittee by e-mail they have questions, then schedule a time when either subcommittee members may attend your weekly BP meeting or you can attend the API subcommittee weekly meeting in order to discuss and resolve the questions. When meeting, please be prepared with architecture and data flow diagrams so the API subcommittee can understand and confirm 1) APIs consumed and offered by your BP, 2) upstream project APIs, and 3) customer-facing demo APIs. This information will be used to update the Akraino website API Map, which makes your BP visible and searchable to customers and entities outside of Akraino, so completeness and accuracy is important.

Release 6 Requirements

High Level Overall Requirements
CI, Blueprint Validation Lab Sub-Committee Requirements
1. Present Pod Topology document.
2. Peering w/LF Jenkins - (Note: peering is an optional requirement)
3. Push logs through Nexus. (Note: This is mandatory for Incubation self-certified and Maturity)
4. Usage of topics for release
  1. Releases >= 1.0 (e.g. 1.xyz, 2.xyz etc) are reserved for BP that have been approved as Core by the TSC (considered ‘GA’ quality).
  2. Releases <1.0 (e.g. 0.xyz etc) are reserved for projects that have not reached the Akraino Core level (i.e. anything that is in Incubation (‘alpha’ quality) and Mature (‘beta’ quality).
5. Enforcement of Static Code Analysis through SonarCloud (SaaS), WIP LF Release Engineering & Security Subcommittee. (Note: This is an optional requirement for Incubation self certified and mandatory for Maturity)
Security Sub-Committee Requirements, please fill in Release 4 Blueprint Scanning Status. Instructions can be found at: Steps To Implement Security Scan Requirements
Blueprint Validation Framework Feature Project Requirements See TSC meeting.
Projects going for Maturity Review please refer to Maturity Criteria defined by Process subcommittee BP Graduation Review Processes and Criteria (Note this is not required for self certification, only required for maturity review)
Documentation Sub-Committee Requirements
User Documents:
The following documentation with the following sections called out should be on the wiki with links to rest of the sections as applicable. We prefer that the entire doc is on the wiki but we do not require it.
Architecture - Blue print Overview and overall architecture
Release Notes – Summary and What is released
Installation Doc – Introduction and deployment architecture
Test Document – Introduction and Overall Test Architecture
Developer Documents:
We are also recommending that Blueprints include via ReadtheDocs, with each Blue Print given their own repo, but we do not require it
API Sub-Committee Requirements (Note: See this link for requirements: Blueprint Projects API Reporting Requirements)
Community Sub-Committee Requirements (Note: no mandatory requirements for Incubation self-certified or Maturity)
Process Sub-Committee Requirements (Note: See the Process Sub Committee page defining the TSC approved Maturity review process and requirements for those requesting inclusion in R3 at Mature level BP Graduation Review Processes and Criteria)
Upstream Sub-Committee Requirements (Note: no mandatory requirements for Incubation self-certified or Maturity). Here is the R6 release Upstream BP review status Release 6 Upstream Review Status, Release Upstream Compliance. Also please refer to the page for the R6 requirement as well.

Blue Prints Participating in Release 6

Internal Target date to meet Rel 6 Criteria is April 30th

(To be updated)

No.	Project Name	TSC Subgroup Release Status	Is this your first release	Blue Print Stage Self-Certify Incubation Mature Core	CD Logs URL to be used for review (Column filled in by PTLs) How to: Push Logs to Nexus Jenkins Master for Private Lab Jenkins Peering Guide Example: KubeEdge BP Test Documents	Link to executive one pager (editable doc format) (Column filled in by PTLs)	API Info Reporting Review (Column filled in by API Subcommittee) (note for PTLs – go here for steps to fill in project API info form)	BluVal BlueVal Logs or Manual Logs Bluval User Guide	Security Certification (TO be filled by Security Subcommittee) Pass/Fail Criteria: Steps To Implement Security Scan Requirements Exception requests should be filed at: Release 6: Akraino CVE and KHV Vulnerability Exception Request	Upstream Review (Column filled by Upstream Subcommittee and PTLs) (note PTL can go to Release 6 Upstream Review Status to find details)	Date ready for TSC review (Column filled in by PTLs)	TSC Review Date (Column filled in by TSC)
1	Connected Vehicle Blueprint thorking Tao Wang abhimanyu		No	Mature	https://nexus.akraino.org/content/sites/logs/parserlabs/r4/cvb/				https://nexus.akraino.org/content/sites/logs/parserlabs/r4/	Approved
2	IEC Type 4: AR/VR oriented Edge Stack for Integrated Edge Cloud (IEC) Blueprint Family Bart Dong thorking abhimanyu		No	Mature	https://nexus.akraino.org/content/sites/logs/parserlabs/r4/cvb/	IEC-Type4 Release 6 datasheet.docx	No API changes expected from R5, per Bart Dong in TSC meeting 07 Apr 2022. Waiting for e-mail from Bart to confirm this Bart confirmed by e-mail 05 Jun 2022		https://nexus.akraino.org/content/sites/logs/parserlabs/r4/	Approved
3
4	ICN - Integrated Cloud-Native Family Kuralamudhan Ramakrishnan (Deactivated)		No	Incubation	ICN Master Bare Metal Deployment Verifier ICN Master Virtual Deployment Verifier	ICN R6 Datasheet	No API changes from R5, per e-mail from Kural Ramakrishnan 28 Apr 2022	BluVal Results	02 May 2022 lynis results: Accepted vuls results: Accepted kube-hunter results: Accepted	Approved	29 Apr 2022
5	ICN - Multi-Tenant Secure Cloud Native Platform Salvador Fuentes (Deactivated) Status changed to end-of-life (EOL), not participating in R6		No	EOL			No API changes from R5, per e-mail from Salvador Fuentes 16 May 2022			Approved
6	ELIOT IoT Gateway Blueprint khemendra kumar		No	Incubation	https://nexus.akraino.org/content/sites/logs/huawei/job/Eliot-aio-log/19/	ELIOT R6 IoT-Gateway Datasheet	No API changes from R5, per e-mail from Khemendra Kumar 28 Apr 2022 Info for ELIOT IOTGateway APIs: https://lf-akraino.atlassian.net/wiki/display/AK/ELIOT+R6+IOTGateway+API+documentation	https://nexus.akraino.org/content/sites/logs/huawei/job/Eliot-security-test/31/results/	16 May 2022 lynis results: Accepted vuls results: Accepted kube-hunter results: Accepted	Approved
7	ELIOT SD-WAN/WAN Edge/uCPE Blueprint khemendra kumar		NO	Incubation		ELIOT R6 - SD-WAN / WAN Edge / uCPE Data Sheet	No API changes from R5, per e-mail from Khemendra Kumar 26 May 2022			Approved
8	Network Cloud and TF (Tungsten Fabric) Integration Project Sukhdev Kapur		No	Mature
9	KNI Provider Access Edge Ricardo Noriega De Soto		No	Incubation
10	KNI Industrial Edge Ricardo Noriega De Soto		No	Incubation
11	Micro-MEC Ferenc Székely
12	The AI Edge: School/Education Video Security Monitoring Yu, Liya		No	incubation	https://nexus.akraino.org/content/sites/logs/baidu/job/	Video Security Monitoring R6 Datasheet	No API changes expected from R5, per Liya Yu in TSC meeting https://nexus.akraino.org/content/sites/logs/baidu/job/31 Mar 2022. Waiting for e-mail from Liya to confirm this. Confirmed in e-mail sent by Liya 10 May 2022	https://nexus.akraino.org/content/sites/logs/baidu/job/security_scan/aiedge/5/results/		Approved based on R5 Release notes.
13	The AI Edge: Intelligent Vehicle-Infrastructure Cooperation System(I-VICS) Yu, Liya		No	Incubation	https://nexus.akraino.org/content/sites/logs/qianyi/job/	https://wiki.akraino.org/download/attachments/28970342/Intelligent%20Vehicle-Infrastructure%20Cooperation%20System%28I-VICS%29%20Datasheet.docx?version=2&modificationDate=1613872984000&api=v2	No API changes from R5, per e-mail from ZhuMing Zhang 28 Apr 2022	https://nexus.akraino.org/content/sites/logs/fate/job/I-VICS/5/	No new features or bugs have been added after R4 release	Yes, with recommendation.
14	5G MEC/Slice System to Support Cloud Gaming, HD Video and Live Broadcasting Blueprint Feng Yang		No	Incubation			No API changes from R5, per e-mail from Eagan Fu 23 May 2022			Approved based on previous release notes
15	IEC Type 3: Android cloud native applications on Arm servers in edge for Integrated Edge Cloud (IEC) Blueprint Family hanyu ding Rajeev Gadgil Davy Zhang		No	Mature	https://nexus.akraino.org/content/sites/logs/ysemi/job/v1/upload/iec-tox-verify-master_334/	https://wiki.akraino.org/download/attachments/24084647/IEC%20Release3-IEC%20Type3-datasheet.docx?version=5&modificationDate=1591272863000&api=v2	API form uploaded by Davy Zhang 28 Apr 2022, scheduled for review at API subcommittee meeting 29 Apr 2022 Approved by API subcommittee at weekly meeting 29 Apr 2022	https://nexus.akraino.org/content/sites/logs/ysemi/job/v1/validation_results_v4/ 12 May 2022 https://nexus.akraino.org/content/sites/logs/ysemi/job/v1/validation_results_v5/ 13 May 2022 https://nexus.akraino.org/content/sites/logs/ysemi/job/v1/validation_results_v6/17 May 2022	18 May 2022 lynis results: Accepted vuls results: Accepted kube-hunter results: Accepted	Approved
16	IEC Type 5: SmartNIC for Integrated Edge Cloud (IEC) Blueprint Family Fu Li jin peng		No	Incubation	https://nexus.akraino.org/content/sites/logs/socnoc/job/baseOS/1/	SOCNOC Release 6 One pag - Akraino - Akraino Confluence	No API changes expected from R5, per Leo Li in TSC meeting 07 Apr 2022. Waiting for e-mail from Leo to confirm this Leo confirmed by mail 11 May 2022	https://nexus.akraino.org/content/sites/logs/socnoc/job/security_scan/
17	Enterprise Applications on Lightweight 5G Telco Edge gaurav.agrawal		No	Incubation	https://nexus.akraino.org/content/sites/logs/huawei/job/Ealtedge-aio-log/15/	EALTEDGE Release 6 Datasheet	No API changes from R5, per e-mail from Khemendra Kumar 28 Apr 2022 Info for EALTEdge APIs: https://lf-akraino.atlassian.net/wiki/pages/viewpage.action?pageId=13669723	https://nexus.akraino.org/content/sites/logs/huawei/job/Ealt-edge-security-test/26/results/	16 May 2022 lynis results: Accepted vuls results: Accepted kube-hunter results: Accepted	Approved
18	Public Cloud Edge Interface (PCEI) Blueprint Oleg Berzin	TSC 2022-05-12 (Thursday) 7:00 am Pacific	No	Incubation	https://nexus.akraino.org/content/sites/logs/cmti/job/pcei-daily/	https://lf-akraino.atlassian.net/wiki/x/LZfQ	Revised API info form sent to Oleg per his requirements (see API Subcommittee meeting minutes 22 Apr 2022 for details) Note - PCEI Blueprint R6 API documentation located here (as of 12 Apr 2022): https://lf-akraino.atlassian.net/wiki/x/KZfQ	12 Apr 2022 https://nexus.akraino.org/content/sites/logs/pcei/job/r6/v1/	12 May 2022 lynis results: Accepted vuls results: Accepted kube-hunter results: Accepted	12 Apr 2022Approved per the upstream review https://lf-akraino.atlassian.net/wiki/x/MZfQ	12 May 2022	12 May 2022
19	The AI Edge: Federated ML application at edge rolandwu haihui wang	TSC 2022-03-17 (Thursday) 7:00 am Pacific	No	Mature	https://nexus.akraino.org/content/sites/logs/fate/job/Fate_test/15/	Akraino R6 Federated ML blueprint datasheet.docx	No API changes from R5, per e-mail from HaiHui Wang 17 Mar 2022	https://nexus.akraino.org/content/sites/logs/fate/fml/5/	Incubation Level Review Results: 20 Aug 2021 Vuls: Accepted with exceptions shown at: Release 5 Vuls Exception Request __________________________________________________________ 20 Aug 2021 Lynis: Accepted __________________________________________________________ 16 Aug 2021 Kube-Hunter: Exception granted: K8s not used by this BP.
20	KubeEdge Edge Service Blueprint Yin Ding		No	Incubation
21	Private LTE/5G ICN Blueprint Prem Sankar G Has been merged with PCEI blueprint
22	Rural Edge blueprint for Tami COVID-19 Blueprint Family Surojit Banerjee		Yes	Incubation
23	Smart Cities Olivier Bernard (Deactivated) Cindy Xing Alexander Su (alexander@nexcom.com) JasonWenMyais Jack Liu	TSC 2022-05-12 (Thursday) 7:00 am Pacific	No	Incubation	https://nexus.akraino.org/content/sites/logs/myais/job/smartcities/8	Smart Cities R6 Executive One Pager - Akraino - Akraino Confluence	No API changes expected from R5, per TSC meeting discussion 21 Apr 2022. Waiting for e-mail from Jason or Jack to confirm this. Update - API form uploaded by Jason 22 Apr 2022 , scheduled for review at API subcommittee meeting 29 Apr 2022 Approved by API subcommittee at weekly meeting 29 Apr 2022	~~https://nexus.akraino.org/content/sites/logs/myais/validation/1/~~ 14 Apr 2022 ~~https://nexus.akraino.org/content/sites/logs/myais/validation/2~~ fix lynis issue, in pb use k3s, add kube-hunter test. 29 Apr 2022 https://nexus.akraino.org/content/sites/logs/myais/validation/3 fix kube-hunter issue ,except CAP_NET_RAW. 07 May 2022	09 May 2022 lynis results: Accepted vuls results: Accepted kube-hunter results: Accepted	Smart Cities R6 Upstream. Approved	12 May 2022	12 May 2022
24	MEC-based Stable Topology Prediction for Vehicular Networks MalikAsif	TSC 2022-06-14 (Tuesday) 7:00 am Pacific	No	Incubation	Nexus repository where we push CD logs via a privately configured Jenkins	Executive One Pager - R6 (MEC-based)	API info form uploaded 15 Jun 2022 by Asif, API subcommittee to review 17 Jun 2022 Approved by API subcommittee 17 Jun 2022			Approved	21 Jun 2022
25	IEC Type 2 for Integrated Edge Cloud (IEC) Blueprint Family Site Administrator ashvin kumar Trevor Tao (Deactivated) Muhammad Hamza		No	Incubation	https://nexus.akraino.org/content/sites/logs/production/vex-yul-akraino-jenkins-prod-1/iec-tox-verify-master/	IEC Type 2 R6 Executive One Pager	No API changes from R5, per e-mail from Muhammad Hamza 24 May 2022	https://jenkins.akraino.org/view/iec/job/bluval-daily-master/ https://sonarcloud.io/project/overview?id=iec https://nexus.akraino.org/content/sites/logs/production/vex-yul-akraino-jenkins-prod-1/iec-tox-verify-master/334/		Approved	24 May 2022
26	IoT Workloads at the Smart Device Edge - Predictive Maintenance (with a Thermal Imaging Camera, vibration sensors, etc.) Vladimir Suvorov Aaron Williams		No
27	Federated Multi-Access Edge Cloud Platform Deepak Vij		No	Incubation
28	Smart Data Transaction Colin Peters		Yes	Incubation	BluVal: https://nexus.akraino.org/content/sites/logs/fujitsu/job/sdt-bluval/2/ https://nexus.akraino.org/content/sites/logs/fujitsu/job/sdt-lynis/3/ https://nexus.akraino.org/content/sites/logs/fujitsu/job/sdt-vuls/2/ Other: https://nexus.akraino.org/content/sites/logs/fujitsu/job/edgex-install/ https://nexus.akraino.org/content/sites/logs/fujitsu/job/edgex-lora/ https://nexus.akraino.org/content/sites/logs/fujitsu/job/lfedge-cluster/ https://nexus.akraino.org/content/sites/logs/fujitsu/job/lfedge-install/	SDT Datasheet.docx	Per e-mail from Colin Peters 13 Mar 2022 , blueprint consumes Kubernetes and EdgeX APIs. They are uploading API info form API info form uploaded 15 Mar 2022 Scheduled for review by API subcommittee review25 Mar 2022 Reviewed and approved by API subcommittee 25 Mar 2022	https://nexus.akraino.org/content/sites/logs/fujitsu/job/sdt-bluval/2/ https://nexus.akraino.org/content/sites/logs/fujitsu/job/sdt-lynis/3/ https://nexus.akraino.org/content/sites/logs/fujitsu/job/sdt-vuls/2/	15 Apr 2022 sdt-lynis results: Accepted sdt-vuls results: Accepted All Exceptions are granted Release 6: Akraino CVE Vulnerability Exception Request	Smart Data Transaction for CPS Release Notes Approved	2022/04/13	2022/04/14
29	Robot basic architecture based on SSES Haruhisa Fukano		Yes	Incubation	https://nexus.akraino.org/content/sites/logs/fujitsu/job/robot-family/sses-lynis/ https://nexus.akraino.org/content/sites/logs/fujitsu/job/robot-family/sses-lynis/	Robot basic architecture based on SSES One Pager	Per e-mail from Inoue Reo 17 Mar 2022 , blueprint does not export or consume APIs. They are uploading an API info form to indicate this, along with comments about future / possible API plans Inoue Reo uploaded an API info form 17 Apr 2022. Review by API subcommittee is scheduled for 01 Apr 2022 Reviewed and approved by API subcommittee	https://nexus.akraino.org/content/sites/logs/fujitsu/job/robot-family/sses-lynis/ https://nexus.akraino.org/content/sites/logs/fujitsu/job/robot-family/sses-lynis/	20 Apr 2022 robot Lynis results: Accepted iotgateway Lynis results: Accepted robot vuls results: Accepted All exceptions are granted iotgateway vuls results: Accepted All exceptions are granted Release 6: Akraino CVE Vulnerability Exception Request	Approved per the BP upstream review	2022/04/13	2022/04/14

Browser not supported