Resource requirements for multi-host deployments

Zenoss strongly recommends a minimum of 3 hosts for all production deployments of Zenoss Service Dynamics. Most environments require more than 3 hosts. Development or testing deployments can be single-host deployments.

CPU and memory requirements

The following table provides CPU and memory requirements for hosts in the types of Control Center resource pools that a typical Resource Manager deployment uses. For more information about pool types, see Key Resource Manager concepts.

Resource pool type Host requirements
Count Resources Comments
Master pool 1 4 CPU cores

16GB main memory

The amount of storage required for application data varies greatly.
Resource Manager pool 2+n 8 CPU cores

32GB main memory

To support failover or additional services, more than two hosts is preferred.
Collector pool n+1 4 CPU cores

8GB main memory

Collector services do not need DFS; remote pools can use higher connection timeout settings.

Control Center master host storage

The Control Center master host virtual machine requires a total of 7 virtual hard disks. The following table identifies the purpose and size of each disk.

Purpose Size
1 Root (/) 30GB
2 Swap 16GB
3 Temporary (/tmp) 16GB
4 Docker data 50GB
5 Control Center internal services data 50GB
6 Application data 200GB
7 Application data backups 150GB

On vSphere hypervisors, the disks are created when the OVA is installed. On Hyper-V hypervisors, the disks must be created manually.

Control Center delegate host storage

Control Center delegate host virtual machines requires a total of 4 virtual hard disks. The following table identifies the purpose and size of each disk.

Purpose Size
1 Root (/) 30GB
2 Swap 16GB
3 Temporary (/tmp) 16GB
4 Docker data 50GB

On vSphere hypervisors, the disks are created when the OVA is installed. On Hyper-V hypervisors, the disks must be created manually.