Configure an optional SMTP server to activate email service for reports and for notification messages when a problem occurs. Administrative alerts occur when vCenter Operations Manager detects a problem with one or more of its components and cannot collect data from the monitored objects.
To configure the Email Notification first we should have access to the vRops admin Portal, from the main menu click on Content,
Out of the box, the Default Policy in vRealize Operations is set to use an Allocation Capacity planning model for most Object types.
In many other circumstances, a better starting point would be to apply a Demand based policy for most Object types and resource dimensions.
We will go through how to make this changes and what difference they will make to the Capacity Planning Analysis results.
Allocation:
Uses simple mathematics to do capacity planning. Works only on containers & Datastores Reduces the CPU, VM or DISK SPACE allocated to a VM from the total available. The total available can be hypothetically increased by using Over commitment Ratios
CPU Demand: Amount of CPU resources an object would have used if there was no contention Demand (Mhz) for CPU comes from vCenter Metrics. Derived as Percentage by vROps Demand can be Greater than , Equal to or Less than Usage
Memory Demand: Derived by vROps by using Active Memory + Overheads
Network Demand: Derived by vROps using network usage per vNic as a percentage of the bandwidth.
Disk Demand: Sum of the queued IO commands and the outstanding IO commands as a percentage of the overall capacity. It is derived by vROps.
There is a very common question will come across your mind,
What is the resources needed for my vRealize Operations Manager? how many Cluster nodes?
Let me simplify this with straight forward Answer, It is depend !!
During the wizard of the installation in Part-1 we selected the Deployment Configuration (Small) which will take resources 4 vCPUs and 16 GB RAMs, this configurations can support up to 2000 VMs
For Extra configurations use the following sizing table guide from VMware,
Notes:
and metrics that are collected from adapter data sources. Example of objects include a virtual machine, a host, a datastore for a VMware vCenter adapter, a storage switch port for a storage devices adapter, an Exchange server, a Microsoft SQL Server, a Hyper-V server, or Hyper-V virtual machine for a Hyperic adapter, and an AWS instance for a AWS adapter. References:
Knowledge Base - Sizing the vRealize Operations Manager Cluster
vRealize Operations Manager 6.0.1 Sizing Guidelines (2109312)
|
| ||||||
|
| ||||||
|
|
|
In this post we will go through the architecture of the product, also we we will go through step by step how to configure the high availability for the vRops by creating Master Replica for the master node of the cluster,
vRealize operations Manager Design Architecture considerations and Node Types:
The Master node is the initial node in your vRealize Operations Manager cluster. if we are planning to have a Single-Node Cluster so the administration and the data are on the same master node, if we are planning to have a Multi-Node Cluster which will include one Master and one or more data nodes,
Enabling the Master Replica Node is the key of having the High availability for the vRealize Operations Manager, if we have a problem occurred with the Master node for any reason, a failover to the replica node will occur automatically,
Data nodes are the additional cluster nodes that allow you to scale out vRealize Operations Manager to monitor larger environments. to perform collection and analysis. On the Larger deployments usually adapters are only installed and configured on data nodes,
On the large environment we might have a distributed deployment across sites, then we will need a remote collector node that can navigate firewalls and reduce bandwidth across data centers, Remote collectors only gather objects for the inventory, without storing data or performing analysis,
Now lets start our deployment of the Master Replica Node to provide the high availability, We will start with deploying another vRops OVF same as we did earlier, We will access it through web URL access,
Select (Expand an Existing Installation)
I spent years in IT industry in most days and in most Modern companies I found that they consider the documentation a burden not a solution for their problems .
Some of the reasons I had seen to avoid Making or updating the documentation :
This is one of the Most common words in IT industry you keep hearing ,ROI study and ROI for this project . in this Short post I will try to make it simple by using example from the IT industry not just by using the raw info .
it’s a performance measure to determine the efficiency
Example :
you want a new servers for building a new private cloud used as a sandbox (Testing) .
Step 1: getting the cost of Accruing those servers ( servers cost + software licenses cost + cost of implementing those ) you will end up with a number (Ex. $100,000 )
Example
you need to run 10 applications (LOB) shall you proceed with Private cloud ?
(the servers cost is used as example only )
each physical server costs $15K (16GB Ram ,6Cores , 1TB Storage )
Now you sum up to 150K
Now we got to the cloud part by using the cloud you removed the physical boundaries with will lead to Higher utilization (I am using the same HW in the physical example)
