Objective
The Reference Architectures define all infrastructure components and properties which have an effect on the virtualised services design, deployment, and operations. The Reference Architecture for Virtualised Cloud Infrastructure (RA1) specifies an OpenStack based Infrastructure-as-a-Service (IaaS) cloud architecture. The Reference Architectures define all infrastructure components and properties which have effect on the virtualised services design, deployment, and operations. The RA1 The document specifies the components of an a conformant IaaS cloud platform stack: a selection of OpenStack projects (capabilities), the resources, and the interfaces exposed by a conformant IaaS cloud service to the workloads.
Problem Statement
Over the past few years, the telecom industry has been going through a massive technology revolution by embracing software defined networking and cloud architecture principles , in pursuit of the goal of achieving more flexibility, agility and operational efficiency. At a high level, the main objective of NFV (Network Function Virtualisation) is the ability to use general purpose standard COTS (Commercial off the Shelf) compute, memory and storage hardware platforms to run multiple virtualised network services (Virtualised Network Functions (- i.e. VNF ) / Cloud Native Network Functions (- i.e. CNF)). Earlier common infrastructure models built based on the previous assumption that networking applications are typically built on discrete hardware, do not offer the level of flexibility and agility needed for the support of newer networking technologies such as 5G, intelligent networks and Edge computing.
...
- Higher development costs due to the need to develop virtualised services on multiple custom platforms for each operator
- Increased complexities due to the need to maintain multiple versions of applications to support each custom environment
- Lack of testing and validation commonalities, leading to inefficiencies and increased time to market. While the operators will still do internal testing, but using an industry driven verification program based on a common cloud infrastructure would provide a head start.
- Slower adoption of cloud-native applications and architectures. A Common common Telco Cloud may provide an easier path to methodologies that will drive faster cloud-native development.
- Increased operational overhead due to the need for operators to integrate diverse and sometime conflicting cloud platform requirements.
The need for a Common Telco Cloud Infrastructure model across the industry to facilitate more rapid adoption is clear. By running network applications services as software rather on commodity hardware, rather than on purpose-built hardware, the operators aspire to realize realise operational efficiencies , and capital expense savings. These virtualised network services services are increasingly being used by telecom operators to support their internal and customer facing network infrastructures. The need for a Common Cloud Infrastructure model across the industry to facilitate more rapid adoption of cloud is clear.
Scope
The diagram below above shows the different types of specifications and how they relate to the different elements of a typical cloud platform stack. RA1 builds upon the Reference Model (RM) specifications, and details:
OpenStack: the selection of OpenStack version and OpenStack projects that would be components of the cloud platform, and specifications for their resiliency and availability
...
Life Cycle Management (LCM): including but not limited to configuration management, logging, monitoring, and alerting.
Link to Reference Architecture Specifications
The RA1 documentation is available here.
Regular Meetings
Normally, Every Monday (check Calendar) 1530 UTC
Zoom: https://zoom.us/j/99279174971?pwd=eWozNENnYkpLSXdRSzZvblNKVU1wdz09
Meetings Agenda and Minutes
The Agenda and Minutes are available here.