This section lists the deployment requirements for Demo Footprint

The following table shows the infrastructure requirements for each deployment platform in terms of CPU, RAM, and the expected number of nodes. Validation of available resources must be performed before installation to ensure that the required capacity is in place. In addition to CPU and RAM requirements, the table also provides information on the expected storage requirements. Storage requirements are calculated based on footprint size and desired raw metric retention period. Use the storage size values for the amount of storage that is expected for persistent data. Persistent volumes are allocated for different services with the backing of persistent storage supported by each of the deployment platforms. Finally, the table also provides some high-level operation metrics that can be used as guidance to determine the suitability supported by each of the given footprints.
Note: For planning the deployment of IP, SAM, ESM Domain Managers, and VMware Telco Cloud Service Assurance sizing in Production environment, refer VMware Telco Cloud Service Assurance Sizing Sheet. The below table captures the Resources required only for the VMware Telco Cloud Service Assurance Demo deployment
Number of Managed Devices (includes routers, switches, hosts, VMs, CNFs, or pods) Demo (750 devices)
TKG Management Cluster Control Plane Node/Worker Node 3 VMs
2 vCPU per VM
4 GB RAM per VM
50 GB local disk
TKG Workload Cluster Control Plane Node 3 VMs across all footprints.
2 vCPU per VM
4 GB RAM per VM
50 GB local disk
Worker Node 4 VMs
16 vCPU per VM
32 GB RAM per VM
100 GB local disk (1.5Tb of vSAN Datastore for PVs)
AKS/EKS Workload Cluster Worker Node 4 VMs
16 vCPU per VM
32 GB RAM per VM
100 GB Local Disk (1.5TB of vSAN Datastore for PVs)
VMBased Deployment Control Plane Node 1 VM
4 vCPU per VM
16 GB RAM per VM
50 GB Local Disk
Note:

The /var partition/directory must have minimum of your 10 GB. This is for the ephemeral storage and filebeat service.

The /tmp partition/directory must have minimum of 8 GB.
Worker Node
VMBased - LocalPV 6 VMs
16 vCPU per VM
32 GB RAM per VM
6 VMs with 650 GB of total storage space.
Note: The /var partition/directory must have minimum of 32 GB. This is for the ephemeral storage and filebeat service.

The /tmp partition/directory must have minimum of 16GB.
VMBased - vSAN 6 VMs
16 vCPU per VM
32 GB RAM per VM
6 VMs with 250Gb of total storage space.
Note:
  • The /var partition/directory must have minimum of 32 GB. This is for the ephemeral storage and filebeat service.

    The /tmp partition/directory must have minimum of 16GB

  • 1.5 TB is the actual storage size required for the data. Based on vSAN Storage policy, the storage size provisioned needs to be increased.
Number of devices 750
Total number of metrics every five minutes 300 K
Total number of active events 8 K
Number of concurrent Northbound API calls 10
Number of concurrent users 10
Bandwidth utilization for Storage Traffic 3.5 Mbps
Total Disk IOPS (Read + Write) 100
Number of Alarms/Analytics definitions 10
Remediation Rule 10
Note: The following notes apply to Demo and Production footprints:
  • For Production deployment, the minimum number of supported VMs, metrics, devices, and events are 9, 3 million, 7.5 K, and 75 K.
  • The Demo footprint is for non-production deployment without HA capabilities and cannot be upgraded and flexibly scaled. Also, it does not support the backup and restore feature.
  • The Demo and Production Footprint System requirements table shows the VMware Tanzu Kubernetes Grid management sizing for deployments where a dedicated TKG management cluster is used for the TKG workload cluster. To size deployments when multiple workload clusters are managed by a single management cluster, see VMware Tanzu Kubernetes Grid documentation.
  • For VMware Tanzu Kubernetes Grid management and workload cluster, and VMBased Deployment it is recommended to enable vSphere HA.
  • In AKS and AWS, by default, first three worker nodes can also be the control plane nodes.
  • The default raw metrics retention interval is 1w and is configurable. If you decide to change the retention interval period, the persistent volume storage must change accordingly.
  • For each of the deployment platforms, a container storage interface is required so that persistent volumes can be allocated from the underlying infrastructure. System requires a storage class provided by the infrastructure that can be used for deployment of stateful services. For the required storage class, see the section for the relevant deployment target.
  • Its recommended not to run the Demo footprint deployments for more than a month.