Skip to end of metadata
Go to start of metadata


Release 2 target date is November 30th 2019.  

  1. Self Certified Milestones Achievement Due Date Oct 30th 2019


2. Maturity Review Milestone Achievement  Due date  Oct 30th 2019

Please add targeted and achieved R2 milestones at:

BP Incubation Stage Reporting R2

Define area of focus




  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 R2.
  5. Want to increase standards on Release 2.
  6. June 19th should be a topic to discuss R2 in mini summit.
  7. Validation Project test layers and test cases
  8. Incubation Self Certification in R2?

Release 2 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 for Maturity Review Approved by TSC July 11, 2019,please fill in Security Scan Status (Note this is not required for self certification, only required for maturity review)
  4. Blueprint Validation Framework Feature Project Requirements See TSC meeting and Slides (Note this is not required for self certification, only required for maturity review)
  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 Blue prints 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 R2 at Muture level BP Graduation Review Processes and Criteria)
  10. Upstream Sub-Committee Requirements (Note: no mandatory requirements for Incubation self-certified or Maturity)


Blue Prints Participating in Release 2

Internal Target date to meet Rel 2 Criteria is Oct 31st ( please add your target/achieved date at the BP Incubation Stage Reporting R2)

Project NameIs 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)

Date ready for TSC review

(Column filled in by PTLs)

 TSC Review Date

(Column filled in by TSC)

YNot Applicable

https://nexus.akraino.org/content/sites/logs/tencent/job/TestCompileCode/

https://nexus.akraino.org/content/sites/logs/tencent/job/TestConnectVehicleService/

https://nexus.akraino.org/content/sites/logs/tencent/job/CD_Install_Tars/

12/04
NN

https://nexus.akraino.org/content/sites/logs/arm-china/jenkins092/iec-type1-deploy-compass-virtual-ubuntu1604-daily-master/

https://nexus.akraino.org/content/sites/logs/arm-china/jenkins092/iec-type1-install-seba_on_arm-compass-virtual-ubuntu1604-daily-master/

https://nexus.akraino.org/content/sites/logs/arm-china/jenkins092/iec-type1-destroy-compass-virtual-ubuntu1604-daily-master/

11/26


NN

https://nexus.akraino.org/content/sites/logs/production/vex-yul-akraino-jenkins-prod-1/iec-deploy-compass-virtual-ubuntu1604-daily-master/

https://nexus.akraino.org/content/sites/logs/production/vex-yul-akraino-jenkins-prod-1/iec-install-seba_on_arm-compass-virtual-ubuntu1604-daily-master/

https://nexus.akraino.org/content/sites/logs/production/vex-yul-akraino-jenkins-prod-1/iec-destroy-compass-virtual-ubuntu1604-daily-master/

https://nexus.akraino.org/content/sites/logs/arm-china/jenkins092/iec-type2-deploy-compass-virtual-ubuntu1604-daily-master/

https://nexus.akraino.org/content/sites/logs/arm-china/jenkins092/iec-type2-install-seba_on_arm-compass-virtual-ubuntu1604-daily-master/

https://nexus.akraino.org/content/sites/logs/arm-china/jenkins092/iec-type2-destroy-compass-virtual-ubuntu1604-daily-master/

11/26
YDec. 25, 2019 (R3)



NOct 31st https://nexus.akraino.org/content/sites/logs/att/job/Install_REC_on_OpenEdge1/11/19
YNot Applicable

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

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

SEBA blueprint R2 datasheet11/19
YNot Applicable

ICN Master Baremetal Deployment Verifier

ICN Master Baremetal Deployment for Hardware verification

ICN Master Baremetal Deployment Virtlet nested K8s Verifier

ICN Master Virtual Deployment Verifer

ICN Master Virtual Deployment Virtlet nested K8s Verifier

ICN R2 Data sheet11/26

ELIOT AIoT in Smart Office Blueprint

jereliu@tencent.com

YNot Applicable



ELIOT IoT Gateway Blueprint

khemendra kumar

NN

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

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

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

https://nexus.akraino.org/content/sites/logs/huawei/blu-val/job/eliot-deploy-virtual-daily-master-validation/13/

ELIOT Release 2 - IoT Gateway Data Sheet11/21
NN

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

https://nexus.akraino.org/content/sites/logs/huawei/blu-val/job/eliot-deploy-virtual-daily-master-validation/13/

ELIOT Release 2 - uCPE Data Sheet11/21

Network Cloud Rover

David Plunkett

NN

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

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

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

Network Cloud Rover and Unicycle R2.docx


11/25

Network Cloud Unicycle with SR-IOV

David Plunkett

NNhttps://nexus.akraino.org/content/sites/logs/att/job/MT_nightly_master_G_unicycle_dell/229/Network Cloud Rover and Unicycle R2.docx11/25

 Network Cloud Unicycle with OVS-DPDK

Jeff Collins

NNhttps://nexus.akraino.org/content/sites/logs/ericsson/job/RC+Unicycle_OVS_DPDK_Deployment/22/Network Cloud Unicycle OVS-DPDK R2.docx11/25
YNot Applicable https://nexus.akraino.org/content/sites/logs/juniper/job/NC-Tungsten_Fabric/27/logs/airship-in-a-bottle.output.log

NetworkCloud-TF blueprint Datasheet.docx

11/1511/15

AI/ML and AR/VR applications at Edge

Vikram Siwach

YNot Applicable



KNI Provider access edge

Yolanda Robla Mota

NNhttps://nexus.akraino.org/content/sites/logs/redhat-kni/192.168.112.199/kni-deploy-baremetal/7/
https://nexus.akraino.org/content/sites/logs/sandbox/vex-yul-akraino-jenkins-sandbox-1/kni-blueprint-basic-3-masters-verify-deploy-baremetal/33/
https://nexus.akraino.org/content/sites/logs/production/vex-yul-akraino-jenkins-prod-1/kni-blueprint-pae-verify-deploy-aws/55/
https://nexus.akraino.org/content/sites/logs/redhat-kni/kni-edge-installer-libvirt/45/

https://wiki.akraino.org/download/attachments/20317140/Akraino%20R2%20blueprint%20Datasheet_%20KNI.pdf11/1511/22
 ACRN  Kailasnath Maneparambil Y N



Rel2_milestones.pptx (self certified)


06/17-19/2019 Technical Mini-Summit

Day 3, Wednesday,  

Room: Fantasy Island

Time

Topics, Zoom Link

10:45 am - 12:00 pm

Akraino Release 2.0 Planning

10:45-11:15 - CI Sub-committee R2 inputs, goals, & Planning - Cesar Berho

 Presentation


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 

1:00 pm - 3:30 pm

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

Upstream Dependency Matrix and Upstream Project Information needs to be updated at SEBA OS and ONAP different features.


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)


3:00 -3:30 - Process Sub-committee R2 inputs, goals & Planning - Andrew Wilkinson
















  • No labels