Master host CPU and RAM resources

You can create a multi-host or single-host deployment of Control Center, on real or virtual hosts.

Zenoss recommends that all production deployments include one Control Center master host and two or more delegate hosts. In this configuration, the master host runs in its own, separate resource pool, and runs only Control Center internal services. Delegate hosts run application services in other resource pools.

For multi-host deployments, the master host typically requires 4 real or virtual CPU cores and 16GB RAM. Very large multi-host deployments may require 8 CPU cores, but no additional RAM.
For single-host deployments, the master host requires a minimum of 8 real or virtual CPU cores and 64GB RAM. Actual CPU and RAM requirements depend on application load.

Warning

An under-resourced master host cannot function properly. Deploy Control Center and Resource Manager on a master host that meets or exceeds the minimum requirements.

Master host storage areas

A Control Center master host requires the following storage areas:

Root

Size: Depends on configuration
Type: XFS file system (typically)
Mount point: /
Resource: One or more block devices or partitions, or one or more LVM physical volumes.
Preparation: None. The file system is created when the operating system is installed.

Docker temporary

Size: 10GB
Type: XFS file system (typically)
Mount point: /tmp
Resource: One or more block devices or partitions, or one or more LVM physical volumes.
Preparation: Depends on configuration. Typically, additional space is allocated for the root filesystem, but a separate real or logical partition may be used. The Control Center installation procedures include instructions to link the Docker temporary directory to /tmp.

Swap

Size: 12GB to 16GB
Type: swap
Mount point: None
Resource: One or more block devices or partitions, one or more LVM physical volumes, or a special file on the root filesystem.
Preparation: Depends on configuration.

Docker data

Size: 50GB
Type: LVM thin pool
Mount point: None
Resource: One or more block devices or partitions, or one or more LVM physical volumes.
Preparation: None. The installation procedures include steps for creating the thin pool.

Control Center internal services data

Size: 50GB
Type: XFS file system
Mount point: /opt/serviced/var/isvcs
Resource: One or more block devices or partitions, or one or more LVM physical volumes.
Preparation: None. The installation procedures include steps for formatting the resource.

Control Center audit logging

Size: 10GB (default)
Type: XFS file system
Mount point: /var/log/serviced
Resource: One or more block devices or partitions, one or more LVM physical volumes, or a remote file server that is compatible with Linux.
Preparation: Depends on configuration. Typically, additional space is allocated for the root filesystem. For more information, see Control Center audit logging.

Application data

Size: 200GB suggested. The size should be twice as large as the base device, which determines the size of tenant virtual devices.

Warning

The ratio of application data stored in the thin pool to the total amount of storage in the pool should always be 50%. When the amount of available space is less than double the amount of total storage, the snapshot feature is prone to failure.
Type: LVM thin pool
Mount point: None
Resource: One or more block devices or partitions, or one or more LVM physical volumes.
Preparation: None. The installation procedures include steps for creating the thin pool.

Application data backups

Size: 150GB suggested. The size should be at least 150% of the size of the base device, or a minimum of 150GB, whichever is greater.

Note: For large environments, this size should be much greater. Individual backup files can be 100GB each, or more. - Type: XFS file system, or a Linux-compatible file server - Mount point: /opt/serviced/var/backups - Resource: One or more block devices or partitions, one or more LVM physical volumes, or a remote file server that is compatible with Linux. Note: When the storage for backups and Control Center internal services data use the same physical device, resource contention can cause failures during backup and restore operations. For optimal results, use separate physical devices. - Preparation: None. The installation procedures include steps for formatting or mounting the resource.

The following example shows the disk configuration of a Control Center master host.

