...
The generic model for an enterprise cloud has to be "hybrid" with the special cases of purely private or public clouds as subsets of the generic hybrid cloud deployment model. In a hybrid cloud deployment, at least two or more distinct cloud infrastructures are inter-connected together.
[ Petar suggests that we delete the following figure and I agree]
Cloud deployments can be created using a variety of technologies open-source (e.g., OpenStack, Kubernetes) and commercial commercial technologies (e.g., VMware). A multi-cloud deployment consists can consist of the use of more than one technology.
A generic Telco cloud is an hybrid multi-cloud. A better designation would be a federation of clouds - a Federated Telco Cloud (FTC)federated cloud:
a collection of cooperating, interoperable autonomous component clouds
- the component clouds perform their local operations (internal requests) while also participating in the federation and responding to other component clouds (external requests)
- the component clouds are autonomous in terms of, for example, execution autonomy
- execution autonomy is the ability of a component cloud to decide the order in which internal and external requests are performed
- the component clouds are loosely coupled where no control is imposed by some central component of the federated system
- the component clouds are likely to differ in, for example, infrastructure resources and their cloud platform software
- workloads may be distributed on single or multiple clouds, where the clouds may be colocated or geographically distributed
In this section we will further explore the characteristics of the federated cloud, architecture and architecture building blocks that constitute the federated cloud. For example, an FTC a Telco Cloud that consists of 4 sub-clouds: Private on prem, Cloud Vendor provided on prem, Private outsourced (Commercial Cloud Provider such as an HCP), and Public outsourced (see diagram below). Such an implementation of an FTC a Telco Cloud allows for mix'n'match of price points, flexibility in market positioning and time to market, capacity with the objective of attaining near "unlimited" capacity, scaling within a sub-cloud or through bursting across sub-clouds, access to "local" capacity near user base, and access to specialised services.
...
The Figure below presents a visualisation of a Federated Telco operator cloud (or simply, Telco cloud) with clouds and cloud components distributed across Regional Data Centers, Metro locations (such as Central Office or a Colocation site) and at the Edge, that are interconnected using a partial mesh network. Please note that at the Regional center level the interconnections are likely to be a "fuller" mesh while being a sparser mesh at the Edges.
...
- The Telco Operator may own and/or have partnerships and network connections to utilize multiple Clouds
- for network services, IT workloads, external subscribers
- On Prem Private
- Open source; Operator or Vendor deployed and managed | OpenStack or Kubernetes based
- Vendor developed; Operator or Vendor deployed and managed | Examples: Azure on Prem, VMWareVMware, Packet, Nokia, Ericsson, etc.
- On Prem Public: Commercial Cloud service hosted at Operator location but for both Operator and Public use | Example: AWS Wavelength
- Outsourced Private: hosting outsourced; hosting can be at a Commercial Cloud Service | Examples: Equinix, AWS, etc.
- (Outsourced) Public: Commercial Cloud Service | Examples: AWS, Azure, VMWareVMware, etc.
- Multiple different Clouds can be co-located in the same physical location and may share some of the physical infrastructure (for example, racks)
...
| Type | System Developer | System Maintenance | System Operated & Managed by | Location where Deployed | Primary Resource Consumption Models |
|---|---|---|---|---|---|
| Private (Internal Users) | Open Source | Self/Vendor | Self/Vendor | On Prem | Reserved, Dedicated |
| Private | Vendor | HCP | Self/Vendor | Self/Vendor | On Prem | Reserved, Dedicated |
| Public | Vendor | HCP | Self/Vendor | Self/Vendor | On Prem | Reserved, On Demand |
| Private | HCP | Vendor | Vendor | Vendor Locations | Reserved, Dedicated |
| Public (All Users) | HCP | Vendor | Vendor | Vendor Locations | On Demand, Reserved |
- Each Federated Telco Cloud (FTC) consists of multiple interconnected Regions
- An FTC A Telco Cloud Region may connect to multiple regions of another FTC another Telco Cloud (large capacity networks)
- An FTC A Telco Cloud also consists of interconnected local/metro sites (multiple possible scenarios)
- An FTCA Telco Cloud's local site may connect to multiple Regions within that FTC that Telco Cloud or another FTCTelco Cloud
- A Telco Cloud An FTC also consists of a large number of interconnected edge nodes
- Edge nodes may be impermanent
- An FTCA Telco Cloud's Edge node may connect to multiple local sites within that FTC that Telco Cloud or another FTCTelco Cloud; an Edge node may rarely connect to an FTC a Telco Cloud Region
Telco Operator Platform Conceptual Architecture
...