Skip to end of metadata
Go to start of metadata

Please refer to the NC Family Documentation - Release 1 for full details of the Unicycle with SR-IOV blueprint

Blueprint Description

Network Cloud Unicycle with SR-IOV support is based on the original seed code provided by AT&T as the foundation for the Akraino Network Cloud Blueprint Family. This blueprint uses Airship to deploy a containerized Openstack environment with support for SR-IOV to provide virtual machines a high speed, low latency data path.

This blueprint addresses multiple edge use cases supporting virtual machine based workloads.

Use Case

The primary use case of Unicycle with SR-IOV blueprint is to support vRAN and 5G Core applications or other VM based edge applications which require high performance through-put with low latency. The blueprint will be evolved further to support multiple edge use cases.

Where on the Edge

The Unicycle blueprint can be deployed at any location in a network where between a three to seven server multi-tenant Openstack service is required to support applications. 

It is expected that telco operator Central Office, Mobile Switch Offices or other aggregation sites would house this blueprint.

Deployment in non telco networks is equally supported.

Overall Architecture

The Network Cloud Architecture describes a detailed architectural view of Akraino Edge Stack Network Cloud (NC) Blueprint Family in R1.

The figure below shows the collection of opensource projects that enable the Akraino Edge Stack Network Cloud (NC) Blueprint Family. This picture also highlights (marked yellow) the components and projects which are updated to fulfill the requirements on this blueprint.

Platform Architecture

The Regional Controller fully automatically deploys one or more Unicycle pods at each edge site location under its control. Unicycle pods consist of 3 control nodes and 0 to 4 worker nodes. Control nodes can also host tenant VMs as well as worker nodes.  The configuration for each Unicycle edge site is defined in a user provided yaml based input file.  Additional details can be found in the NC Family Documentation - Release 1.


Licensed under the Apache License, Version 2.0 (the "License");
you may not use this software except in compliance with the License.
You may obtain a copy of the License at

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
See the License for the specific language governing permissions and
limitations under the License.

  • No labels