## lsblk -ap --output=NAME,SIZE,TYPE,FSTYPE,MOUNTPOINT
NAME                                                   SIZE TYPE FSTYPE      MOUNTPOINT
/dev/fd0                                                 4K disk
/dev/sda                                              29.3G disk
└─/dev/sda1                                           29.3G part xfs         /
/dev/sdb                                              48.8G disk
└─/dev/sdb1                                           48.8G part LVM2_member
  ├─/dev/mapper/docker-docker--pool_tmeta              900M lvm
  │ └─/dev/mapper/docker-docker--pool                 42.2G lvm
  │   ├─/dev/mapper/docker-8:1-42048-7a049d85cad6c      45G dm   xfs         /var/lib/docker/devicemapper/mnt/7a049d85cad6c
  │   ├─/dev/mapper/docker-8:1-42048-0f93eb8de36bb      45G dm   xfs         /var/lib/docker/devicemapper/mnt/0f93eb8de36bb
  │   ├─/dev/mapper/docker-8:1-42048-d84939118b6de      45G dm   xfs         /var/lib/docker/devicemapper/mnt/d84939118b6de
  │   ├─/dev/mapper/docker-8:1-42048-2daa75d92947e      45G dm   xfs         /var/lib/docker/devicemapper/mnt/2daa75d92947e
  │   ├─/dev/mapper/docker-8:1-42048-e7277d3081955      45G dm   xfs         /var/lib/docker/devicemapper/mnt/e7277d3081955
  │   ├─/dev/mapper/docker-8:1-42048-e91db5ccdcf21      45G dm   xfs         /var/lib/docker/devicemapper/mnt/e91db5ccdcf21
  │   ├─/dev/mapper/docker-8:1-42048-99104ce4a2d39      45G dm   xfs         /var/lib/docker/devicemapper/mnt/99104ce4a2d39
  │   └─/dev/mapper/docker-8:1-42048-a29f148212846      45G dm   xfs         /var/lib/docker/devicemapper/mnt/a29f148212846
  └─/dev/mapper/docker-docker--pool_tdata             42.2G lvm
    └─/dev/mapper/docker-docker--pool                 42.2G lvm
      ├─/dev/mapper/docker-8:1-42048-7a049d85cad6c      45G dm   xfs         /var/lib/docker/devicemapper/mnt/7a049d85cad6c
      ├─/dev/mapper/docker-8:1-42048-0f93eb8de36bb      45G dm   xfs         /var/lib/docker/devicemapper/mnt/0f93eb8de36bb
      ├─/dev/mapper/docker-8:1-42048-d84939118b6de      45G dm   xfs         /var/lib/docker/devicemapper/mnt/d84939118b6de
      ├─/dev/mapper/docker-8:1-42048-2daa75d92947e      45G dm   xfs         /var/lib/docker/devicemapper/mnt/2daa75d92947e
      ├─/dev/mapper/docker-8:1-42048-e7277d3081955      45G dm   xfs         /var/lib/docker/devicemapper/mnt/e7277d3081955
      ├─/dev/mapper/docker-8:1-42048-e91db5ccdcf21      45G dm   xfs         /var/lib/docker/devicemapper/mnt/e91db5ccdcf21
      ├─/dev/mapper/docker-8:1-42048-99104ce4a2d39      45G dm   xfs         /var/lib/docker/devicemapper/mnt/99104ce4a2d39
      └─/dev/mapper/docker-8:1-42048-a29f148212846      45G dm   xfs         /var/lib/docker/devicemapper/mnt/a29f148212846
/dev/sdc                                              15.6G disk
└─/dev/sdc1                                           15.6G part swap        [SWAP]
/dev/sdd                                              15.6G disk
└─/dev/sdd1                                           15.6G part xfs         /tmp
/dev/sde                                              48.8G disk
└─/dev/sde1                                           48.8G part xfs         /opt/serviced/var/isvcs
/dev/sdf                                             149.2G disk
└─/dev/sdf1                                          149.2G part xfs         /opt/serviced/var/backups
/dev/sdg                                             195.3G disk
└─/dev/sdg1                                          195.3G part LVM2_member
  ├─/dev/mapper/serviced-serviced--pool_tmeta          1.8G lvm
  │ └─/dev/mapper/serviced-serviced--pool            172.3G lvm
  │   └─/dev/mapper/docker-8:1-33639769-33l4GP          90G dm   ext4        /exports/serviced_volumes_v2/a9hil5o55iy266s5l
  └─/dev/mapper/serviced-serviced--pool_tdata        172.3G lvm
    └─/dev/mapper/serviced-serviced--pool            172.3G lvm
      └─/dev/mapper/docker-8:1-33639769-33l4GP          90G dm   ext4        /exports/serviced_volumes_v2/a9hil5o55iy266s5l
/dev/sr0                                              1024M rom