vRealize Operations Manager 8.x Requirements, Sizer, and maximums
Abhijeet D
Advertisements
In this post, we will discuss about requirements for vROPS 8.0 and 8.1 requirements, vROPS Sizer tool and sizing guidelines for vRealize Operations Manager to determine the configurations used during installation and post install.
vROPS Sizer
VMware provides vROPS sizer tool to help you with sizing vROPS deployments. Recommended sizing for vRealize Operations Manager 6.5 and later can be generated by using this tool.
Once connected provide details of vROPS version you are using or planning to use and also select the option of sizing guide, basic or advanced.
Enter the details of expected inventory size for required components as per your environment on the next screen. Once entered with all details, click on view recommendations.
It provides recommendations based on input you provided about inventory items as in image below.
vROPS 8.0 and 8.1 Requirements and Maximums
The vRealize Operations Manager virtual appliance must be deployed on hosts that are ESXi 6.0 or later. For ESXi 6.5 there is requirement that ESXi 6.5 must be running with Update 1.
If you are running previous version of vROPS on older version of ESXi such as ESXi 5.5, you must upgrade the vCenter Server to versions 6.0 or 6.5, and then upgrade to vRealize Operations Manager 8.0 and later.
We may need to expand VROPS Cluster capacity once the vRealize Operations Manager instance outgrows the existing size over the period of time. In such event, we can expand the cluster by adding more nodes of similar configuration to the cluster. In VROPS Cluster, all nodes should be with same configuration in terms of resources.
Below are the details of default configurations and maximums in vROPS 8.0. While deploying vROPS, we get default configuration options as Extra Small, Small, Medium, Large, and Extra Large configurations during installation.
Appliance Configurations
Extra Small Configuration
No of vCPU:
2 vCPUs
Default Memory (GB):
8 GB
Max Memory Configuration (GB):
8 GB
vCPU:Physical core ratio for data nodes:
1:1 at scale maximums
Network latency for data nodes:
< 5ms
Network latency for agents (to vRealize Operations node or RC):
< 20 ms
Datastore latency:
Consistently < 10 ms with possible occasional peaks up to 15 ms
SmallConfiguration
No of vCPU: 4 vCPUs
4 vCPUs
Default Memory (GB): 16 GB
16 GB
Max Memory Configuration (GB): 32 GB
32 GB
vCPU:Physical core ratio for data nodes:
1:1 at scale maximums
Network latency for data nodes:
< 5ms
Network latency for agents (to vRealize Operations node or RC):
< 20 ms
Datastore latency: Consistently < 10 ms with possible occasional peaks up to 15 ms
Consistently < 10 ms with possible occasional peaks up to 15 ms
MediumConfiguration
No of vCPU: 4 vCPUs
8 vCPUs
Default Memory (GB): 16 GB
32 GB
Max Memory Configuration (GB): 32 GB
64 GB
vCPU:Physical core ratio for data nodes:
1:1 at scale maximums
Network latency for data nodes:
< 5ms
Network latency for agents (to vRealize Operations node or RC):
< 20 ms
Datastore latency: Consistently < 10 ms with possible occasional peaks up to 15 ms
Consistently < 10 ms with possible occasional peaks up to 15 ms
Large Configuration
No of vCPU: 4 vCPUs
16 vCPUs
Default Memory (GB): 16 GB
48 GB
Max Memory Configuration (GB): 32 GB
96 GB
vCPU:Physical core ratio for data nodes:
1:1 at scale maximums
Network latency for data nodes:
< 5ms
Network latency for agents (to vRealize Operations node or RC):
< 20 ms
Datastore latency: Consistently < 10 ms with possible occasional peaks up to 15 ms
Consistently < 10 ms with possible occasional peaks up to 15 ms
Extra Large Configuration
No of vCPU: 4 vCPUs
24 vCPUs
Default Memory (GB): 16 GB
128 GB
Max Memory Configuration (GB): 32 GB
128 GB
vCPU:Physical core ratio for data nodes:
1:1 at scale maximums
Network latency for data nodes:
< 5ms
Network latency for agents (to vRealize Operations node or RC):
< 20 ms
Datastore latency: Consistently < 10 ms with possible occasional peaks up to 15 ms
Consistently < 10 ms with possible occasional peaks up to 15 ms
Remote Collector Standard
No of vCPU: 4 vCPUs
2 vCPUs
Default Memory (GB): 16 GB
4 GB
Max Memory Configuration (GB): 32 GB
8 GB
vCPU:Physical core ratio for data nodes:
1:1 at scale maximums
Network latency for data nodes:
< 5ms
Network latency for agents (to vRealize Operations node or RC):
< 20 ms
Datastore latency: Consistently < 10 ms with possible occasional peaks up to 15 ms
Consistently < 10 ms with possible occasional peaks up to 15 ms
Remote Collector Large
No of vCPU: 4 vCPUs
4 vCPUs
Default Memory (GB): 16 GB
16 GB
Max Memory Configuration (GB): 32 GB
32 GB
vCPU:Physical core ratio for data nodes:
1:1 at scale maximums
Network latency for data nodes:
< 5ms
Network latency for agents (to vRealize Operations node or RC):
< 20 ms
Datastore latency: Consistently < 10 ms with possible occasional peaks up to 15 ms
Consistently < 10 ms with possible occasional peaks up to 15 ms
Below are the Objects and Metrics maximums for all possible appliance configurations like extra small, small and other deployments
Maximum number of the vRealize Application Remote Collector telegraf agents
10,000
Maximum number of the End Point Operations agents
10,000
Telegraf agents using vRealize Application Remote Collector
Small
Medium
Large
vCPU
4
8
16
Default Memory (GB)
8
16
24
Maximum Number of supported telegraf agents
500
3,000
6,000
Sizing guidelines for vRealize Operations Continuous Availability
This is a new feature available with the release of vROPS 8.0 and onwards. Continuous Availability allows the cluster nodes to be stretched across two fault domains that are placed across two different sites. Just like how we deploy vSAN stretched cluster. Continuous Availability requires an equal number of nodes in each fault domain and a witness node which is placed in a third site, to monitor and avoid split brain syndrome scenarios.
Small
Medium
Large
Extra Large
Maximum number of nodes in each Continuous Availability fault-domain
1
4
8
5
Network requirements for Continuous Availability
Between fault-domains
Between witness node and fault-domains
Latency
< 10ms, with peaks up to 20ms during 20sec intervals
< 30ms, with peaks up to 60ms during 20sec intervals
Packet Loss
Peaks up to 2% during 20sec intervals
Peaks up to 2% during 20sec intervals
Bandwidth
10Gbits/sec
10Mbits/sec
Sizing Guidelines
For information about the sizing guidelines for vRealize Operations Manager 6.x, 7.x and 8.x, access the KB articles listed in the following table:
Remember that the sizing guides are version specific, please use the sizing guide based on the vRealize Operations version you are planning to deploy.
