Translate in Your language

Wednesday, 27 April 2016

VMware vRealize Operations Manager (vROps) 6.X Architecture

VMware vRealize Operations Manager (vROps) 6 helps IT admins to monitor, troubleshoot, and manage the health and capacity of virtual environment. vRealize Operations is a suite that includes vCenter Infrastructure Navigator (VIN), vRealize Configuration Manager (vCM), vRealize Log Insight, and vRealize Hyperic.

vCenter Operations Manager 6 (vROps) is designed to use a common platform that uses the same components in all type of deployment architecture. The following diagram shows the five major components of the Operations Manager architecture:

Product/Admin UI:

In vROps 6, the UI is devided into two components—the Product UI and the Admin UI. 

The vROps 6.0 Product UI is present on all nodes with the exception of nodes that are deployed as remote collectors. 

Primary purpose of the Product UI is to make GemFire calls to the Controller API to access data and create views, such as dashboards and reports. Product UI is simply accessed via HTTPS on TCP port 443.

The Product UI is the main Operations Manager graphical user interface. Product UI is based on Pivotal tomcat Server and can make HTTP REST calls to the CaSA (Cluster and Slice Administrator) for administrative tasks.  

The Admin UI is a web application hosted by Pivotal tomcat Server and is responsible for making HTTP REST calls to the Admin API for node administration tasks.

The collector is responsible for processing data from solution adapter instances. collector uses adapters to collect data from various sources and then contacts the GemFire locator for connection information of one or more controller cache servers to send the collected data.

The controller manages the storage and retrieval of the inventory of the objects
within the system. The queries are performed by leveraging the GemFire MapReduce
function that allows you to perform selective querying. This allows efficient data
querying as data queries are only performed on selective nodes rather than all nodes.

Analytics is the runtime layer for data analysis. The role of the analytics process is to track the individual states of every metric and uses various forms of correlation to determine whether there are problems.

Analytics layer is responsible for the following tasks:

• Metric calculations
• Dynamic thresholds
• Alerts and alarms
• Metric storage and retrieval from the Persistence layer
• Root cause analysis
• Historic Inventory Server (HIS) version metadata calculations and
relationship data

The Persistence layer, is the layer where the data is persisted to disk. The layer primarily consists of a series of databases that replace the existing vCOps 5.x filesystem database (FSDB) and PostgreSQL combination.

Sharding is the term that GemFire uses to describe the process of distributing data
across multiple systems to ensure that computational, storage, and network loads
are evenly distributed across the cluster.

1 comment:


Popular Posts This Week