| View file | ||||
|---|---|---|---|---|
|
Release 4 target date is November 30th 2020.
...
- Virtual meeting to start to have a session to discuss all of the agenda items.
- Different patches from different blueprints need to be up-streamed.
- Need a consistent framework
- New blueprints have been committed for R3R4.
- Want to increase standards on Release 34.
- Validation Project test layers and test cases
- Incubation Self Certification in R3R4?
Release 4 Requirements
| View file | ||||
|---|---|---|---|---|
|
- 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: no mandatory requirements for Incubation self-certified or MaturitySee 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 R4 release Upstream BP review status, Release Upstream Compliance. Also please refer to the page for the R4 requirement as well.
...
Internal Target date to meet Rel 4 Criteria is Nov 30th ( please add your target/achieved date at the BP Incubation Stage Reporting R2 (To Be Updated))
(To be updated)
| No. | Project Name |
|---|
| TSC Subgroup Release Status | Is this your first release | Going for Maturity Review? | 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)
BluVal
Certification
Security
Certification
Pass/Fail Criteria: Steps To Implement Security Scan Requirements
Date ready for TSC review
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: |
|---|
be modified
CentOS 8 is not supported in BluVal at the moment. Test has been run manually. And the results are in the Nexus.
Vuls, Lynis: Accepted
- with exceptions listed in link below.
Kube-Hunter: Exemption granted, this blueprint does not currently use Kubernetes.
Bluval validation missing in Test Doc. Rest of the Doc is accepted
Same status as Connected Vehicle.
1. ToC is missing in all doc. 2. Installation doc still has a lot of important sections missing. 3. Lic term is supposed to be a separate section, not under Software Components
Note: I have reviewed this BP, multiple times. Please follow the templates on the Doc Subcommittee page.
Not ready
Accepted
Tina to setup follow up with Randy and Tapio. Expect to close by
Upstream Review (Column filled by Upstream Subcommittee and PTLs) (note PTL can go to R4 Release Upstream Compliance to find details) | Date ready for TSC review (Column filled in by PTLs) | TSC Review Date (Column filled in by TSC) | |||||||
|---|---|---|---|---|---|---|---|---|---|
| 1 | scheduled at | N | Y | https://nexus.akraino.org/content/sites/logs/parserlabs/r4/jobs/cvb/ | Form uploaded Scheduled for API subcommittee review Waiting for re-uploaded API info form with PaaS API info Reviewed by API subcommittee, PaaS APIs are subset of TARS APIs Accepted |
CentOS 8 is not supported in BluVal at the moment. Test has been run manually. And the results are in the Nexus.
Vuls, Lynis: Accepted
- with exceptions listed in link below.
Kube-Hunter: Exemption granted, this blueprint does not currently use Kubernetes.
Complete
- Please add license terms in the Installation doc or Architecture doc.
- TOC is missing in a few of your Docs
- It would be helpful if you have the R3 docs clearly identified, they can have ref to the older docs. Currently, it's not organized by release like other BPs
Not Accepted yet
Accepted
Complete
Accepted
ICN Master Baremetal Deployment Verifier
ICN Master Virtual Deployment Verifer
ICN Master Hardware Baremetal Deployment Verifer
Vuls, Lynis, Kube-Hunter: Accepted - with exceptions listed in link below.
All test cases are performed, the first review is done by Security Sub Committee on 13th May 2020 and the latest updates have been updated in the Security Scan Status
Complete
Accepted
| Yes | 12/01 | |||||||||||
| 2 | scheduled at | N | Y | https://nexus.akraino.org/content/sites/logs/parserlabs/r4/jobs/iec-type4/ | Form uploaded Scheduled for API subcommittee review Waiting for re-uploaded API info form with PaaS API info Reviewed by API subcommittee, PaaS APIs are subset of TARS APIs Accepted |
Vuls: Accepted with exceptions shown at: Release 4 Vuls Exception Request https://nexus.akraino.org/content/sites/logs/tencent/MR/iec-type4/
Lynis: Accepted No Exceptions Required, Excellent! https://nexus.akraino.org/content/sites/logs/tencent/MR/iec-type4/ Kube-Hunter: Exception granted: K8s not used by this BP. | Yes | 12/01 | ||||
| 3 | Scheduled at Release 4 Review 2020-12-01 (Tues) 7 am Pacific | N | Mature | https://nexus.akraino.org/content/sites/logs/att/job/Install_REC_on_OpenEdge1/ | Form uploaded Reviewed by API subcommittee Accepted | https://nexus.akraino.org/content/sites/logs/att/job/Bluval_Logs/results-11-27-2020.tar | https://nexus.akraino.org/content/sites/logs/att/job/Bluval_Logs/results-2021-02-01/
Vuls: Accepted with exceptions shown at: Release 4 Vuls Exception Request
Lynis: Accepted with exceptions shown at: Kube-Hunter: Accepted with exceptions shown at: | Yes | 12/01 | |||
| 4 | Scheduled at | N | N | ICN Master Baremetal Deployment Verifier | Form uploaded Reviewed by API subcommittee Accepted | https://nexus.akraino.org/content/sites/logs/intel/bluval_results/icn/master/20201210-010310/. | https://nexus.akraino.org/content/sites/logs/intel/bluval_results/icn/master/20201210-010310/ ICN R4 Test Document#BluValTesting Vuls: Accepted with exceptions shown at: Lynis: Accepted with exceptions shown at: k8s/conformance:
Kube-Hunter: Accepted
| Yes | 12/10 | 12/16 | ||
| 5 | scheduled at | N | N | ELIOT R4 IOT-Gateway Datasheet | Form uploaded Reviewed by API subcommittee Accepted | vuls exceptions Akraino CVE Vulnerability Exception Request |
Vuls: Accepted with exceptions shown at: Lynis: Accepted with exceptions shown at: Kube-Hunter: Accepted with exceptions shown at: | Yes | 12/08 | |||
| 6 | scheduled at | N | N | https://nexus.akraino.org/content/sites/logs/huawei/blueprints/uCPE/job/eliot-uCPE-deploy-k8s-centos-virtual-daily-master/545/ | ELIOT R4 - SD-WAN / WAN Edge / uCPE Data Sheet | Form uploaded Reviewed by API subcommittee Accepted | vuls exceptions Akraino CVE Vulnerability Exception Request |
Vuls: Accepted with exceptions shown at: Lynis: Accepted with exceptions shown at: Kube-Hunter: Accepted with exceptions shown at: | Yes | 12/08 | ||
| 7 | Scheduled at Release 4 Review 2020-12-09 (Wed) 7:30am | N | Not Applicable | https://nexus.akraino.org/content/sites/logs/juniper/job/NC-Tungsten_Fabric/40/ https://nexus.akraino.org/content/sites/logs/juniper/validation-2021/ | Form uploaded Scheduled for API subcommittee review Reviewed by API subcommittee Accepted | Y | https://nexus.akraino.org/content/sites/logs/juniper/validation/ Updated results - https://nexus.akraino.org/content/sites/logs/juniper/validation-2021/
Vuls: Accepted with exceptions shown at:
Lynis: Accepted with exceptions shown at: Note there were exceptions granted for mandatory incubation items that must be fixed in the next incubation level release as well as other items that must be fixed for maturity.
Kube-Hunter: Accepted with exceptions shown at: | Yes | 12/09 | 12/09 | ||
| 8 | Scheduled at | N | N | AWS footprint: GCP footprint: | Form uploaded Reviewed by API subcommittee Accepted | https://nexus.akraino.org/content/sites/logs/redhat-kni/bluval_results_pae/ |
Vuls: Accepted with exception. The KNI Provider Access Edge blueprint uses OpenShift as its k8s distribution, which is deployed on Red Hat CoreOS, an immutable OS that is not supported by Vuls. https://nexus.akraino.org/content/sites/logs/redhat-kni/bluval_results_pae/os/vuls/log.html.gz Lynis:
https://nexus.akraino.org/content/sites/logs/redhat-kni/bluval_results_pae/os/lynis/ Accepted with exceptions shown at: Accepted with exceptions shown at: | Yes | 12/09 | 12/09 | ||
| 9 | Slides for KNI blueprints review: | Scheduled at | Y | N | Mgmt Hub logs: IE logs: | Form uploaded Reviewed by API subcommittee Accepted | https://nexus.akraino.org/content/sites/logs/redhat-kni/bluval_results_ie/ |
Vuls: Accepted with exception. The KNI Industrial Edge blueprint uses OpenShift as its k8s distribution, which is deployed on Red Hat CoreOS, an immutable OS that is not supported by Vuls. https://nexus.akraino.org/content/sites/logs/redhat-kni/bluval_results_ie/os/vuls/log.html.gz Lynis: https://nexus.akraino.org/content/sites/logs/redhat-kni/bluval_results_ie/os/lynis/ Accepted with exceptions shown at: Kube-Hunter: Accepted with exceptions shown at: | Yes | |||
| 10 | Y | N | https://nexus.akraino.org/content/sites/logs/micromec | Akraino R3 MicroMEC blueprint datasheet.docx | Form uploaded API committee review scheduled for Reviewed by API subcommittee Accepted | N/A | ||||||
| 11 | N | N | https://nexus.akraino.org/content/sites/logs/baidu/job/aiedge-otestack-master-deploy/ https://nexus.akraino.org/content/sites/logs/baidu/job/aiedge-otestack-master-validation/ | Hechun replied by e-mail 12Jan, API info form is in progress Form uploaded API committee review tentatively scheduled for Reviewed by API subcommittee Accepted | https://nexus.akraino.org/content/sites/logs/baidu/job/bluval/aiedge/results/ | https://nexus.akraino.org/content/sites/logs/baidu/job/security_scan/aiedge/2/results/
Vuls: Accepted with exceptions shown at: Lynis: Accepted with exceptions shown at: Kube-Hunter: Accepted with exceptions shown at: Release 4 Kube-Hunter Exceptions | Yes (Please also update the upstream version besides the repo name) | 06/02 | ||||
| 12 | Y | N | https://nexus.akraino.org/content/sites/logs/baidu/job/xinhong/results/ | Form uploaded API subcommittee review scheduled for Reviewed by API Subcommittee Accepted | N/A |
Vuls: Accepted with exceptions shown at: Release 4 Vuls Exception Request Lynis: The following must be fixed for incubation:
Kube-Hunter: Exception granted: K8s not used by this BP. | Yes （Please update the upstream versions besides the repo name) | |||
| 13 | Y | N |
Vuls, Lynis,
Form uploaded Reviewed by API subcommittee Accepted | N/A | https://nexus.akraino.org/content/sites/logs/tencent/bluval/results_upload
Vuls: Accepted with exceptions shown at: Release 4 Vuls Exception Request Lynis: Accepted with exceptions shown at: |
Kube-Hunter: Accepted |
with exceptions |
shown at: | Please update the release note with upstream information (R4 to R6 - Release Notes) | 06/03 | |
| 14 |
Complete
TOC missing in Architecture, Installation and Test doc.
Accepted
Ready for TSC approval.| N | N | https://nexus.akraino.org/content/sites/logs/ |
| arm-china/ |
| jenkins092/iec-type3-android-cloud-ubuntu1804-daily-master/ |
| job/nvdroid/17/ | IEC Release4-IEC Type3-datasheet.docx | Hanyu replied by e-mail that they have no APIs offered or consumed. API subcommittee replied they still need to fill out the API info reporting form with BP name and Comments field explaining current and future API status, and upload the form Form uploaded Reviewed by API Subcommittee Accepted | Bluval Exception has been accepted |
Complete
Not Accepted yet
- TOC should be in all documents.
- Doc should be aligned with the template posted on Doc SC page
Not completely addressed the above two, sent email
Accepted
arm-china/jenkins092/iec-type3-android-cloud-ubuntu1804-daily-master/job/nvdroid/30/ Vuls：Accepted with exceptions shown at: Release 4 Vuls Exception Request |
Complete
- TOC missing in Docs - [ Yolanda - added ]
- Installation Doc has missing sections, ref to the template on Doc subcommittee page - [ Yolanda: added relevant sections and restructured ]
Accepted
Ready for TSC approval.
jenkins092/iec-type3-android-cloud-ubuntu1804-daily-master/job/nvdroid/34/ Lynis: Accepted with exceptions shown at: Kube-Hunter: Exception granted: K8s not used by this BP. | Yes | 02/04 | ||
| 15 | Scheduled at | N | N |
Form uploaded Scheduled for API subcommittee review Reviewed by API subcommittee Accepted | Bluval Exception has been accepted for the project. |
Lynis & Kube-Hunter: Accepted
- with exceptions listed in link below.
Vuls: Exemption granted, this blueprint uses RHCoreOS which vuls does not support.
Complete
TOC missing
Accepted
https://logs.akraino.org/redhat-kni/bluval_results/blueprint-pae/20200505-104443/out.log
china/jenkins092/iec-type3-android-cloud-ubuntu1804-daily-master/job/nvdroid/34/ Lynis：Accepted with exceptions shown at: Kube-Hunter: Exception granted: K8s not used by this BP. | Yes | |||||||
| 16 | scheduled at | N | N | Form uploaded Reviewed by API subcommittee Accepted | Vuls Exception Akraino CVE Vulnerability Exception Request |
Complete
Not Accepted yet
Address the review comments posted on Doc SC page
Accepted
/huawei/blueprints/ealt-edge/job/ealt-edge-bluval-daily-master/251/results/ Akraino CVE Vulnerability Exception Request
Vuls: Accepted with exceptions shown at: Release 4 Vuls Exception Request Lynis: Accepted with exceptions shown at: Kube-Hunter: Accepted with exceptions shown at: updated results link - 09-dec | Yes | 12/10 | |
| 17 | Scheduled at TSC 2021-1-14 (Thurs) 7 am Pacific PCEI Time Slot 7:30-8:00 am Pacific | Y |
| https://nexus.akraino.org/content/sites/logs/ |
| cmti/job/ |
Complete
Look at the Documentation Template. A number of key elements missing in:
Inst Doc: Uninstall, Dev Guide and Troubleshooting
Test: Test Env setup
Accepted
| pcei-daily/ | PCEI R4 Datasheet | Form uploaded 4Jan Scheduled for API subcommittee review For R4, third-party location API provided as an example in PCEI architecture diagrams. For R5 they expect PCEI APIs to be exported Reviewed by API subcommittee Accepted | https://nexus.akraino.org/content/sites/logs/pcei/job/v1/ New BluVal logs 2021-01-08: https://nexus.akraino.org/content/sites/logs/pcei/job/v2/results/
Updated BluVal logs with fixed sysctl key net.ipv4.conf.default.accept_source_route |
Updated BluVal logs with fixed Kube-Hunter Vulnerability KHV050, KHV002, KHV005 |
Vuls, Lynis, Kube-Hunter: Accepted - with exceptions listed in link below.
Incubation BP
Complete
TOC needs to be in all Doc.
Follow the template of the Doc
Inst Doc: Uninstall, Dev Guide and Troubleshooting
Release Doc needs update to include items in template
Accpeted
Pending closer Doc SC. CD Logs need to be updated. Tina will follow up with PTL
23 June 2020 - TSC sub-group reviewed the logs and requirements met. Ready for TSC approval.
.org/content/sites/logs/pcei/job/v4/ |
Vuls: Vuls: Accepted with exceptions shown at: Release 4 Vuls Exception Request vuls.log included in the new logs (V2) Lynis: Accepted with exceptions shown at: Kube-Hunter: Accepted with exceptions shown at: Release 4 Kube-Hunter Exceptions | Yes | 01/14/21 | ||||||
| 18 | Scheduled at | Y | N | https://nexus.akraino.org/content/sites/logs/webank/job/ | Federated ML application at edge R4 Datasheet | Form uploaded Reviewed by API subcommittee Accepted | N/A | https://nexus.akraino.org/content/sites/logs/webank/job/FL_SCAN/results/ https://nexus.akraino.org/content/sites/logs/webank/job/FL_SCAN/lynis_fixed/
Vuls: Accepted with exceptions shown at: Release 4 Vuls Exception Request
Lynis: Accepted with exceptions shown at: |
Complete
TOC needs to be in all Doc.
Follow the template of the Doc
Inst Doc: Uninstall, Dev Guide and Troubleshooting
Release Doc needs update to include items in template
Accepted
Vuls & Lynis: Accepted - with exceptions listed in link below.
Accepted: First release - Kube-Hunter security scan not required.
Kube-Hunter: Exception granted: K8s not used by this BP. | Yes | 12/08 | |
| 19 | Scheduled at Release 4 Review 2020-11-17 (Tue) 7 am Pacific |
| Y | N | https://nexus.akraino.org/content/sites/logs/ |
| futurewei/ |
| kubeedgees/ | KubeEdge Edge Service Blueprint Release 4 datasheet | Form uploaded Reviewed by API subcommittee Accepted | Yes |
Vuls & Lynis: Accepted
Logs received from:
Yihui Wang, wangyihui@chinamobile.com
- with exceptions listed in link below.
Kube-Hunter: Exemption granted, this blueprint does not currently use Kubernetes.
Complete
Updated the Installation doc with config details, included the Lic terms with Upstream. Updated the Test doc to reflect setup.
Accepted as per review comments
Vuls: Accepted with exceptions shown at: Release 4 Vuls Exception Request
Lynis: Accepted Kube-Hunter: Exception granted: KubeEdge node is not on same subnet as the cloud node. Communication occurs through the websocket endpoint, so kube-hunter can't be used. | Yes | 11/17 | |||
| 20 | Scheduled at | Y | N | https://nexus.akraino.org/content/sites/logs/ |
| juniper/ |
| job/ |
| Private%205G%20BP/ | Akraino Private LTE/5G BP Datasheet | Prem replied by e-mail 17Jan, API info form is in progress Form uploaded API committee review scheduled for Reviewed by API subcommittee Accepted | N/A | Private 5G/LTE is using Tungsten Fabric hosts and Kubernetes orchestration. Vuls: Accepted using Network Cloud and TF approval Lynis: Accepted using Network Cloud and TF approval Kube-Hunter: Accepted using Network Cloud and TF approval See: Network Cloud and TF (Tungsten Fabric) Integration Project | Yes | 02/24 | ||
| 21 | Scheduled at Release 4 Review 2020-12-09 | Y | N | https://nexus.akraino.org/content/sites/logs/ai_solutions/job/Eden-flir/ | Form uploaded Reviewed by API subcommittee , waiting for revised API info form to be uploaded 2nd revision of form uploaded by V S Final review by API subcommittee set for Reviewed by API subcommittee Accepted | Have an exception |
Vuls, Lynis and Kube-Hunber: Accepted
- with exceptions listed in link below.
Test results provided by Srinivasan Selvam
NA (First Release)
Note: Security tools (Vuls, Lyns & Kube-Hunter) has been integrated with no critical test failures.
Test results provided by Jian Li
Vuls: The vuls.log file needs to be uploaded/provided. It contains the test results to make our security evaluation. Also, can you verify which OS and version this blueprint is using is it linuxkit?
Lyins: The lynis.log file needs to be uploaded/provided. It contains the test results to make our security evaluation.
Kube-Hunter: Exception granted: K8s not used by this BP. | Yes | 12/09 |
03/02~03/2020 Akraino TSC F2F & 2020 Planning meeting
...