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
...
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 or a subsequent 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 projects against the Incubation to Mature review as defined in the Akraino Project Reviews page.
Note: Reporting of 'Achieved dates' are mandatory (if not optional milestones). The advance publishing of Target dates is optional.
Project Name | MBI0 Project |
---|
Induction | MBI1 |
---|
Kick Off | MBI2 Planning |
---|
process defined | MBI3 |
---|
Integration Test plan created and shared with the community
Requirement/Feature Freeze (if applicable)
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 |
---|
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 serversAd hoc reporting CI/CD based testing and bug fixing |
---|
MBI5 Second community validation |
---|
MBI8
Second community validationlab fully setup |
---|
MBI9
BP successfully deployed in second community validation lab
MBI10
Critical issues fixed.
Documentation complete for other community member(s)s to deploy identical validation lab
MBI6 Ready for Maturity Review | Maturity Graduation Review as per BP Graduation Review Processes and Criteria |
---|
(Request for graduation review made by PTL |
---|
(Decision of graduation made TSC)
TSC's Graduation review can have one of two outcomes:
) | |
---|---|
1 |
12/7/2019 | Target date |
Feb 2, 2019 | April 22, 2019 | May 30, 2019 | Jun 30, 2019 | |||||
Achieved date |
Feb 2, 2019 | |||||||
2 | Serverless Blueprint Proposal for Addition to Network Cloud Blueprint Family | 12/7/2019 | Target date |
Achieved date |
3 |
12/7/2019 | Target date |
Achieved date |
Feb 11, 2019 | Apr 29, 2019 | Aug 22, 2018 | Aug 22, 2018 | Feb 11, 2019 | ||||
4 | 12/7/2019 | Target date |
Achieved date |
Feb 11, 2019 | Apr 29, 2019 | Aug 22, 2018 | Aug 22, 2018 | Feb 11, 2019 | ||||
5 | 12/7/2019 | Target date |
Feb 8,2019 | March 13,2019 | May 3, 2019 | May 30, 2019 | |||||
Achieved date | Feb 8,2019 | March 13,2019 | April 29, 2019 | May 26, 2019 |
6 | 12/7/2019 | Target date |
Achieved date |
7 | 12/7/2019 | Target date |
Mar 23, 2019 | Mar 29, 2019 | Apr 22, 2019 | May 30, 2019 | May 31, 2019 | ||||
Achieved date |
Mar 23, 2019 | Mar 29, 2019 | ||||||
8 | 12/7/2019 | Target date |
Feb 27, 2019 | Apr 30, 2019 | May 10, 2019 | May 30, 2019 | |||||
Achieved date |
9 | 12/7/2019 | Target date |
Feb 27, 2019 | Apr 30, 2019 | May 10, 2019 | May 30, 2019 | |||||
Achieved date |
10 | 12/7/2019 | Target date |
Jan 28, 2019 | Feb 05, 2019 | Apr 15, 2019 | May 30, 2019 | Jun 30, 2019 | ||||
Achieved date | Jan 28, 2019 | Feb 05, 2019 | Apr 2, 2019 | May 21, 2019 |
11 | 12/7/2019 | Target date |
Jan 28, 2019 | Feb 05, 2019 | Apr 15, 2019 | May 30, 2019 | Jun 30, 2019 | ||||
Achieved date | Jan 28, 2019 | Feb 05, 2019 | Apr 2, 2019 | May 21, 2019 |
12 | 12/7/2019 | Target date |
Feb 11, 2019 | Apr 30, 2019 | May 5, 2019 https://jenkins.akraino.org/view/kni/ | Jun 30, 2019 | Jun 30, 2019 | ||||
Achieved date | Feb 11, 2019 | Apr 30, 2019 | May 3, 2019 |
13 | 12/7/2019 | Target date |
Feb 11, 2019 | Apr 30, 2019 | May 5, 2019 https://jenkins.akraino.org/view/kni/ | May 30, 2019 | Jun 30, 2019 | ||||
Achieved date | Feb 11, 2019 | Apr 30, 2019 | May 3, 2019 | May 27, 2019 |
14 | 12/7/2019 | Target date |
2019-03-12 | 2019-05-20 | 2019-05-15 | 2019-05-30 | 2019-05-10 | 2019-05-30 | |||
Achieved date | 2019-03-12 | 2019-05-28 | 2019-05-28 | 2019-05-28 |
15 | 12/7/2019 | Target date |
2019-03-04 | 2019-05-03 | 2019-05-28 | 2019-05-28 | |||||
Achieved date |
2019-03-04 | 2019-05-03 | 2019-06-04 | 2019-06-04 | |||||
16 | 12/7/2019 | Target date |
Achieved date |
17 | Target date | ||||||||||
Achieved date | |||||||||||
18 | 12/4/2019 | Target date |
April 12, 2019 | June 12, 2019 | Sep 12, 2019 | Oct 12,2019 | ||||||||
Achieved date | |||||||||||
19 | 4/25/2019 | Target date | May 10, 2019 | June 6, 2019 | August 12, 2019 | October 12, 2019 | November, 12 2019 | TBD | TBD | ||
Achieved date | May 10, 2019 | ||||||||||
20 | |||||||||||
21 |
CHECK AND UPDATE TABLE BELOW ONCE MBIs AGREED
MBI | Name | Description/Checklist |
---|---|---|
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 |
|
|
|
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>
Scripts development and Set up accessible
AW: What are these scripts?
Lab is set up for CD
Additional Test scripts development CD lab is setup |
|
|
|
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 (AW: not all additional testing must be automated) and made them 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 |
|
First deployment in validation lab
First testing logs shipped
|
| ||
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.
|
MBI5 | Second community validation lab fully setup |
|
|
Part of the graduation requirements from incubation to mature require deployment in at least 2 community labs
|
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. |
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 review | TSC conducts graduation review as per criteria set out in |
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:
|