...
Below is a sample Use case template. The full template will be maintained on the Akraino Wiki.
Use Case Attributes | Description | Informational |
Type | New or Modification to an existing submission |
|
Industry Sector | Telco and carrier networks |
|
Business driver | Emerging technologies such as 5G (vRAN, Core) and associated Edge Services requires Cloud instance deployed at the edge of the provider network to support latency need.
Without Edge Cloud, above said services cannot be enabled. |
|
Business use cases | For Example:
|
|
Business Cost - Initial Build | For Example:
|
|
Business Cost - Operational | For Example:
|
|
Operational need | For Example: Edge Solution should have role based access controls, Single Pane of Glass control, administrative and User Based GUIs to manage all network cloud family based blueprints. The automation should also support zero touch provisioning and management tools to keep operational cost lower |
|
Security need | For Example: The solution should have granular access control and should support periodic scanning |
|
Regulations | For Example: The Edge cloud solution should meet all the industry regulations of data privacy, telco standards (NEBS), etc., |
|
Other restrictions | Consider the power restrictions of specific location in the design (example - Customer premise) |
|
Additional details | The Edge Cloud Solution should be deployable across the globe and should be able to support more than 10,000 locations |
|
3.3.2.2.2.2 Template 2 - Blueprint family template
Below is a sample Blueprint family template. The full template will be maintained on the Akraino Wiki.
Use Case Attributes | Description | Informational |
Type | New or Modification to an existing submission |
|
Blueprint Family - Proposed Name | Network Cloud Family |
|
Use Case | Network Cloud |
|
Blueprint proposed | Central Office deployments
Customer Premise deployments
|
|
Initial POD Cost (capex) | Examples Only:
|
|
Scale | Examples Only:
|
|
Applications | Any type of Edge Virtual Network Functions |
|
Power Restrictions | Example Only:
|
|
Preferred Infrastructure orchestration | OpenStack - VM orchestration Docker/K8 - Container Orchestration OS - Linux VNF Orchestration - ONAP Under Cloud Orchestration - Airship |
|
Additional Details | Submitter to provide additional use case details |
|
3.3.2.2.2.3 Template 3 - Blueprint species template
Below is a sample Blueprint template defining an Akriano species. The full template will be maintained on the Akraino Wiki.
Use Case Attributes | Description | Informational |
Type | New or Modification to an existing submission |
|
Blueprint Family - Proposed Name | Network Cloud Family |
|
Use Case | Network Cloud |
|
Blueprint proposed Name | Unicycle A |
|
Initial POD Cost (capex) | Examples Only:
|
|
Scale & Type |
|
|
Applications | 5G Core or vRAN (RIC) |
|
Power Restrictions | Example Only:
|
|
Infrastructure orchestration | OpenStack Pike or above - VM orchestration Docker 1.13.1 or above / K8 1.10.2 or above- Container Orchestration OS - Ubuntu 16.x VNF Orchestration - ONAP Beijing Under Cloud Orchestration - Airship v1.0 |
|
SDN | SR-IOV & OVS-DPDK or VPP-DPDK |
|
Workload Type | VMs and Containers |
|
Additional Details | Submitter to provide additional use case details |
|
3.3.2.3 Akraino Validation Projects
...
The life cycle of a project is depicted in the following diagram:
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
To move from one state to the next state, the Project Team has to formulate a Kick-Off release review to the TSC, by specifying its goal to move up the Project Lifecycle ladder.
From State | To State | Review Description |
Null | Proposal |
|
Proposal | Incubation | Incubation review |
Incubation | Mature | Maturity review |
Mature | Core | Core review |
Core | Archived | Termination review |
Note 1: Project proposals are posted in the “Proposed Projects” section of the Akraino wiki. Approved projects are posted to the “Approved Projects” section of the Akraino wiki.
...
A project’s release cycle may be tailored by allowing some exceptions to the normal release process. Tailoring may be initiated in two ways:
- By the TSC voting membersvoting members: TSC voting members reserves the right to allow changes to the process in order to meet criteria that were initially unknown.
- By Project Team Lead: Any project team lead can email TSC voting members to request tailoring the process the process for a particular release. The key point in tailoring is to anticipate as much as possible, to justify the request, and document the request in the wiki.
Tailoring practices will be documented as we progress through our releases. The TSC should respond to requests in a timely manner.
...
As a guideline, a subcommittee is most appropriate when the task to be addressed involves a relatively stable group of people with a high level of intersection of common involvement. A coordinator is more appropriate when there is a more dynamic group of people and issues may change frequently. A coordinator is also more appropriate for smaller efforts or topics requiring infrequent meetings.
Glossary
Term | Full Meaning |
IoT | Internet of things |
PTL | Project technical lead |
ETE | End to end |
SDK | Software development kit |
API | Application program interface |
POD | Point of delivery |
CI/CD | Continuous integration and continuous delivery |
LCM | Lifecycle management |
YAML | YAML Ain't Markup Language. It's basically a human-readable structured data format. |
OS | Operating system |
EOL | End of life |
VNF
CIVS | Virtual Network Function (VM or container based)
Condorcet Internet Voting Service
|