Akraino project reporting provides visibility of the each BP validation project (MBx1, MBx2 etc) and feature project (MF1, MF2 etc) by means of a set of defined milestones.
The milestones are defined by the Documentation subcommittee.
BP validation projects milestones will be different in the 'Incubation' and 'Mature' stages since the graduation criteria from these two stages are different.
A single table shall be maintained for all projects in Incubation (i.e. tracking the progress towards graduating from Incubation to Mature)
A single table shall be maintained for all project in Mature stage (i.e. tracking the progress towards graduating Mature to Core)
Each BP validation project's PTL is responsibility for updating the Incubation or Mature BP tracking tables for their BP validation project so that the TSC can easily track all BP validation projects' status.
Each feature project's PTL is responsibility for updating tracking tables for their feature project so that the TSC can easily track all feature projects' status.
Blueprint Validation Project reporting
Incubation stage reporting
MBI = Milestone Bp Incubation
1) Entry Criteria: MBI0The project is approved to enter the 'Incubation' stage after TSC review and approval (Akraino Project Reviews)
2) All milestones below may not apply to all projects and hence some may be marked optional after approval from TSC
3) Details of the Blue Print Milestones are in table below at the bottom of the page
4) There are sequential milestones (S) and non sequential milestones (NS). The non sequential milestones are guidelines to be completed at a certain stage, however they are not gating factors to enter the next stage. However the NS milestones also need to be completed at some point which will be marked as part of the relevant stage.
The graduation reviews are done by assessing the projects
Project Name | MBI0 Kick-Off (Project inducted to 'Incubation' by TSC) | MBI1 Planning complete Identify integration/developers team & testing team | MBI2 Integration Test plan created and shared with the community Requirement/Feature Freeze (if applicable) | MBI3 Scripts development and Set up accessible Lab is set up for CD | MBI4 Code Freeze (if applicable) Additional test case development complete ( | MBI5 First deployment in validation lab First test report logs shipped to LF CI servers | Ad hoc reporting CI/CD based testing Critical issues fixed. Documentation complete (for third parties to recreate setup and run the tests) | MBI6 Second community validation lab identified | MBI7 Second community validation lab fully setup | MBI8 BP successfully deployed in second community validation lab | 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 | SDN Enabled Broadband Access (SEBA) for Network Cloud Blueprint Family | x | ||||||||||
| 2 | Serverless Blueprint Proposal for Addition to Network Cloud Blueprint Family | x | ||||||||||
| 3 | x | |||||||||||
| 4 | x | |||||||||||
| 5 | OVS-DPDK Unicycle Dell Blueprint Proposal | x | ||||||||||
| 6 | x | |||||||||||
| 7 | Edge Video Processing | x | ||||||||||
| 8 | x | |||||||||||
| 9 | x | |||||||||||
| 10 | x | |||||||||||
| 11 | IEC Type 2 for Integrated Edge Cloud (IEC) Blueprint Family | x | ||||||||||
| 12 | x | |||||||||||
| 13 | x | |||||||||||
| 14 | x | |||||||||||
| 15 | x | |||||||||||
| 16 | x | |||||||||||
| 17 |
CHECK AND UPDATE TABLE BELOW ONCE MBIs AGREED
MBI | Name | Description/Checklist |
|---|---|---|
| MBI0 | Blue Print Kick Off | The project is defined and approved to enter incubation stage (Incubation Review) |
| MBI1 | Planning complete |
|
| MBI2 | Integration Test plan created and shared with the community Requirement/ Feature Freeze (if applicable) |
|
| MBI3 | Scripts development and Set up accessible |
|
| MBI4 | Code Freeze (if applicable) Test case development complete |
|
| MBI5 | first deployment in validation lab first testing logs shipped |
|
| MBI6 | CI/CD based testing Critical issues fixed. Documentation complete (for third parties to recreate setup and run the tests) |
|
| Sign-Off | Release | Project graduate to Mature stage |
Mature stage reporting
MBM = Milestone Bp Mature
1) Entry Criteria: MBM0 The project is graduated by the TSC from Incubation to Mature after TSC review and approval (Akraino Project Reviews)
Project Name | MBM0 Kick-Off (Project graduated from 'Incubation' to 'Mature' by TSC) | MBM1 | ...... | Ad hoc reporting | ..... | 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 | SDN Enabled Broadband Access (SEBA) for Network Cloud Blueprint Family | ||||||
| 2 | Serverless Blueprint Proposal for Addition to Network Cloud Blueprint Family | ||||||
| 3 | |||||||
| 4 | |||||||
| 5 | OVS-DPDK Unicycle Dell Blueprint Proposal | ||||||
| 6 | |||||||
| 7 | Edge Video Processing | ||||||
| 8 | |||||||
| 9 | |||||||
| 10 | |||||||
| 11 | IEC Type 2 for Integrated Edge Cloud (IEC) Blueprint Family | ||||||
| 12 | |||||||
| 13 | |||||||
| 14 | |||||||
| 15 | |||||||
| 16 | |||||||
| 17 |
Core stage reporting
MBC = Milestone Bp Core
1) Entry Criteria: The project is graduated by the TSC from Mature to Core after TSC review and approval (Akraino Project Reviews).
DO WE WANT TO CONDUCT MBC PROJECT REVIEWS IN CORE STATE (AS THERE'S NO WHERE TO GO!)? OR RATHER HANDOVER PROJECT REPORTING TO THE PROJECT'S WIKI PAGE (FEATURES ADDED, BUGS etc)
Feature Project reporting
MF = Milestone Feature
REMOVE THE RC STAGES AS THIS IS A WATER FALL MODEL
Project Name | MF0 Kick-Off | MF1 Planning | MF2 Functionality freeze | MF3 API Freeze | MF4 Code Freeze | RC0 Release Candidate 0 | RC1 Release Candidate 1 | RC2 Release Candidate 2 | Sign-Off Release Delivery | |
|---|---|---|---|---|---|---|---|---|---|---|
| 17 | x | |||||||||
| 18 | x | |||||||||
| 19 | x | |||||||||
| 20 | x |