Versions Compared

Old Version 21

changes.mady.by.user Andrew Wilkinson

Saved on

compared with

New Version Current

changes.mady.by.user Tapio Tallgren

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Please go to R2 page for  Rel 2 BP incubation Stage Milestone Reporting

PTL TSC Presentation Criteria

1) Is a validation lab in place?

2) Has a code repository been established?

3) Have regular meetings been scheduled?

4) Has a backlog been established?

5) Have any issues been identified that require support from the TSC?


Incubation stage reporting

 MBI = Milestone Bp Incubation

...

Note: Reporting of 'Achieved dates' are mandatory (if not optional milestones). The advance publishing of Target dates is optional.



Project Name

MBI0

Project

inducted to 'Incubation' by TSC

Induction


MBI1

First regular community call held

Kick Off

MBI2

Planning

complete

Identify integration/developers team & testing team

Identify whether LF CD or external validation lab to be used for first validation.

MBI3

Integration Test plan created and shared with the community

Requirement/Feature Freeze (if applicable)

MBI4

Additional test scripts development and Set up accessible

Lab is set up for CD

process defined


MBI3

CD Test Scripts developed

1st Validation Lab is Set up


MBI4

First Full CD deployment

BP is ready to download and deployable by users as self certified

MBI5

Code Freeze (if applicable)

Additional test case development complete

MBI6

First deployment in validation lab

First test report logs shipped to LF CI servers

Ad hoc reporting

CI/CD based testing

MBI7

Second community validation lab identified

MBI8

and bug fixing


MBI5

Second community validation lab fully setup

MBI9

BP successfully deployed in second community validation lab

 MBI10

Critical issues fixed.

Documentation complete for other community member(s) to deploy identical validation lab

MBI6

Ready for Maturity Review

Maturity Graduation Review as per BP Graduation Review Processes and Criteria

Graduation Review by TSC

(Request for graduation review made by PTL

)(Decision of graduation made TSC

)


