Versions Compared

Key

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

...


Project Name

MBI0

Project Induction


MBI1

Kick Off

MBI2

Planning complete


MBI3

Requirement/Feature Freeze (O)

Integration Test plan created


MBI4

Test Scripts developed

CD Lab is Set up


MBI5

Code Freeze (O)


MBI6

First Full CD deployment

Ad hoc reporting

CI/CD based testing and bug fixing


MBI7

Second community validation lab identified

MBI8

Second community validation lab fully setup

MBI9 MBI8

BP successfully deployed in second community validation lab

 MBI10

Critical issues fixed.

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

lab

Maturity 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:

  • Project remains at 'Incubation' (i.e. the request to graduate wasn't approved by the TSC)
  • 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

    MBI0Project InductionBlue Print is 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 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'.
    MBI2

    Planning complete

    • 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 validation.
    • 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 & testing
    • Peer Jenkins Set up in case of external validation lab (CI, Blueprint Validation Lab, documentation sub-committee
    MBI3

    Requirement/ Feature Freeze (if applicable)

    Integration Test plan created and shared


    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 and shared
    • Document the required lab setup . If the lab is third party lab, get the lab reserved.
    • Security:<TBF>


    MBI4

    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 including the method to reserve/un-reserve 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
    • Security: <TBF>
    MBI5

    Code Freeze (if applicable)

    • Integration complete of all SW packages that are part of the blueprint (In case of CI this waterfall approach is optional)
    • 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)
    MBI6

    First Full CD deployment

    • All requirements uptill up till MBI4  should be complete at this stage
    • First full CD deplyment 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 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 Second community validation lab fully setup
    • Second community validation
    lab 
    • 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 MBI8 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

    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