MBI0 | Project Induction | Blue Print is voted by TSC as an Akraino Blueprint. The project is defined and approved by TSC vote to enter incubation stage (Incubation Review) |
MBI1 | Kick 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 Process 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 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 | 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
- Peer Jenkins Set up in case of external validation lab (CI, Blueprint Validation Lab, documentation sub-committee
- Security: <TBF>
|
MBI4 | First Full CD deployment | - All requirements up till MBI4 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 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
|
MBI5 | Second community validation lab fully setup | - Second community validation lab is identified and set up
- This is non sequential and not dependent on any other MBI
- Peer Jenkins, BP HW and all necessary components setup ready to start testing of BP
|
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. |
Maturity Graduation review | TSC 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: - 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)
|