VVD 4.2 – vRealize Operations Manager

 

VMware Validated Design Architecture and Design document contains a validated model of the Software-Defined Data Center (SDDC) and provides a detailed design of each management component of the SDDC stack. The architecture of the operations management layer supports centralized monitoring of and logging data about the other solutions in the SDDC.

Operations Management layer include two models, architectures:

  1. Monitoring Architecture
  2. Logging Architecture

Monitoring architecture is defined by vRealize Operations Manager (vROPs), which tracks and analyzes the operation of multiple data sources in the SDDC by using specialized analytic algorithms. These algorithms help vRealize Operations Manager learn and predict the behavior of every object it monitors. Users access this information by using views, reports, and dashboards.

vRealize Operations Manager is available as a pre-configured virtual appliance in OVF. You can deploy the OVF file of the virtual appliance once for each node. After node deployment, you access the product to set up cluster nodes according to their role and log in to configure the installation. There are two types of deployment models:

  • Standalone node
  • Cluster of one master and at least one data node, and optionally a group of remote collector nodes

Architecture

Selection_003

For high availability and scalability, you can deploy several vRealize Operations Manager instances in a cluster to track, analyze, and predict the operation of monitored systems. Cluster nodes can have either of the following roles :

Master Node – This is essentially the first node of the cluster, required. In large-scale environments, manages all other nodes. In small-scale environments, the master node is the single standalone vRealize Operations Manager node.

Master Replica Node – is the exact copy of the master node. This is to give resiliency to the solution. *Optional. Enables high availability of the master node.

Data Node – each node which collects data in the vROps cluster is a Data Node. Data nodes have adapters installed to perform collection and analysis. Data nodes also host vRealize Operations Manager management packs.

Remote Collector Node –  used to fetch the data from a remote location into a centralized vROps cluster/node. Remote collector nodes only gather statistics about inventory objects and forward collected data to the data nodes. Remote collector nodes do not store data or perform analysis.

You can deploy two types of node groups :

  • Analytics Cluster – Tracks, analyzes, and predicts the operation of monitored systems. Consists of a master node, data nodes, and optionally of a master replica node. Typically a normal deployment of vROPs.
  • Remote Collector Group – consists of remote collector nodes, which only collects diagnostics data without storage or analysis. A vRealize Operations Manager
    deployment can contain several collector groups.

We can configure vRealize Operations Manager user authentication to use one or more of the following authentication sources:

  • vCenter Single Sign-On
  • VMware Identity Manager
  • OpenLDAP via LDAP
  • Active Directory via LDAP

vROPs is a powerful tool for integrating with third-party solutions using Management packs. Management packs contain extensions and third-party integration software. They add dashboards, alert definitions, policies, reports, and other content to the inventory of vRealize Operations Manager. You can learn more details about and download management packs from VMware Solutions Exchange.

Using VMware Validated Design, you can also implement a large-scale vRealize Operations Manager deployment across multiple regions by using the following configuration:

  • Load-balanced analytics cluster that runs multiple nodes is protected by Site Recovery Manager to fail over across regions
  • Multiple remote collector nodes that are assigned to a remote collector group in each region handle data coming from management solutions

In a multi-region SDDC, you can deploy a vRealize Operations Manager configuration that consists of validated design :

  • 3-node (medium-size) vRealize Operations Manager analytics cluster that is highly available (HA). This topology provides high availability, scale-out capacity up to sixteen nodes, and failover. Analytics cluster consists of 1 master node, 1 master replica node, and 1 data node.
  • Group of 2 remote collector nodes in each region. The remote collectors communicate directly with the data nodes in the vRealize Operations Manager analytics cluster. For load balancing and fault tolerance, two remote collectors are deployed in each region.

Selection_004

These are the values of resources for an medium-size deployment of vROPs.

(*) Metric numbers reflect the total number of metrics that are collected from all adapter instances in vRealize Operations Manager.

The design integrates solutions for compute, storage, network, cloud operations, and cloud management. A single vRealize Operations analytics cluster monitors and performs diagnostics across the SDDC by using a series of remote collectors and solution management packs.

Selection_005
vRealize Operations Design

Next article, we will cover Logging Architecture, which is defined by vRealize Log Insight.  Stay tuned !!!  🙂

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.