Today I was involved in a project to deploy vRealize Operations Manager 6.0. Before installation I read a great set of guides about whats new, the architecture, high availability and deployment models from vExpress.blogspot.in, which was very helpful to get a good understanding of the changes from 5.x to 6.x
I recommend reading those guides here:
Part 1: vCOps 5.x to vROps 6.0 – Intelligent Operations from Apps to Storage
Part 2: vRealize Operations Manager Architecture Deep-dive
Part 3: High Availability options with vRealize Operations Manager
Part 4: vRealize Operations Manager Deployment Models
We decided to go with the virtual appliance instead of using the Windows or Linux versions. This approach is easy and upgrades have historically been very easy and straightforward. During the OVF deployment you are prompted to select a deployment configuration.
This choice depends on your size of the environment and which other data sources you will configure within vRealize Operations. Before proceeding I took the time to look into sizing guidelines, if they existed and it didn’t take long to find a nice VMware kb article with recommendations and maximum configurations.
In this article VMware has also attached a nice excel spreadsheet with sizing guidelines. I recommend that you use this before installing vRealize Operations.
In this spreadsheet there is two versions you can use. The basic version is if you use vRealize Operations with vSphere-only management pack, hence your vCenter servers as the only data source. This is straightforward. You basically fill in the following options:
- High Availability = Enabled / Disabled
- Data Retention (month) = 6 (default and recommended)
- Virtual Machines = Numbers of VMs
- Hosts = Number of Hosts
- Datastores = Number of Datastores
It looks like this:
It will the give you a recommendation for which deployment configuration you should choose and how many appliances you need to deploy. It will estimate the disk capacity size and IOPS requirement, based on your input, so you know the impact of your system.
Note: Take into account that the medium node per default is configured with 200Gb of capacity for disk2, where data resides. Before turning on the VM the first time, it may be a good idea to extend disk 2, to fit your numbers for requirement. The Disk capacity and IOPS requirement is per node!
If you however will configure vRealize Operations with additional data sources, you should choose the advanced spreadsheet. In this spreadsheet you will be prompted for additional information, to calculate the sizing requirements for your environment, as depicted below:
Based on this input I was now ready to deploy the virtual appliances I needed for this environment. Remember to extend disk 2 before powering on, as it’s just easier this way.