Versions Compared

Old Version 11

changes.mady.by.user Andrew Wilkinson

Saved on

compared with

New Version 12

changes.mady.by.user Andrew Wilkinson

Saved on

Key

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

...

The graduation reviews are done by assessing the projects 



Project Name

MBI0

Project inducted to 'Incubation' by TSC


MBI1

First regular community call held

MBI2

Planning complete

Identify integration/developers team & testing team

MBI3

Integration Test plan created and shared with the community

Requirement/Feature Freeze (if applicable)

MBI4

Scripts development and Set up accessible

Lab is set up for CD


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

Critical issues fixed.

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

MBI7

Second community validation lab identified

MBI8

Second community validation lab fully setup

MBI9

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. 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)
1SDN Enabled Broadband Access (SEBA) for Network Cloud Blueprint Family

12/7/2019

Target date










Achieved date










2Serverless Blueprint Proposal for Addition to Network Cloud Blueprint Family

12/7/2019

Target date










Achieved date










3

Unicycle Blueprint Proposal for Addition to Network Cloud Blueprint Family

12/7/2019

Target date










Achieved date










4

Rover Blueprint Proposal for Addition to Network Cloud Blueprint Family

12/7/2019

Target date










Achieved date










5OVS-DPDK Unicycle Dell Blueprint Proposal

12/7/2019

Target date










Achieved date










6

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

12/7/2019

Target date










Achieved date










7Edge Video Processing

12/7/2019


Target date










Achieved date










8

ELIOT IoT Gateway Blueprint

12/7/2019Target date










Achieved date










9

ELIOT SD-WAN/WAN Edge/uCPE Blueprint

12/7/2019Target date










Achieved date










10

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

12/7/2019Target date










Achieved date










11IEC Type 2 for Integrated Edge Cloud (IEC) Blueprint Family12/7/2019Target date










Achieved date










12

Industrial Edge (IE) Blueprint

12/7/2019Target date










Achieved date










13

Provider Access Edge (PAE) Blueprint

12/7/2019Target date










Achieved date










14

Radio Edge Cloud

12/7/2019Target date










Achieved date










15

StarlingX Far Edge Distributed Cloud

12/7/2019Target date










Achieved date










16

Time-Critical Edge Compute

12/7/2019Target date










Achieved date










17

Micro-MEC


Target date










Achieved date











CHECK AND UPDATE TABLE BELOW ONCE MBIs AGREED


MBI

Name

Description/Checklist

MBI0Blue Print Kick OffThe project is defined and approved by TSC vote to enter incubation stage (Incubation Review)
MBI1 First regular community call held 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'.
MBI2Planning complete

MBI2 is dependent on MBI1

  • Projects that have successfully completed
MS0
  • MBI1, must complete their planning, including scenario or deliverable definition.
  • As part of the planning process, all projects will complete a project planning template.
  • hardware set up definition frozen
(NS)
  • Identify team working on features & testing
(NS)
Paid
  • Peer Jenkins Set up
(NS)
MBI2
MBI3


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
  • hardware set up definition frozen ( NS)
  • Document the lab setup required and identify the labs that would be used to test this blueprint. If the lab is third party lab, get the lab reserved.
  • Security:<TBF>
MBI3


MBI4

Scripts development and Set up accessible

AW: What are these scripts?

Lab is set up for CD

  • Make scripts available to create setups in third party labs.
  • Make the setups accessible for everybody (optional
).
  • ) - AW: must be available to community if part of BP)
  • Instructions to access the setups. Method to reserve/un-reserve setups. Preferably two setups at-least. (AW: What does two setups mean?)
  • All HW required to deploy the BP has been installed and is ready to start CD of actual BP
  • Security: <TBF>
MBI4
MBI5

Code Freeze (if applicable)

Test

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 (AW: not all additional testing must be automated)
All test cases are automated
  • and made them available in blueprint repos.
  • Make the images available in public repository (Nexus?) and create scripts
to
  • necessary to install all SW packages in various sites as identified by blueprint
MBI5
  • (In case of CI this waterfall approach is optional)


MBI6

First

first

deployment in validation lab

first

First testing logs shipped

  • All requirements uptill
MB4 including NS ones
  • MB4  should be complete at this stage
  • 1st run of test cases and
results shared
  • rest results logs automatically posted to LF CI servers  
  • All test cases planned for the release have been executed
  • Test results published
  • Failures and other issues have been documented
MBI6

CI/CD based testing

Critical issues fixed.

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

  • Complete the documentation
  • Critical issues fixed
Sign-OffReleaseProject graduate to Mature stage