Release 6 target date is April 30th 2022.
The requirements for the blueprints to be included in release 5 are as follows:
Depending upon the situation, the PTLs are suggested to meet the following criteria -
If the blueprint is already part of release 5 and you want this to be included in release 5, please follow the following steps:
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.
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.
Please follow the requirements specified in release 6 with the following exceptions:
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.
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).
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).
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)
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
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
| CD Logs URL to be used for review (Column filled in by PTLs) | 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 Certification | Security Certification Provide link to Vuls, Lynis, and Kube-Hunter logs below. Pass/Fail Criteria: Steps To Implement Security Scan Requirements Exception requests should be filed at: | 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 | No | Mature | |||||||||||
2 | No | Mature | No API changes expected from R5, per Bart Dong in TSC meeting . Waiting for e-mail from Bart to confirm this | ||||||||||
3 | |||||||||||||
4 | Incubation | ||||||||||||
5 | No | Incubation |
| ||||||||||
6 | No | Incubation | |||||||||||
7 | NO | Incubation | |||||||||||
8 | No | Incubation | |||||||||||
9 | No | Incubation | |||||||||||
10 | No | Incubation | |||||||||||
11 |
| ||||||||||||
12 | No | incubation | No API changes expected from R5, per Liya Yu in TSC meeting . Waiting for e-mail from Liya to confirm this | ||||||||||
13 | No |
| https://nexus.akraino.org/content/sites/logs/fate/job/I-VICS/5/ | No new features or bugs have been added after R4 release | |||||||||
14 | No | Incubation | |||||||||||
15 | No | Incubation | |||||||||||
16 | No | Incubation | No API changes expected from R5, per Leo Li in TSC meeting . Waiting for e-mail from Leo to confirm this | ||||||||||
17 | No | Incubation | |||||||||||
18 | No | Incubation | https://wiki.akraino.org/x/SC0wAw | ||||||||||
19 | No |
| 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 | Incubation Level Review Results:
Vuls: Accepted with exceptions shown at: Release 5 Vuls Exception Request __________________________________________________________ Lynis: Accepted __________________________________________________________ Kube-Hunter: Exception granted: K8s not used by this BP. | | ||||||
20 | No | Incubation | |||||||||||
21 | |||||||||||||
22 | Yes | Incubation | |||||||||||
23 | No | Incubation | https://nexus.akraino.org/content/sites/logs/myais/job/smartcities/8 | ||||||||||
24 | No | Incubation | |||||||||||
25 | No | Incubation | |||||||||||
26 | No | ||||||||||||
27 | No | Incubation | |||||||||||
28 | Yes | Incubation | BluVal: https://nexus.akraino.org/content/sites/logs/fujitsu/job/sdt-bluval/ https://nexus.akraino.org/content/sites/logs/fujitsu/job/sdt-lynis/ https://nexus.akraino.org/content/sites/logs/fujitsu/job/sdt-vuls/ 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 , blueprint consumes Kubernetes and EdgeX APIs. They are uploading API info form API info form uploaded Scheduled for review by API subcommittee review Reviewed and approved by API subcommittee | https://nexus.akraino.org/content/sites/logs/fujitsu/job/sdt-bluval/ https://nexus.akraino.org/content/sites/logs/fujitsu/job/sdt-lynis/ https://nexus.akraino.org/content/sites/logs/fujitsu/job/sdt-vuls/ | 2022/04/13 | 2022/04/14 | |||||
29 | Yes | Incubation | BluVal: 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 , 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 . Review by API subcommittee is scheduled for 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/ |
iotgateway Lynis: Need to fix the following vulnerabilities:
robot Lynis: Need to fix the following vulnerabilities:
| This blueprint does not have contribution to upstream project and upstream dependency. | 2022/04/13 | 2022/04/14 |