Release 3 Planning
Release 3 target date is May 30th 2020.
Self Certified Milestones Achievement Due Date Apr 30th 2020 ( Milestone 4)
2. Maturity Review Milestone Achievement Due date Apr 30th 2020
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
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 Security Scan 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 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). Here is the R3 release Upstream BP review status, R4 Release Upstream Compliance
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 | TSC Subgroup Release Status | Is this your first release | TSC Approval | 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 | Date ready for TSC review (Column filled in by PTLs) | TSC Review Date (Column filled in by TSC) | |
|---|---|---|---|---|---|---|---|---|---|---|---|
Yong Yang @thorking | Bluval validation missing. Rest of the Doc is accepted May 31, 20201. Needs to specify what Bluval layer tests executed 2. Inst doc needs Lic details. @thorking please add this. Jun 23, 2020 1. ToC is missing in all doc. 2. Installation doc still has a lot of important sections missing. Note: I have reviewed this BP, multiple times. Please follow the templates on the Doc Subcommittee page. Not ready Jun 25, 2020 Accepted
| Jun 16, 2020 Tina to setup follow up with Randy and Tapio. Expect to close by Jun 19, 2020 | N | Approved | Not Applicable | CentOS 8 is not supported in BluVal at the moment. Test has been run manually. And the results are in the Nexus. Jun 24, 2020 | Jun 24, 2020 Vuls, Lynis: Accepted - with exceptions listed in link below. Kube-Hunter: Exemption granted, this blueprint does not currently use Kubernetes. | 05/28 |
| ||
IEC Type 4: AR/VR oriented Edge Stack for Integrated Edge Cloud (IEC) Blueprint Family @Bart Dong @thorking | Bluval validation missing in Test Doc. Rest of the Doc is accepted May 31, 2020 Same status as Connected Vehicle. Jun 23, 2020 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 Jun 25, 2020 Accepted | Jun 16, 2020 Tina to setup follow up with Randy and Tapio. Expect to close by Jun 19, 2020 | N | TSC approved | N | https://nexus.akraino.org/content/sites/logs/ampere/iec-type4/logs/ | CentOS 8 is not supported in BluVal at the moment. Test has been run manually. And the results are in the Nexus. Jun 24, 2020
| Jun 24, 2020 Vuls, Lynis: Accepted - with exceptions listed in link below. Kube-Hunter: Exemption granted, this blueprint does not currently use Kubernetes.
| 05/28 |
| |
@Paul Carver | Complete May 31, 2020
Not Accepted yet Jun 16, 2020 Accepted | Ready for TSC approval. | N | TSC approved | Mature |
| Jun 4, 2020 Vuls, Lynis, Kube-Hunter: Accepted - with exceptions listed in link below. | 5/26 |
| ||
ICN - Integrated Cloud-Native Family @Kuralamudhan Ramakrishnan (Deactivated) | Complete May 31, 2020 Accepted | Ready for TSC approval. | N | TSC approved | Not Applicable | Y | Jun 4, 2020 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 | ||
@khemendra kumar | Complete Jun 5, 2020 Accepted | Ready for TSC approval. | N | TSC approved |
| Y | Jun 4, 2020 Vuls, Lynis, Kube-Hunter: Accepted - with exceptions listed in link below. | 05/26 |
| ||
ELIOT SD-WAN/WAN Edge/uCPE Blueprint @khemendra kumar | Complete Jun 6, 2020 TOC missing in Architecture, Installation and Test doc. Jun 8, 2020 Accepted
| Ready for TSC approval. | N | TSC approved | N | Y | Jun 4, 2020 Vuls, Lynis, Kube-Hunter: Accepted - with exceptions listed in link below. | 05/26 |
| ||
Network Cloud and TF Integration Project @Sukhdev Kapur | Complete Not Accepted yet
Jun 6, 2020 Not completely addressed the above two, sent email Jun 15, 2020 Accepted | Ready for TSC approval. | N | TSC approved | Not Applicable |
| Y | Jun 15, 2020 Vuls, Lynis, Kube-Hunter: Accepted - with exceptions listed in link below. | 05/21 | 06/02 | |
@Yolanda Robla Mota (Deactivated) | Complete Jun 6, 2020
Jun 18, 2020 Accepted | Ready for TSC approval.
| N | TSC approved | N | 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 ] | Jun 4, 2020 Lynis & Kube-Hunter: Accepted - with exceptions listed in link below. Jun 11, 2020 Vuls: Exemption granted, this blueprint uses RHCoreOS which vuls does not support. | 05/05 | 05/19 | ||
ACRN @kailasnath.s.maneparambil@intel.com |
| N/A | Y |
| N |
|
|
| Jun 8, 2020 No security scan logs received for vuls, lynis or kube-hunter. |
|
|
Complete Jun 6, 2020 TOC missing Jun 16, 2020 Accepted | Ready for TSC approval | Y | TSC approved | N | N/A | Jun 16, 2020 Accepted: First release - security scan not required. |
|
| |||
The AI Edge: School/Education Video Security Monitoring @Hechun Zhang | Complete Not Accepted yet Address the review comments posted on Doc SC page Jun 15, 2020 Accepted | Ready for TSC approval | Y | TSC approved | N | N/A | Jun 5, 2020 Vuls, Lynis, Kube-Hunter: Accepted - with exceptions listed in link below. | 06/02 |
| ||
5G MEC/Slice System to Support Cloud Gaming, HD Video and Live Broadcasting Blueprint @Feng Yang | Complete Look at the Documentation Template. A number of key elements missing in: Inst Doc: Uninstall, Dev Guide and Troubleshooting Test: Test Env setup Jun 11, 2020 Accepted | Ready for TSC approval | Y | TSC approved | N | N/A | Jun 4, 2020 Vuls, Lynis, Kube-Hunter: Accepted - with exceptions listed in link below. Incubation BP | 06/03 |
| ||
@hanyu ding | Complete Jun 4, 2020 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 Jun 21, 2020 Accpeted | Jun 16, 2020 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. |