Skip to end of metadata
Go to start of metadata


Release 4 target date is November 30th 2020.  

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



  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 R4.
  5. Want to increase standards on Release 4.
  6. Validation Project test layers and test cases
  7. Self Certification in R4?

Release 4 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 Release 4 Blueprint Scanning 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: See this link for requirements: Blueprint Projects R4 API Reporting Requirements)
  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 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 NameTSC Subgroup Release StatusIs 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)

API Info Reporting Info Review

(Column filled in by API Subcommittee)

(note for PTLs – go here for steps to fill in project API info template)

BluVal

Certification

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://wiki.akraino.org/display/AK/Akraino+CVE+Vulnerability+Exception+Request

Upstream Review (Column filled by Upstream Subcommittee and PTLs)


(note PTL can go to Release Upstream Compliance to find details)

Date ready for TSC review

(Column filled in by PTLs)

 TSC Review Date

(Column filled in by TSC)

1scheduled at 

TSC 2020-12-01 (Tues) 7 am Pacific

NY

https://nexus.akraino.org/content/sites/logs/parserlabs/r4/jobs/cvb/


https://nexus.akraino.org/content/sites/logs/parserlabs/r4/jobs/cvb/

 

Vuls:  Failed - errors sent to BP owner

 

Lynis:  Failed - errors sent to BP owner

Kube-Hunter:  Exception granted:  K8s not used by this BP.

Yes12/01
2scheduled at 

TSC 2020-12-01 (Tues) 7 am Pacific

NY

https://nexus.akraino.org/content/sites/logs/parserlabs/r4/jobs/iec-type4/


https://nexus.akraino.org/content/sites/logs/parserlabs/r4/jobs/iec-type4/

 

Vuls:  Failed - errors sent to BP owner

 

Lynis:  Failed - errors sent to BP owner

Kube-Hunter:  Exception granted:  K8s not used by this BP.

Yes12/01
3Scheduled at Release 4 Review 2020-12-01 (Tues) 7 am PacificNMature

https://nexus.akraino.org/content/sites/logs/att/job/Install_REC_on_OpenEdge1/

https://logs.akraino.org/production/vex-yul-akraino-jenkins-prod-1/rec-aarch64_baremetal-install-rec-weekly-master/

Received.

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-11-27-2020.tar

 

Vuls:  Accepted with exceptions show at:

Release 4 Vuls Exception Request

 

Lynis:  Failed - errors sent to BP owner

Kube-Hunter: Does not appear to have run correctly - question sent to BP owner




4Scheduled at 

Release 4 Review 2020-12-16 (Wed) 7 am Pacific

NN



Receivedhttps://logs.akraino.org/intel/bluval_results/icn/master/20201116-231827/results/(work in progress - not for review yet)



12/0412/09
5scheduled at 

TSC 2020-12-08 (Tues) 7 am Pacific

NN

https://nexus.akraino.org/content/sites/logs/huawei/blueprints/iotgateway/job/eliot-iotgateway-deploy-k8s-virtual-daily-master/649/






Akraino CVE Vulnerability Exception Request



12/01
6scheduled at 

TSC 2020-12-08 (Tues) 7 am Pacific

NNhttps://nexus.akraino.org/content/sites/logs/huawei/blueprints/uCPE/job/eliot-uCPE-deploy-k8s-centos-virtual-daily-master/534/

https://nexus.akraino.org/content/sites/logs/huawei/blueprints/uCPE/job/eliot-uCPE-deploy-k8s-centos-virtual-daily-master/535/results/

Akraino CVE Vulnerability Exception Request


Yes12/01
7
NNot Applicable

https://nexus.akraino.org/content/sites/logs/juniper/job/NC-Tungsten_Fabric/40/



NetworkCloud-TF blueprint Datasheet.docx


Y
12/0912/09
8Scheduled at 

TSC 2020-12-17 (Thurs) 7 am Pacific

NN

AWS footprint:
https://logs.akraino.org/production/vex-yul-akraino-jenkins-prod-1/kni-blueprint-pae-verify-deploy-aws/81/

GCP footprint:

https://logs.akraino.org/production/vex-yul-akraino-jenkins-prod-1/kni-blueprint-pae-verify-deploy-gcp/51/


ReceivedN [ 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 ]



12/0912/09
9Scheduled at 

TSC 2020-12-17 (Thurs) 7 am Pacific

YN

Mgmt Hub logs:

https://logs.akraino.org/production/vex-yul-akraino-jenkins-prod-1/kni-blueprint-management-hub-verify-deploy-gcp/9/

IE logs:

https://logs.akraino.org/production/vex-yul-akraino-jenkins-prod-1/kni-blueprint-ie-verify-deploy-gcp/2/


Received




10

Micro-MEC


YNhttps://nexus.akraino.org/content/sites/logs/micromecAkraino R3 MicroMEC blueprint datasheet.docxReceivedN/A





11

Scheduled at TSC 2020-11-24 (Tues) 7 am Pacific

NY

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



06/02
12

The AI Edge: Intelligent Vehicle-Infrastructure Cooperation System(I-VICS) Hechun Zhang


YN







13

5G MEC/Slice System to Support Cloud Gaming, HD Video and Live Broadcasting Blueprint

Feng Yang


YN

https://nexus.akraino.org/content/sites/logs/tencent/job/5g-mec-cloud-gaming-CD/15/

https://logs.akraino.org/production/vex-yul-akraino-jenkins-prod-1/5g-mec-cloud-gaming-master-verify/

5G MEC Rel 3 DatasheetReceivedN/A



06/03
14
NNhttps://nexus.akraino.org/content/sites/logs/ampere/job/akraino_arm_anbox_test/6/

NA (First Release)





15Scheduled at 

TSC 2020-12-10 (Thurs) 7 am Pacific

NN

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)



06/04
16scheduled at 

TSC 2020-12-10(Thurs) 7 am Pacific

NN
https://nexus.akraino.org/content/sites/logs/huawei/
blueprints/ealt-edge/job/ealt-edge-deploy-virtual-daily-master/374/

Received;

Accepted

https://nexus.akraino.org/content/sites/logs/huawei/blueprints/ealt-edge/job/ealt-edge-bluval-daily-master/219/results/


https://nexus.akraino.org/content/sites/logs/huawei/blueprints/ealt-edge/job/ealt-edge-bluval-daily-master/219/results/

Akraino CVE Vulnerability Exception Request

Yes12/02
17
Y
https://nexus.akraino.org/content/sites/logs/cmti/job/pcei-daily/PCEI Release 3 Datasheet
N/A



11/19
18Scheduled at 

TSC 2020-12-08 (Tues) 7 am Pacific

YNhttps://nexus.akraino.org/content/sites/logs/webank/job/

Received

Accepted

N/Ahttps://nexus.akraino.org/content/sites/logs/webank/job/FL_SCAN/results/
12/08
19Scheduled at Release 4 Review 2020-11-17 (Tue) 7 am PacificYNhttps://nexus.akraino.org/content/sites/logs/futurewei/kubeedgees/

Received;

Accepted.

Yes

https://nexus.akraino.org/content/sites/logs/futurewei/kubeedgees/58/results/

Akraino BluVal Exception Request

 

Vuls:  Accepted with exceptions show at:

Release 4 Vuls Exception Request

 

Lynis:  Accepted

Kube-Hunter: Exception granted:  KubeEdge node is not on same subnet as the cloud node.  Communication occurs through the websocket endpoint, so kube-hunter can't be used.

Yes11/17
20
Y








21Scheduled at Release 4 Review 2020-12-09 YN
Received


12/09



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








  • No labels