...
- Self Certified Milestones Achievement Due Date Apr 30th 2020
...
- ( Milestone 4)
| View file | ||||
|---|---|---|---|---|
|
2. Maturity Review Milestone Achievement Due date Apr 30th 2020
(figure to be updated)
| View file | ||||
|---|---|---|---|---|
|
...
- 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 , please fill in Security Scan Status (Note this is not required for self certification, only required for maturity review). Instructions can be found at: Steps To Implement Security Scan Requirements
- 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 R2 R3 at Muture level 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) |
|---|
Date ready for TSC review
(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) |
|---|---|---|---|
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/
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. 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 Accepted | Tina to setup follow up with Randy and Tapio. Expect to close by | 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.
|
Vuls, Lynis: Accepted - with exceptions listed in link below. Kube-Hunter: Exemption granted, this blueprint does not currently use Kubernetes. | 05/28 | ||||
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 | N | TSC approved | N |
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. | 05/28 | |||
Complete
Not Accepted yet Accepted | Ready for TSC approval. | N | TSC approved | Mature |
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/
| 5/26 | |||||||||||
Complete Accepted | Ready for TSC approval. | N | TSC approved | Not Applicable | 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 | Ready for TSC approval. | N | TSC approved |
|
| ELIOT R3 IOT-Gateway Datasheet | Y | 05/26 | |||
Complete TOC missing in Architecture, Installation and Test doc. Accepted | Ready for TSC approval. | N | TSC approved | N |
| ELIOT R3 uCPE Datasheet | Y | 05/26 | |||
Complete Not Accepted yet
Not completely addressed the above two, sent email Accepted | Ready for TSC approval. | N | TSC approved | Not Applicable |
ICN Master Baremetal Deployment Verifier
ICN Master Baremetal Deployment for Hardware verification
ICN Master Baremetal Deployment Virtlet nested K8s Verifier
| Y | 05/21 | 06/02 | ||||
Complete
Accepted | Ready for TSC approval. | N | TSC approved | N |
Network Cloud Rover
| 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: Exemption granted, this blueprint uses RHCoreOS which vuls does not support. | 05/05 | 05/19 | ||||||||
| ACRN Kailasnath Maneparambil | N/A | Y | N |
No security scan logs received for vuls, lynis or kube-hunter. | |||||||
Complete TOC missing Accepted | Ready for TSC approval | Y | TSC approved | N |
Network Cloud Rover and Unicycle R2.docx
Network Cloud Unicycle with SR-IOV
Network Cloud Unicycle with OVS-DPDK
| Akraino R3 MicroMEC blueprint datasheet.docx | N/A | ||||
Complete Not Accepted yet Address the review comments posted on Doc SC page Accepted | Ready for TSC approval | Y | TSC approved | N |
| N/ |
| A | 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 Accepted | Ready for TSC approval | Y | TSC approved | N |
| 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 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. | Y | TSC approved | N | IEC Release3-IEC Type3-datasheet.docx | NA (First Release) |
Vuls & Lynis: Accepted - with exceptions listed in link below. Accepted: First release - Kube-Hunter security scan not required. | 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 Accepted | Ready for TSC approval | Y | TSC approved | N |
https://nexus.akraino.org/content/sites/logs/redhat-kni/kni-edge-installer-libvirt/45
Rel2_milestones.pptx (self certified)
03/02~03/2020 Akraino TSC F2F & 2020 Planning meeting
(To be updated)
Day 3, Wednesday,
Room: Fantasy Island
...
Time
...
Topics, Zoom Link
...
| NA (First Release) |
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. | 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 | Ready for TSC approval | Y | TSC approved | N | EALTEdge Rel 3 Datasheet | NA (First Release) |
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. | 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 | Not part of R3 | Y | Not part of R3 | N | PCEI Release 3 Datasheet | N/A |
Vuls, Lynis - Accepted Kube-Hunter - Kubernetes not being used at this time - with exceptions listed in link below. Test results provided by Jian Li | 06/03 | 06/03 |
03/02~03/2020 Akraino TSC F2F & 2020 Planning meeting
Akraino Release 2.0 Planning
10:45-11:15 - CI Sub-committee R2 inputs, goals, & Planning - Cesar Berho
11:15- 11:45 - Community Sub-committee R2 inputs, goals & Planning - Tapio Tallgren
Going forward, we had the idea to present all the Release 1 projects in the community call and record the presentations. This way we would have documentation about the status of all of the projects available. All of the Release 1 projects are listed below and also on the page https://wiki.akraino.org/display/AK/Technical+Community.
I would appreciate if the PTLs would sign up on that page, otherwise I will have to find volunteers. Suggest we start the process on July 11th.
11:45- 12:15 - TSC Goals for R2 - Kandan Kathirvel & Tina Tsou
| View file | ||||
|---|---|---|---|---|
|
...
Akraino Release 2.0 Planning
1:00-1:30 - Security Sub-committee R2 inputs, goals & Planning - Ken Yi
1:30-2:00 - Documentation Sub-committee R2 Inputs, goals & Planning - sujata tibrewala
2:00-2:30 - Upstream Sub-committee R2 inputs, goals & Planning -Wenjing Chu
2:30-3:00 - API Sub-committee R2 inputs, goals & Planning -Vikram Siwach
Akraino BP API Standards
a)Community whitepaper ( AI: API SC)
b)Explore possibility of actionable plan with O-RAN, ETSI MEC, LF Edge projects, etc.,
Do a joint press release to publicly annonce plans ( AI: API/Community/TSC Chair/Co-Chair/Marketing subcommittee)
...