TSC's Graduation review can have one of two outcomes:

  1. Project remains at 'Incubation' (i.e. the request to graduate wasn't approved by the TSC)
  2. Project graduates from 'Incubation' to 'Mature' (i.e. the request to graduate was approved by the TSC)
1

SDN Enabled Broadband Access (SEBA) for

Network Cloud

Telco Appliance Blueprint Family

Aaron Byrd

12/7/2019

Target date
 
Feb 2, 2019April 22, 2019May 30, 2019Jun 30, 2019



Achieved date
 
Feb 2, 2019






2

Serverless Blueprint Proposal for Addition to Network Cloud Blueprint Family

Itamar Eshet

12/7/2019

Target date
 








Achieved date
 








3

Unicycle

Blueprint Proposal for Addition to Network Cloud Blueprint Family

with SR-IOV Project

David Plunkett

12/7/2019

Target date
 








Achieved date
 
Feb 11, 2019Apr 29, 2019Aug 22, 2018Aug 22, 2018Feb 11, 2019


4

Rover Blueprint Proposal for Addition to Network Cloud Blueprint Family

David Plunkett

12/7/2019

Target date
 








Achieved date
 
Feb 11, 2019Apr 29, 2019Aug 22, 2018Aug 22, 2018Feb 11, 2019


5

OVS-DPDK Unicycle Dell Blueprint Proposal

Rakesh Bohra

12/7/2019

Target date
 
Feb 8,2019March 13,2019May 3, 2019May 30, 2019



Achieved dateFeb 8,2019March 13,2019April 29, 2019May 26, 2019
Achieved date 




6

NC-TF-BluePrint-ProposalAkraino Network Cloud and TF Integration

Sukhdev Kapur

12/7/2019

Target date
 








Achieved date
 








7

Edge Video Processing

Adnan Saleem

12/7/2019


Target date
 
Mar 23, 2019Mar 29, 2019Apr 22, 2019May 30, 2019May 31, 2019


Achieved date
 
Mar 23, 2019Mar 29, 2019





8

ELIOT IoT Gateway Blueprint

khemendra kumar

12/7/2019Target date
 
Feb 27, 2019Apr 30, 2019May 10, 2019May 30, 2019



Achieved date
 








9

ELIOT SD-WAN/WAN Edge/uCPE Blueprint

khemendra kumar

12/7/2019Target date
 
Feb 27, 2019Apr 30, 2019May 10, 2019May 30, 2019



Achieved date
 








10

IEC Type 1 for Integrated Edge Cloud (IEC) Blueprint Family

Trevor Tao

12/7/2019Target date
 
Jan 28, 2019 Feb 05, 2019Apr 15, 2019May 30, 2019Jun 30, 2019


Achieved date
 
Jan 28, 2019 Feb 05, 2019Apr 2, 2019

May 21, 2019

IEC Release 1 Documentation





11

IEC Type 2 for Integrated Edge Cloud (IEC) Blueprint Family

xinhuili

12/7/2019Target date
 
Jan 28, 2019 Feb 05, 2019Apr 15, 2019May 30, 2019Jun 30, 2019


Achieved dateJan 28, 2019 Feb 05, 2019

Apr 2, 2019

https://jenkins.akraino.org/view/iec/

May 21, 2019

IEC Release 1 Documentation

Achieved date 





12

Industrial Edge (IE) Blueprint

Yolanda Robla Mota

12/7/2019Target date
 
Feb 11,
2019		Apr 30,
2019		May 5, 2019
https://jenkins.akraino.org/view/kni/		Jun 30, 2019Jun 30, 2019


Achieved date
 
Feb 11,
2019		Apr 30,
2019		May 3, 2019




13

Provider Access Edge (PAE) Blueprint

Yolanda Robla Mota

12/7/2019Target date
 
Feb 11,
2019		Apr 30,
2019		May 5, 2019
https://jenkins.akraino.org/view/kni/		May 30, 2019Jun 30, 2019


Achieved date
 
Feb 11,
2019		Apr 30,
2019		May 3, 2019May 27, 2019



14

Radio Edge Cloud

Paul Carver

12/7/2019Target date
 
2019-03-122019-05-202019-05-152019-05-30
2019-05-102019-05-30
Achieved date
 
2019-03-122019-05-282019-05-282019-05-28



15

StarlingX Far Edge Distributed Cloud

Bill Zvonar

12/7/2019Target date
 
2019-03-042019-05-032019-05-282019-05-28



Achieved date2019-03-042019-05-032019-06-042019-06-04
Achieved date 




16

Time-Critical Edge Compute

Shane Dewing

12/7/2019Target date
 








Achieved date
 








17

Micro-MEC

Tapio Tallgren


Target date








Achieved date
 Achieved date








18

Connected Vehicle Blueprint

xin qiu

12/4/2019Target date

April 12,

2019

June 12,

2019

Sep 12, 2019

Oct 12,2019





Achieved date







19

IEC Type 4 for Integrated Edge Cloud (IEC) Blueprint Family

Wenhui Zhang

 4/25/2019

Target dateMay 10, 2019June 6, 2019August 12, 2019October 12, 2019November, 12 2019TBDTBD
Achieved dateMay 10, 2019






20

AI/ML and AR/VR applications at Edge

Vikram Siwach











21

Integrated Cloud Native NFV/App stack family (Short term: ICN)

Kuralamudhan Ramakrishnan

 












CHECK AND UPDATE TABLE BELOW ONCE MBIs AGREED

...

Integration Test plan created and shared with the community

Requirement/ Feature Freeze (if applicable)

MBI3 is dependent on MBI1

  • Requirement/Feature freeze if there is code contribution as part of the blueprint or the upstream (All features are identified and JIRA stories created)
  • Comprehensive test plan documentation is created
  • Document the lab setup required and identify the external and/or LF CD lab that would be used to test this blueprint. If the lab is third party lab, get the lab reserved.
  • Security:<TBF>

MBI

Name

Description/Checklist

MBI0Project InductionBlue Print Kick Offis voted by TSC as an Akraino Blueprint. The project is defined and approved by TSC vote to enter incubation stage (Incubation Review)
MBI1Kick Off First  First regular community call held Recurring , Recurring meeting should have been setup and details appear in the BP community meeting calendar: https://lists.akraino.org/g/blueprints/calendar. The first meeting date would be the timestamp for the 'Achieved date'.
MBI2

Planning completeCD lab identifiedProcess Defined

  • MBI2 is dependent on MBI1
  • Identify integration/developers team & testing team
  • Identify whether LF CD or external validation lab is to be used for first validationProjects that have successfully completed MBI1, must complete their planning, including scenario or deliverable definition.
  • hardware set up definition frozen and clearly and fully published to the community such that any community member can replicate
  • Identify team working on features & testingIdenitify where the BP CD will occur for the first validation (KLF CD lab or community owned 'external' validation lab)
  • Peer Jenkins Set up in case of external validation lab (CI, Blueprint Validation Lab, documentation sub-committee
MBI3

Additional Test scripts development

CD lab is setup

  • All  additional test cases beyond those defined as mandatory for each layer being deployed by the BP are automated if possible and made available in blueprint repos.
  • If LF lab is used for CD
    • The set up is complete and is accessible
    • Instructions to access the setup
MBI4

Test scripts development

LF lab for CD setup and accessible if using LF lab for CD

External validation lab is set up for CD if using external lab

  • Make scripts available to create setups in third party labs.
  • Make the setups accessible for everybody if LF lab is used for CD
  • Instructions to access the setup if CD is bwing performed in the LF CD labs
    • including the method to reserve/un-reserve
    setups in the LF CD lab.
    • hardware are available.
  • If member validation lab is being used for CD
    • All HW required to deploy the BP has been installed and is ready to start CD of actual BP
    (either in the LF CD or a community validation lab)
  • Peer Jenkins Set up in case of external validation lab (CI, Blueprint Validation Lab sub-committee
  • Security: <TBF>
MBI5

Code Freeze (if applicable)

Additional test case development complete

  • Integration complete of all SW packages that are part of the blueprint (In case of CI this waterfall approach is optional)
  • All  additional test cases beyond those defined as mandatory for each layer being deployed by the BP are automated if possible and made available in blueprint repos.
  • Make the images available in public repository (Nexus?) and create scripts necessary to install all SW packages in various sites as identified by blueprint (In case of CI this waterfall approach is optional)
MBI4

First Full CD deployment

  • All requirements up till MBI4 
MBI6

First deployment in validation lab

First testing logs shipped

  • All requirements uptil MB4  should be complete at this stage
  • First full CD deployment either in the Member CD lab or the LF lab
  • 1st run of test cases and rest results logs automatically posted to LF CI servers  
  • All test cases planned for the release have been executed (In case of CI / CD this waterfall approach is optional)
  • Failures and other issues have been documented
 Ad hoc reporting

 On going CI/CD

Not really a milestone but an on going reporting period

Ad hoc reporting milestone is dependent on MBI6

Unlike the other milestones this milestone is a continuous one that spans from the start of testing (MBI6) as long as required by the CI/CD process until the BP is ready for the Maturing review by the TSC.

  • All test cases and rest results logs automatically posted to LF CI servers  
 MBI7 MBI5 Second community validation lab identifiedlab fully setup
  • Second community validation lab is identified and set up
  • This is non sequential and not dependent on any other MBI

Part of the graduation requirements from incubation to mature require deployment in at least 2 community labs

 MBI8 Second community validation lab fully setup
  •  Peer Jenkins, BP HW and all necessary components setup ready to start testing of BP
 MBI9 MBI6 BP successfully deployed in second community validation lab

 All test cases planned for the release have been executed .

Deployment in second lab may result in CI/CD iterations of the BP depending on results/experiences with the second setup.

MBI10

CI/CD based testing completed in all target validation labs

Critical issues fixed.

Documentation complete (for third parties to recreate setup and run the tests)

MBI10 is dependent on MBI6 and MBI9

  • Complete the documentation
  • Critical issues fixed
Maturity Graduation reviewTSC conducts graduation review as per criteria set out in Akraino Project Reviews Remove This Page 2

Request for graduation review made by PTL

Decision of graduation made TSC

TSC's Maturity Graduation review can have one of two outcomes:

  1. Project remains at 'Incubation' (i.e. the request to graduate wasn't approved by the TSC)
  2. Project graduates from 'Incubation' to 'Mature' (i.e. the request to graduate was approved by the TSC)
BP either graduates to the mature stage or remains in the incubation stage