The virtual infrastructure design comprises the design of the software components that form the virtual infrastructure layer. This layer supports running telco workloads and workloads that maintain the business continuity of services. The virtual infrastructure components include the virtualization platform hypervisor, virtualization management, storage virtualization, network virtualization, and backup and disaster recovery components.
This section outlines the building blocks for the virtual infrastructure, their components, and the networking to tie all the components together.
This reference architecture uses a shared storage design that is based on vSAN. Telco Cloud Infrastructure also supports certified third-party shared storage solutions, as listed in the VMware Compatibility Guide.
vSAN is a storage virtualization software that allows locally attached storage to be pooled and presented as a shared storage pool for all hosts in a vSphere cluster. This simplifies the storage configuration with a single datastore per cluster for the management and VNF workloads. With vSAN, VM data is stored as objects and components. An object consists of multiple components, which are distributed across the vSAN cluster based on the policy that is assigned to the object. The policy for the object ensures a highly available storage backend for the cluster workload, with no single point of failure.
vSAN is a fully integrated hyperconverged storage solution that allows creating hybrid or all flash-based vSAN storage cluster. vSAN presents a flash-optimized, highly resilient, shared storage datastore to ESXi hosts and VMs. This allows for the control of capacity, performance, and availability through storage policies, on a per VM basis.
The Telco Cloud Infrastructure platform consists of Infrastructure (VMkernel and VM network traffic) networks. Infrastructure networks are host-level networks that connect hypervisors to physical networks. Each ESXi host has multiple port groups configured for each infrastructure network.
The hosts in each Pod are configured with VMware vSphere® Distributed Switch™ (VDS) that provide a consistent network configuration across multiple hosts. One VDS switch is used for VM networks and VMkernel networks. The N-VDS Enhanced switch is used as the transport for the telco workload traffic.
Infrastructure networks are used by the ESXi hypervisor for vMotion, vSphere Replication, vSAN traffic, management, and backup as well as Management VMs to communicate with each other. A separate N-VDS Enhanced switch is used for workload traffic. Each N-VDS switch has separate uplink connectivity to the physical data center network, completely separating its traffic from other network traffic. The uplinks are mapped to a pair of physical NICs on each ESXi host for optimal performance and resiliency.
VMs can be connected to each other over a VLAN or over Geneve-based overlay tunnels. Both networks are designed according to the requirements of the workloads that are hosted by a specific Pod. The infrastructure VDS and networks remain the same regardless of the Pod function. However, the VM networks depend on the networks that the specific Pod requires. The VM networks are created by NSX-T Data Center to provide enhanced networking services and performance to the Pod workloads. The ESXi host's physical NICs are used as uplinks to connect the distributed switches to physical network switches. All ESXi physical NICs connect to layer 2 or layer 3 managed switches on the physical network. It is common to use two switches for connecting to the host physical NICs for redundancy purposes.
The VMkernel traffic networks used in the Pods are:
ESXi Management Network: The network for the ESXi host management traffic.
vMotion Network: The network for the VMware vSphere® vMotion® traffic.
vSAN Network: The network for the vSAN shared storage traffic.
Backup Network: The network that is dedicated to offline storage such as NFS and used for workload backup and restore as required.
Replication Network: The network that is used for replicating data for data protection.