Invisible Infrastructure: In-Place Hypervisor Conversion

The Most powerful Infrastructure is the Infrastructure you don’t see or interact with, in another word the “Invisible Infrastructure”

Single Interface that combined Compute, Storage, DR, Cloud connect and even the HYPERVISOR and more, we are talking about the future of the IT “Enterprise Cloud” we are talking about NUTANIX.

One of the very cool new features in the new edition of AOS 4.6 is the ability to convert the Hypervisor running in your Cluster, in this blog post we will go through the conversion from ESXI to AHV and from AHV to ESXI,

The beautiful part that every thing is automated and GUI even the Guest VMs are converted to the hypervisor target format with no effort,

Let’s start with the first step after having the NUTANIX Cluster up and running ESXI hypervisor, Click on “Convert Cluster”

Read the notes and consider the requirements then click on “AHV”

VMware vRealize Operations Manager Step by Step (Part-5) Creating vRops Email Notifications

 

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,

 

VMware vRealize Operations Manager Step by Step (Part-4) Policy Configurations (Allocation Or Demand?)

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.

Dell Acquires EMC; VMware to Remain Independent

طبعا كلنا سمعنا امبارح عن خبر بيع EMC الى DELL وطبعا لكل المهتمين بشركة VMware فيه سؤال بيطرح نفسه علينا كلنا ......

ايه مصير VMware فى الموضوع ده ؟؟

وخصوصا ان DELL عندها بعض ال Softwares اللى بتتنافس مع بعض منتجات VMware 

على سبيل المثال وليس الحصر فيه تنافس  فى الآتى:

VRealize operations and DELL Foglighr

VMware Horizon View and DELL vWorkspace

الإجابة من VMware بخصوص ده ان VMware سوف تبقى مستقلة كشركة منتجة للبرمجيات ولن يتم دمجها فى DELL software 

المصدر من موقع VMware

http://www.vmware.com/radius/dell-acquires-emc-vmware-to-remain-independent/

VMware vRealize Operations Manager Step by Step (Part-3) Sizing and requirements of the Cluster

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 !!

• how large is your environment you will monitor and analyze
• metrics you plan to collect
• number and type of resources collected
• number and type of adapters installed
• Do you have HA or no
• the duration of data retention,
• quantity of specific data points of interest, (symptoms, changes…etc.)
• and how long you need to store your data

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:

• Maximum number of remote collectors (RC) certified: 50
• Maximum number of VMware vCenter adapter instances certified: 50
• Maximum number of VMware vCenter adapter instances that were tested on a single collector: 30
• Maximum number of certified concurrent users per node (regardless of node size): 4
• If you enable High Availability (HA), then the number of the nodes will be two times more than in a non HA configuration - 8 nodes is the limit. You do not need to account for any HA overhead beyond that.
• An object in this table represents a basic entity in vRealize Operations Manager that is characterized by properties 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.
• The limitation of a collector per node: The object or metric limit of a collector is the same as the scaling limit of objects per node.  The collector process on a node will support adapter instances where the total number of resources is not more than 2,400, 5,000, and 10,000 respectively, on a small, medium, and large multi-node vRealize Operations Manager cluster.  For example, a 4-node system of medium nodes will support a total of 20,000 objects. However, if an adapter instance needs to collect 8,000 objects, a collector that runs on a medium node cannot support that as a medium node can handle only 5,000 objects.  In this situation, you can add a large remote collector or use a configuration that uses large nodes instead of small nodes.
• If the number of objects is close to the high-end limit, dependent on the monitored environment, increase the memory on the nodes.  Contact Product Support for more details.

References:

Knowledge Base - Sizing the vRealize Operations Manager Cluster

vRealize Operations Manager 6.0.1 Sizing Guidelines (2109312)

VMware vRealize Operations Manager Step by Step (Part-2) Architecture and High Availability

 

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:

• Master Node

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,

• Master Replica Node

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 Node

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,

• Remote Collector Node

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)

VMware vRealize Operations Manager Step by Step (Part-1) Overview and Installation

vRealiza operations Manager (vRops) previously called vCenter Operations Manager (vCOps) is a part from the vRealize Suite,
vRealize Suite consists of the following products:

• VMware vRealize Automation Advanced or Enterprise
• VMware vRealize Operations Advanced or Enterprise
• VMware vRealize Log Insight
• VMware vRealize Business

vRealize Suite is available with two licensing models:

• Per Processor: For on premise private cloud or virtual environments
• Per OS Instance: For public cloud workloads or workloads on physical hardware

In this post I will go through how to deploy and configure vRealize Operations Manager 6.0,
From the vSphere Client Connected to your vCenter Start by Deploying OVF Template, Download the Source, Select, Next

Review, Click Next