...
A reference architecture is provided for each use case, driving the corresponding blueprint. A set of Blueprints comprises an Akraino release. TSC will provide acceptance criteria for each release. See the Figure below.
For instance, a 5G Core or 5G access use case will require support for Service-Based Architecture (SBA) as an enabler of Cloud Native 5G implementations. SBA aims to evolve the 5G system in such a way that it will enable novel network architecture capabilities, e,g,, the re-use of services and flexible network slicing, by means of functionality offered as a service from the Network Functions (NF). The NF services will be implemented as containers. Therefore, the selected blueprint must provide support for containers and container management framework like Kubernetes. Furthermore, networking and storage needs of Kubernetes can be supported by Calico as a CNI (Container Networking Interface) plugin and Ceph as Software Defined Storage (SDS). Data plane needs can be supported by SR-IOV/OVS. A POD based on Cruiser can provide support for all control, compute, and storage nodes to be hosted on racks and physically connected and networked. Airship is used as the orchestration tool to deploy the Kubernetes based containerized cluster with support for Calico and Ceph. The physical underlay network provides L2 connectivity from the control and compute nodes to the TORs. Separate networks are provided for management, storage, Redfish API, and KSN. KSN provides an L2 transport network to setup L3 network using BGP route peering with Fabric TORs. Accompanying the CI/CD system and test automation tools provides the ability to integrate, test and deploy the Blueprint code. Finally, a fully declarative configuration management brings the blueprint together to support the use case.
...