Release 3 target date is May 30th 2020.
- Self Certified Milestones Achievement Due Date Apr 30th 2020 ( Milestone 4)
View file | ||||
---|---|---|---|---|
|
2. Maturity Review Milestone Achievement Due date Apr 30th 2020
View file | ||||
---|---|---|---|---|
|
Please add targeted and achieved R3 milestones at:
BP Incubation Stage Reporting R2 (To be updated)
Define area of focus
(to be updated)
- 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 R3.
- Want to increase standards on Release 3.
- Validation Project test layers and test cases
- Incubation Self Certification in R3?
Release 3 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 for Maturity Review Approved by TSC July 11, 2019,please fill in Security Scan Status (Note this is not required for self certification, only required for maturity review)
- Blueprint Validation Framework Feature Project Requirements See TSC meeting and Slides
- 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 Maturity)
- 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)
Blue Prints Participating in Release 3
Internal Target date to meet Rel 3 Criteria is Apr 30th ( please add your target/achieved date at the BP Incubation Stage Reporting R2)
(To be updated)
Project Name | Documentation Review 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 (Column filled in by PTLs) | TSC Review Date (Column filled in by TSC) |
---|---|---|---|---|---|---|---|---|---|
Bluval validation missing. Rest of the Doc is accepted 1. Needs to specify what Bluval layer tests executed 2. Inst doc needs Lic details. Thor Chin please add this. Not ready | N | Not Applicable | https://nexus.akraino.org/content/sites/logs/tencent/job/connectedVehicle/TestCompileCode/ https://nexus.akraino.org/content/sites/logs/tencent/job/connectedVehicle/TestConnectVehicleService/ https://nexus.akraino.org/content/sites/logs/tencent/job/CD_Install_Tars/ |
This blueprint does not have output information from vuls, lynis or kube-hunter. I have sent an email to Thor Chin and Tapio Tallgren. This appears to be an issue with BluVal not executing the scans correctly. | 05/28 | ||||
Bluval validation missing in Test Doc. Rest of the Doc is accepted Same status as Connected Vehicle. Not ready | N | N | https://nexus.akraino.org/content/sites/logs/tencent/job/iectype4/iec_deploy/ https://nexus.akraino.org/content/sites/logs/tencent/job/iectype4/Develop_Tars/ https://nexus.akraino.org/content/sites/logs/tencent/job/iectype4/CompileTarsCode/ https://nexus.akraino.org/content/sites/logs/tencent/job/iectype4/VR_Classroom_Deployment/ https://nexus.akraino.org/content/sites/logs/tencent/job/iectype4/iec_destroy/ |
No security scan logs received for vuls, lynis or kube-hunter. | 05/28 | ||||
Complete
Not Accepted yet | N | Oct 31st | https://nexus.akraino.org/content/sites/logs/att/job/Install_REC_on_OpenEdge1/ | 5/26 | |||||
Complete Accepted | N | Not Applicable | ICN Master Baremetal Deployment Verifier ICN Master Virtual Deployment Verifer ICN Master Hardware Baremetal Deployment Verifer | ICN R3 Data sheet | Y |
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 | 05/29 | 06/02 | |
Complete Accepted | N | N | https://nexus.akraino.org/content/sites/logs/huawei/blueprints/iotgateway/job/eliot-iotgateway-deploy-k8s-virtual-daily-master/430/ | ELIOT R3 IOT-Gateway Datasheet | Y | 05/26 | |||
Complete TOC missing in Architecture, Installation and Test doc. Accepted | N | N | ELIOT R3 uCPE Datasheet | Y | 05/26 | ||||
Complete Not Accepted yet
Not completely addressed the above two, sent email | N | Not Applicable | https://nexus.akraino.org/content/sites/logs//juniper/job/NC-Tungsten_Fabric/37/ https://nexus.akraino.org/content/sites/logs/juniper/validation/ | Y |
Vuls & Lynis: Accepted - with exceptions listed in link below. Kube-Hunter: requested that Sukhdev verify if remediations listed in Steps To Implement Security Scan Requirements can be use in this blueprint. Some checks are not applicable because of VM based deployment | 05/21 | 06/02 | ||
Complete
| N | N | https://nexus.akraino.org/content/sites/logs/redhat-kni/192.168.112.199/kni-deploy-baremetal/7/ | N [ Not passing as blueprint is based on OKD, not Kubernetes. So we run our own validation suite - https://logs.akraino.org/redhat-kni/bluval_results/blueprint-pae/20200505-104443/out.log ] |
Lynis & Kube-Hunter: Accepted - with exceptions listed in link below. Vuls: no scan output provided, emailed Yolanda Mota. | 05/05 | 05/19 | ||
ACRN Kailasnath Maneparambil | Y | N | |||||||
Complete TOC missing | Y | N | https://nexus.akraino.org/content/sites/logs/micromec | Akraino R3 MicroMEC blueprint datasheet.docx | N/A | ||||
Complete Not Accepted yet
| Y | 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/ | N/A |
Exception: Vuls doesn't work on ARM server since the binary cannot be compiled successfully on ARM server.
Vuls, Lynis, Kube-Hunter: Accepted - with exceptions listed in link below. | 06/02 | |||
Complete Look at the Documentation Template. A number of key elements missing in: Inst Doc: Uninstall, Dev Guide and Troubleshooting Test: Test Env setup | Y | N | https://nexus.akraino.org/content/sites/logs/tencent/job/5g-mec-cloud-gaming-CD/15/ | 5G MEC Rel 3 Datasheet | N/A |
Vuls, Lynis, Kube-Hunter: Accepted - with exceptions listed in link below. Incubation BP | 06/03 | ||
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 | Y | Y | https://nexus.akraino.org/content/sites/logs/bytedance/job/android-x86/47/ | IEC Release3-IEC Type3-datasheet.docx | NA (First Release) |
Need scan results for Vuls, Lynis, and Kube-Hunter. | 06/04 | ||
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 | Y | N | https://nexus.akraino.org/content/sites/logs/bytedance/job/run-install-bluefield-fs/ https://nexus.akraino.org/content/sites/logs/bytedance/job/run-install-ovs-dpdk/ | NA (First Release) |
Vuls did not run correctly, no vuls.log file created. Lynis.log file has not be received. Kube-Hunter: Exemption granted, this blueprint does not currently use Kubernetes. | 06/04 | |||
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 | Y | N | https://nexus.akraino.org/content/sites/logs/huawei/blueprints/ealt-edge/job/ealt-edge-deploy-virtual-daily-master/135/ | EALTEdge Rel 3 Datasheet | NA (First Release) |
Vuls & Lynis: Accepted - with exceptions listed in link below. Kube-Hunter: requested that Gaurav verify if remediations listed in Steps To Implement Security Scan Requirements can be used in this blueprint. NA (First Release) Note: Security tools (Vuls, Lyns & Kube-Hunter) has been integrated with no critical test failures. | 05/28 | ||
Completed 1. Test Doc: Can you please provide the h/w required to validate the BP. 2. Installation doc: Should include config with a diagram Comments addressed. Accepted | Y | N | https://nexus.akraino.org/content/sites/logs/cmti/job/pcei-daily/ | PCEI Release 3 Datasheet | N/A | Vuls: incorrect scan output provided, need lynis.log file emailed Oleg Berzin vuls report: https://nexus.akraino.org/content/sites/logs/cmti/job/pcei-vuls/ Lynis: incorrect scan output provided, need lynis.log file emailed Oleg Berzin Lynis report: https://nexus.akraino.org/content/sites/logs/cmti/job/pcei-lynis/ Kube-Hunter: incorrect scan output provided, need lynis.log file emailed Oleg Berzin kube-hunter report: https://nexus.akraino.org/content/sites/logs/cmti/job/pcei-kube-hunter/ | 06/03 | 06/03 |