...
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.
...
- High Level Overall Requirements
- CI, Blueprint Validation Lab Sub-Committee Requirements
- Present Pod Topology document.
- Peering w/LF Jenkins - (Note: peering is an optional requirement)
- Push logs through Nexus. (Note: This is mandatory for Incubation self-certified and Maturity)
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)
- 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.
...
| 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 BlueVal Logs or Manual Logs | 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 | No | Mature | https://nexus.akraino.org/content/sites/logs/parserlabs/r4/cvb/ | https://nexus.akraino.org/content/sites/logs/parserlabs/r4/ | Approved | ||||||||
| 2 | No | Mature | https://nexus.akraino.org/content/sites/logs/parserlabs/r4/cvb/ | No API changes expected from R5, per Bart Dong in TSC meeting . Waiting for e-mail from Bart to confirm this Bart confirmed by e-mail | https://nexus.akraino.org/content/sites/logs/parserlabs/r4/ | Approved | |||||||
| 3 | |||||||||||||
| 4 | No | Incubation | ICN R6 Datasheet | No API changes from R5, per e-mail from Kural Ramakrishnan | BluVal Results |
lynis results: Accepted vuls results: Accepted kube-hunter results: Accepted | Approved |
| |||||
| 5 | No | EOL | No API changes from R5, per e-mail from Salvador Fuentes | Approved | |||||||||
| 6 | No | Incubation | https://nexus.akraino.org/content/sites/logs/huawei/job/Eliot-aio-log/19/ | No API changes from R5, per e-mail from Khemendra Kumar Info for ELIOT IOTGateway APIs: | https://nexus.akraino.org/content/sites/logs/huawei/job/Eliot-security-test/31/results/ | lynis results: Accepted vuls results: Accepted kube-hunter results: Accepted | Approved | ||||||
| 7 | NO | Incubation | ELIOT R6 - SD-WAN / WAN Edge / uCPE Data Sheet | No API changes from R5, per e-mail from Khemendra Kumar | Approved | ||||||||
| 8 | No | Mature | |||||||||||
| 9 | No | Incubation | |||||||||||
| 10 | No | Incubation | |||||||||||
| 11 |
| ||||||||||||
| 12 | 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/. Waiting for e-mail from Liya to confirm this. Confirmed in e-mail sent by Liya | https://nexus.akraino.org/content/sites/logs/baidu/job/security_scan/aiedge/5/results/ | Approved based on R5 Release notes. | ||||||
| 13 | No |
| 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 | 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 | No | Incubation | No API changes from R5, per e-mail from Eagan Fu | Approved based on previous release notes | |||||||||
| 15 | 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 , scheduled for review at API subcommittee meeting Approved by API subcommittee at weekly meeting |
https://nexus.akraino.org/content/sites/logs/ysemi/job/v1/validation_results_v5/
https://nexus.akraino.org/content/sites/logs/ysemi/job/v1/validation_results_v6/ |
lynis results: Accepted vuls results: Accepted kube-hunter results: Accepted | Approved | |||||
| 16 | No | Incubation | https://dev.socnoc.cn/#/homenexus.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 . Waiting for e-mail from Leo to confirm this Leo confirmed by mail | socnoc - Akraino - Akraino Confluencehttps://nexus.akraino.org/content/sites/logs/socnoc/job/security_scan/ | |||||||
| 17 | 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 | https://nexus.akraino.org/content/sites/logs/huawei/job/Ealt-edge-security-test/26/results/ |
lynis results: Accepted vuls results: Accepted kube-hunter results: Accepted | Approved | |||||
| 18 | TSC 2022-05-12 (Thursday) 7:00 am Pacific | No | Incubation | https://nexus.akraino.org/content/sites/logs/cmti/job/pcei-daily/ | https://wikilf-akraino.akrainoatlassian.orgnet/wiki/x/SC0wAwLZfQ | Revised API info form sent to Oleg per his requirements (see API Subcommittee meeting minutes for details) Note - PCEI Blueprint R6 API documentation located here (as of ): https://wikilf-akraino.akrainoatlassian.orgnet/wiki/x/Qy0wAwKZfQ |
lynis results: Accepted vuls results: Accepted kube-hunter results: Accepted |
|
| ||||
| 19 | 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 | 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 | No API changes expected from R5, per TSC meeting discussion . Waiting for e-mail from Jason or Jack to confirm this. Update - API form uploaded by Jason , scheduled for review at API subcommittee meeting Approved by API subcommittee at weekly meeting |
fix lynis issue, in pb use k3s, add kube-hunter test.
https://nexus.akraino.org/content/sites/logs/myais/validation/3 fix kube-hunter issue ,except CAP_NET_RAW.
|
lynis results: Accepted vuls results: Accepted kube-hunter results: Accepted | Approved |
|
| ||||
| 24 | TSC 2022-06-14 (Tuesday) 7:00 am Pacific | No | Incubation | Nexus repository where we push CD logs via a privately configured Jenkins | API info form uploaded by Asif, API subcommittee to review Approved by API subcommittee | Approved |
| ||||||
| 25 | No | Incubation | No API changes from R5, per e-mail from Muhammad Hamza | https://jenkins.akraino.org/view/iec/job/bluval-daily-master/ | Approved | ||||||||
| 26 | No | ||||||||||||
| 27 | No | Incubation | |||||||||||
| 28 | 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 , 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/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/ |
sdt-lynis results: Accepted sdt-vuls results: Accepted All Exceptions are granted | Smart Data Transaction for CPS Release Notes Approved | 2022/04/13 | 2022/04/14 | |||
| 29 | 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 , 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/ |
robot Lynis results: Accepted iotgateway Lynis results: Accepted robot vuls results: Accepted iotgateway vuls results: Accepted | Approved per the BP upstream review | 2022/04/13 | 2022/04/14 |
...