This section lists the deployment requirements for Demo and HA footprints.
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, ESM Domain Managers, and VMware Telco Cloud Service Assurance sizing, refer VMware Telco Cloud Service Assurance Sizing Sheet.
- Refer VMware Telco Cloud Service Assurance Domain Manager Performance Benchmarking and Sizing Guidelines document for planning the SAM deployment.
| Number of Managed Devices (includes routers, switches, hosts, VMs, CNFs, or pods) | Demo (750 devices) | 25 K | 50 K | 75 K | 100 K | 125 K | 150 K | 175 K | 200 K | |
|---|---|---|---|---|---|---|---|---|---|---|
| TKG Management Cluster | Control Plane Node/Worker Node | 3 VMs across all footprints. | ||||||||
| 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 for demo footprint and 4vCPU per VM for 25k and higher footprint. | ||||||||||
| 4 GB RAM per VM for demo footprint and 16 GB RAM per VM for 25k and higher footprint. | ||||||||||
| 50 GB local disk | ||||||||||
| Worker Node | 4 VMs | 9 VMs | 14 VMs | 17 VMs | 20 VMs | 23 VMs | 24 VMs | 29 VMs | 32 VMs | |
| 16 vCPU per VM | 16 vCPU per VM | |||||||||
| 32 GB RAM per VM | 64 GB RAM per VM | |||||||||
| 100 GB local disk | 200 GB local disk | |||||||||
| AKS/EKS Workload Cluster | Worker Node | 4VMs | 9 VMs | 14 VMs | 17 VMs | 20 VMs | 23 VMs | 24 VMs | 29 VMs | 32 VMs |
| 16 vCPU per VM | 16 vCPU per VM | |||||||||
| 32 GB RAM per VM | 64 GB RAM per VM | |||||||||
| 100 GB local disk | 200 GB local disk | |||||||||
| Raw Metric Retention | 1W | 1.05 TB | 8.3 TB | 16.5 TB | 24.5 TB | 32.5 TB | 40.5 TB | 48.5 TB | 56.5 TB | 64.5 TB |
| 2W | 1.2 TB | 9.8 TB | 19.5 TB | 29 TB | 38.5 TB | 48 TB | 57.5 TB | 67 TB | 76.5 TB | |
| 3W | 1.32 TB | 11 TB | 21.9 TB | 32.6 TB | 43.3 TB | 54 TB | 64.7 TB | 75.4 TB | 86.1 TB | |
| 4W | 1.45 TB | 12.3 TB | 24.5 TB | 36.5 TB | 48.5 TB | 60.5 TB | 72.5 TB | 84.5 TB | 96.5 TB | |
| 5W | 1.59 TB | 13.7 TB | 27.3 TB | 40.7 TB | 54.1 TB | 67.5 TB | 80.9 TB | 94.3 TB | 107.7 TB | |
| 6W | 1.7 TB | 14.8 TB | 29.5 TB | 44 TB | 58.5 TB | 73 TB | 87.5 TB | 102 TB | 116.5 TB | |
| 7W | 1.85 TB | 16.3 TB | 32.5 TB | 48.5 TB | 64.5 TB | 80.5 TB | 96.5 TB | 112.5 TB | 128.5 TB | |
| Number of devices | 750 | 25 K | 50 K | 75 K | 100 K | 125 K | 150 K | 175 K | 200 K | |
| Total number of metrics every five minutes | 300 K | 10 million | 20 million | 30 million | 40 million | 50 million | 60 million | 70 million | 80 million | |
| Total number of active events | 8 K | 125 K | 250 K | 375 K | 500 K | 625 K | 750 K | 875 K | 1000 K | |
| Number of concurrent Northbound API calls | 60 | 60 | 60 | 60 | 60 | 60 | 60 | 60 | 60 | |
| Number of concurrent users | 60 | |||||||||
| Bandwidth utilization for Storage Traffic | 3.5 Mbps | 33 Mbps | 66 Mbps | 99 Mbps | 132 Mbps | 165 Mbps | 198 Mbps | 231 Mbps | 264 Mbps | |
| Total Disk IOPS (Read + Write) | 100 | 1000 | 2000 | 3000 | 4000 | 5000 | 6000 | 7000 | 8000 | |
| Number of Alarms/Analytics definitions | 10 | 10 | 10 | 10 | 10 | 14 | 16 | 18 | 20 | |
| Remediation Rule | 10 | 100 | ||||||||
Note: The following notes apply to Demo and HA-based footprints:
- The Demo footprint is for non-production deployment without HA capabilities and cannot be upgraded and incrementally scaled. Also, it does not support the backup and restore feature.
- The table shows the VMware Tanzu Kubernetes Grid management cluster sizing for deployments when a dedicated VMware Tanzu Kubernetes Grid management cluster is used for the VMware Tanzu Kubernetes Grid workload cluster in VMware Telco Cloud Service Assurance. 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, it is recommended to enable vSphere HA for VMware cluster.
- In AKS, by default, first three worker nodes can also be the control plane nodes. For the different footprints, the recommended AKS VM size template is Standard_D16s_v3.
- 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.
