Skip to end of metadata
Go to start of metadata


Release 3 target date is May 30th 2020.  

  1. 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)



  1. Virtual meeting to start to have a session to discuss all of the agenda items.
  2. Different patches from different blueprints need to be up-streamed.
  3. Need a consistent framework
  4. New blueprints have been committed for R3.
  5. Want to increase standards on Release 3.
  6. Validation Project test layers and test cases
  7. Incubation Self Certification in R3?

Release 3 Requirements

  1. High Level Overall Requirements
  2. CI, Blueprint Validation Lab Sub-Committee Requirements
    1. Present Pod Topology document.
    2. Peering w/LF Jenkins - (Note: peering is an optional requirement)
    3. Push logs through Nexus. (Note: This is mandatory for Incubation self-certified and Maturity)
    4. Usage of topics for release

      1. 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).

      2. 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).

    5. 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)

  3. Security Sub-Committee Requirements, please fill in Security Scan Status.  Instructions can be found at:  Steps To Implement Security Scan Requirements
  4. Blueprint Validation Framework Feature Project Requirements See TSC meeting.
  5. 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)
  6. 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

  7. API Sub-Committee Requirements  (Note: no mandatory requirements for Incubation self-certified or Maturity)
  8. Community Sub-Committee Requirements  (Note: no mandatory requirements for Incubation self-certified or Maturity)
  9. 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)
  10. Upstream Sub-Committee Requirements (Note: no mandatory requirements for Incubation self-certified or Maturity). Here is the R3 release Upstream BP review status, 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 NameDocumentation Review StatusTSC Subgroup Release StatusIs this your first release TSC ApprovalGoing 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.

 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 

NApprovedNot 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.

Security Scan Status

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  

NTSC approvedN

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.

Security Scan Status

Kube-Hunter:  Exemption granted, this blueprint does not currently use Kubernetes.


05/28

Complete

 

  1. Please add license terms in the Installation doc or Architecture doc. 
  2. TOC is missing in a few of your Docs
  3. 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

Ready for TSC approval.NTSC approvedMature

 

Vuls, Lynis, Kube-Hunter:  Accepted - with exceptions listed in link below.

Security Scan Status

5/26

Complete

 Accepted

Ready for TSC approval.NTSC approvedNot Applicable ICN R3 Data sheetY

 

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/2906/02

Complete

 Accepted

Ready for TSC approval.NTSC approved
  • N
ELIOT R3 IOT-Gateway DatasheetY

  

Vuls, Lynis, Kube-Hunter:  Accepted - with exceptions listed in link below.

Security Scan Status

05/26

Complete

 TOC missing in Architecture, Installation and Test doc.

 Accepted


Ready for TSC approval.NTSC approvedNELIOT R3 uCPE DatasheetY

  

Vuls, Lynis, Kube-Hunter:  Accepted - with exceptions listed in link below.

Security Scan Status

05/26

Complete

Not Accepted yet

  1. TOC should be in all documents.
  2. Doc should be aligned with the template posted on Doc SC page

 Not completely addressed the above two, sent email

 Accepted

Ready for TSC approval.NTSC approvedNot Applicable


NetworkCloud-TF blueprint Datasheet.docx

Y

 

Vuls, Lynis, Kube-Hunter:  Accepted

- with exceptions listed in link below.

Security Scan Status

05/2106/02

Complete

 

  1. TOC missing in Docs - [ Yolanda -  added ]
  2. Installation Doc has missing sections, ref to the template on Doc subcommittee page - [ Yolanda: added relevant sections and restructured ]

 Accepted

Ready for TSC approval.


NTSC approvedNN [ 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.

Security Scan Status

 

Vuls:  Exemption granted, this blueprint uses RHCoreOS which vuls does not support.

05/0505/19
 ACRN  Kailasnath Maneparambil
N/A Y
 N


 

No security scan logs received for vuls, lynis or kube-hunter.



Micro-MEC

Complete

 TOC missing

 Accepted

Ready for TSC approvalYTSC approvedNAkraino R3 MicroMEC blueprint datasheet.docxN/A

 

Accepted:  First release - security scan not required.

Security Scan Status



The AI Edge: School/Education Video Security Monitoring

Hechun Zhang

Complete

Not Accepted yet

Address the review comments posted on Doc SC page

 Accepted

Ready for TSC approvalYTSC approvedNN/A

 

Vuls, Lynis, Kube-Hunter:  Accepted - with exceptions listed in link below.

Security Scan Status

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

 Accepted

Ready for TSC approvalYTSC approvedN5G MEC Rel 3 DatasheetN/A

 

Vuls, Lynis, Kube-Hunter:  Accepted - with exceptions listed in link below.

Security Scan Status

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.

YTSC approvedNIEC Release3-IEC Type3-datasheet.docxNA (First Release)

 

Vuls & Lynis:  Accepted - with exceptions listed in link below.

Accepted:  First release - Kube-Hunter security scan not required.

Security Scan Status

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 approvalYTSC approvedNNA (First Release)

 

Vuls & Lynis:  Accepted

Logs received from:

Yihui Wang, wangyihui@chinamobile.com

- with exceptions listed in link below.

Security Scan Status

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 approvalYTSC approvedN

EALTEdge Rel 3 DatasheetNA (First Release)

 

Vuls, Lynis and Kube-Hunber:  Accepted

- with exceptions listed in link below.

Test results provided by Srinivasan Selvam

Security Scan Status

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 R3YNot part of R3NPCEI Release 3 DatasheetN/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

Security Scan Status

06/0306/03


03/02~03/2020 Akraino TSC F2F & 2020 Planning meeting








  • No labels