Release 4 Planning
Release 4 target date is November 30th 2020.
Self Certified Milestones Achievement Due Date Oct 31st 2020 ( Milestone 4)
2. Maturity Review Milestone Achievement Due date Oct 31st 2020
Please add targeted and achieved R4 milestones at:
BP Incubation Stage Reporting R4 (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 R4.
Want to increase standards on Release 4.
Validation Project test layers and test cases
Self Certification in R4?
Release 4 Requirements
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 R4 release Upstream BP review status, Release Upstream Compliance. Also please refer to the page for the R4 requirement as well.
Blue Prints Participating in Release 4
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? | 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) | 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: https://lf-akraino.atlassian.net/wiki/display/AK/Akraino+CVE+Vulnerability+Exception+Request | 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 | @thorking @Tao Wang | scheduled at | N | Y | https://nexus.akraino.org/content/sites/logs/parserlabs/r4/jobs/cvb/ | Form uploaded Scheduled for API subcommittee review Dec 21, 2020 Waiting for re-uploaded API info form with PaaS API info Reviewed by API subcommittee, PaaS APIs are subset of TARS APIs Accepted | https://nexus.akraino.org/content/sites/logs/parserlabs/r4/jobs/cvb/ | Dec 1, 2020 Vuls: Accepted with exceptions shown at: Release 4 Vuls Exception Reques https://nexus.akraino.org/content/sites/logs/parserlabs/r4/jobs/cvb/ Jan 26, 2021 Lynis: Accepted with exceptions shown at: https://nexus.akraino.org/content/sites/logs/parserlabs/r4/jobs/cvb/lynis_updated_26.log Kube-Hunter: Exception granted: K8s not used by this BP. | Yes | 12/01 | ||
2 | IEC Type 4: AR/VR oriented Edge Stack for Integrated Edge Cloud (IEC) Blueprint Family @Bart Dong @thorking | scheduled at | N | Y | https://nexus.akraino.org/content/sites/logs/parserlabs/r4/jobs/iec-type4/ | Form uploaded Scheduled for API subcommittee review Dec 21, 2020 Waiting for re-uploaded API info form with PaaS API info Reviewed by API subcommittee, PaaS APIs are subset of TARS APIs Accepted | https://nexus.akraino.org/content/sites/logs/parserlabs/r4/jobs/iec-type4/ | Dec 1, 2020 Vuls: Accepted with exceptions shown at: Release 4 Vuls Exception Request https://nexus.akraino.org/content/sites/logs/tencent/MR/iec-type4/ Mar 10, 2021 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 | @Paul Carver | 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/ Dec 2, 2020 Vuls: Accepted with exceptions shown at: Release 4 Vuls Exception Request Feb 3, 2021 Lynis: Accepted with exceptions shown at: Jan 28, 2021 Kube-Hunter: Accepted with exceptions shown at: | Yes | 12/01 | ||
4 | ICN - Integrated Cloud-Native Family @Kuralamudhan Ramakrishnan (Deactivated) | 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 | @khemendra kumar | scheduled at | N | N | Form uploaded Reviewed by API subcommittee Dec 11, 2020 Accepted | vuls exceptions Akraino CVE Vulnerability Exception Request | Dec 7, 2020 Vuls: Accepted with exceptions shown at: Lynis: Accepted with exceptions shown at: Kube-Hunter: Accepted with exceptions shown at: | Yes | 12/08 | |||
6 | ELIOT SD-WAN/WAN Edge/uCPE Blueprint @khemendra kumar | scheduled at | N | N | Form uploaded Reviewed by API subcommittee Dec 11, 2020 Accepted | vuls exceptions Akraino CVE Vulnerability Exception Request | Dec 7, 2020 Vuls: Accepted with exceptions shown at: Lynis: Accepted with exceptions shown at: Kube-Hunter: Accepted with exceptions shown at: | Yes | 12/08 | |||
7 | Network Cloud and TF (Tungsten Fabric) Integration Project @Sukhdev Kapur | 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 Dec 18, 2020 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/ Jan 6, 2021 Vuls: Accepted with exceptions shown at: Feb 10, 2021 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. Feb 3, 2021 Kube-Hunter: Accepted with exceptions shown at: | Yes | 12/09 | 12/09 | |
8 | @Ricardo Noriega De Soto | 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/ | Jan 12, 2021 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: Jan 20, 2021 https://nexus.akraino.org/content/sites/logs/redhat-kni/bluval_results_pae/os/lynis/ Accepted with exceptions shown at: Kube-Hunter: Jan 20, 2021 Accepted with exceptions shown at: | Yes | 12/09 | 12/09 | |
9 | @Ricardo Noriega De Soto 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/ |
|