...
The below diagram (Figure 5) illustrates the process.
Figure 5 – Akraino Blueprint Creation Process
...
Below picture illustrates the Network Cloud blueprint family and POD level specification which allows possibility of different component level.
Figure 6 - Illustration of blueprint family and its blueprints
3.3.2.2.2 Akraino Use Cases, blueprint families and blueprints
...
Blueprint templates are required to create or modify blueprints within a blueprint family. In some cases, new or modification to a blueprint may require updates to existing use case templates and/or blueprint family templates and the submitter should make changes to all 3 templates as required.
Figure 7 - Templates needed for blueprint family and blueprint creation and modification
When one or more fully defined blueprint addresses the same use case common test cases should be adopted where possible.
...
Individual blueprint within a blueprint family shall not be tied to the overall Akraino release schedule (e.g. 6 months). An Akraino release can be composed of 1 to N fully verified blueprints or individual feature projects. As such the number of blueprints and contributing projects within a given Akraino release may vary overtime. Figure 8 show this with two blueprint families, Network Cloud and the imaginary Canis Edge and a number of individual blueprint species within each family.
Figure 8 - Project and AKraino Akraino release lifecycles
Each project shall provide an expected release plan document published with the blueprint on the wiki. From the project schedules an overall Akraino release schedule shall be maintained and published.
...
Project State | Description |
Proposal | Project doesn’t really exist yet, may not have real resources, but is proposed and is expected to be created due to business needs. |
Incubation | Project has resources, but is recognized to be in the early stages of development. The outcome is a minimum viable product (MVP) that demonstrates the value of the project and is a useful vehicle for collecting feedback, but is not expected to be used in production environments. |
Mature | Project is fully functioning and stable, has achieved successful releases. |
Core | Project provides value to and receives interest from a broad audience. |
Archived | Project can reach Archived state for multiple reasons. Either project has successfully been completed and its artifacts provide business values, or project has been cancelled for unforeseen reasons (no value anymore, technical, etc.). Project in any state can be Archived through a Termination Review. |
Figure 9 – Akraino Project States
...
The TSC functional roles of chair and co-chair will be held by TSC members.
Figure 10 - Akraino Community Structure
4.3 TSC Functional Roles
...