Versions Compared

Old Version 19

changes.mady.by.user Andrew Wilkinson

Saved on

compared with

New Version 20

changes.mady.by.user Andrew Wilkinson

Saved on

Key

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

Akraino project reporting provides visibility of the each BP validation project (MB1MBx1, MB2 MBx2 etc) and feature project (MF1, MF2 etc) by means of a set of defined milestones.

...

Incubation stage reporting

 MBI = Milestone Bp Incubation

1) Entry Criteria:  MB0 The MBI0The project is approved to enter the 'Incubation' stage after TSC review and approval (Akraino Project Reviews)

...

The graduation reviews are done by assessing the projects 


Project Name

MB0MBI0

Kick-Off

(Project inducted to 'Incubation' by TSC)

MB1MBI1

Planning complete

Identify integration/developers team & testing team

MB2MBI2

Integration Test plan created and shared with the community

Requirement/Feature Freeze (if applicable)

MB3MBI3

Scripts development and Set up accessible

Lab is set up for CD


MB4MBI4

Code Freeze (if applicable)

Additional test case development complete (

MB5MBI5

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)

MB6MBI6

Second community validation lab identified

MB7MBI7

Second community validation lab fully setup

MB8MBI8

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 Familyx









2Serverless Blueprint Proposal for Addition to Network Cloud Blueprint Familyx









3

Unicycle Blueprint Proposal for Addition to Network Cloud Blueprint Family

x









4

Rover Blueprint Proposal for Addition to Network Cloud Blueprint Family

x









5OVS-DPDK Unicycle Dell Blueprint Proposalx









6

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

x









7Edge Video Processingx









8

ELIOT IoT Gateway Blueprint

x









9

ELIOT SD-WAN/WAN Edge/uCPE Blueprint

x









10

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

x









11IEC Type 2 for Integrated Edge Cloud (IEC) Blueprint Familyx









12

Industrial Edge (IE) Blueprint

x









13

Provider Access Edge (PAE) Blueprint

x









14

Radio Edge Cloud

x









15

StarlingX Far Edge Distributed Cloud

x









16

Time-Critical Edge Compute

x









17

Micro-MEC













CHECK AND UPDATE TABLE BELOW ONCE MBIs AGREED

MBI

Name

Description/Checklist

MBI0Blue Print Kick OffThe project is defined and approved to enter incubation stage (Incubation Review)
MBI1Planning complete
  • Projects that have successfully completed MS0, 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 Jenkins Set up (NS)
MBI2

Integration Test plan created and shared with the community

Requirement/ Feature Freeze (if applicable)


  • 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

Scripts development and Set up accessible

  • Make scripts available to create setups in third party labs.
  • Make the setups accessible for everybody (optional).
  • Instructions to access the setups. Method to reserve/un-reserve setups. Preferably two setups at-least.
  • Security: <TBF>
MBI4

Code Freeze (if applicable)

Test case development complete



  • Integration complete of all SW packages that are part of the blueprint
  • 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

first deployment in validation lab

first testing logs shipped

  • All requirements uptill MB4 including NS ones should be complete at this stage
  • 1st run of test cases and results shared
  • 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

Mature stage reporting

 MBM = Milestone Bp Mature

1) Entry Criteria:  MB0 MBM0 The project is graduated by the TSC from Incubation to Mature after TSC review and approval (Akraino Project Reviews)




Project Name

MB0MBM0

Kick-Off

(Project graduated from 'Incubation' to 'Mature' by TSC)

MB1MBM1


......


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. Project remains at 'Mature' (i.e. the request to graduate wasn't approved by the TSC)
  2. Project graduates from 'Mature' to 'Core' (i.e. the request to graduate was approved by the TSC)
1SDN Enabled Broadband Access (SEBA) for Network Cloud Blueprint Family





2Serverless Blueprint Proposal for Addition to Network Cloud Blueprint Family





3

Unicycle Blueprint Proposal for Addition to Network Cloud Blueprint Family







4

Rover Blueprint Proposal for Addition to Network Cloud Blueprint Family







5OVS-DPDK Unicycle Dell Blueprint Proposal





6

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







7Edge Video Processing





8

ELIOT IoT Gateway Blueprint







9

ELIOT SD-WAN/WAN Edge/uCPE Blueprint







10

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







11IEC Type 2 for Integrated Edge Cloud (IEC) Blueprint Family





12

Industrial Edge (IE) Blueprint







13

Provider Access Edge (PAE) Blueprint







14

Radio Edge Cloud







15

StarlingX Far Edge Distributed Cloud







16

Time-Critical Edge Compute







17

Micro-MEC






...

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)

...


Project Name

M0 Kick-Off

M1

Planning

M2

Functionality freeze

M3

API Freeze

M4

Code Freeze

RC0

Release Candidate 0

RC1

Release Candidate 1

RC2

Release Candidate 2

Sign-Off

Release Delivery


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

Akraino Blueprint Validation Framework

x







18

Akraino Portal Feature Project

x







19

Cluster Health & Overload Monitoring Platform (CHOMP) Feature Project

x







20

Support of OVS-DPDK in Airship

x

MS

Name

Description/Checklist

MB0Blue Print Kick OffThe project is defined and approved to enter incubation stage (Incubation Review)MB1Planning complete
  • Projects that have successfully completed MS0, 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 Jenkins Set up (NS)
MB2

Integration Test plan created and shared with the community

Requirement/ Feature Freeze (if applicable)

  • 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>
MB3

Scripts development and Set up accessible

  • Make scripts available to create setups in third party labs.
  • Make the setups accessible for everybody (optional).
  • Instructions to access the setups. Method to reserve/un-reserve setups. Preferably two setups at-least.
  • Security: <TBF>
MB4

Code Freeze (if applicable)

Test case development complete

  • Integration complete of all SW packages that are part of the blueprint
  • 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
MB5

first deployment in validation lab

first testing logs shipped

  • All requirements uptill MB4 including NS ones should be complete at this stage
  • 1st run of test cases and results shared
  • All test cases planned for the release have been executed
  • Test results published
  • Failures and other issues have been documented
MB6

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-OffReleaseProjects tagged by PTLs using tagging procedure.