In one of our recent discussions, he mentioned about the install base of vRealize Operations Standard Edition across various customers he has worked with. He was absolutely correct in pointing out that there are a number of installations of vRealize Operations Manager on Standard License edition which have either been stand alone purchases or has been bought by customers as a part of the vSphere with Operations Manager. He also mentioned that while the Advanced and Enterprise editions of vROps give some fantastic features around customization of Dashboards, Reports etc. vROps Standard has pretty much everything to offer to an organization who wants to get on the journey of monitoring their Virtual Infrastructure with tools which understand virtualization. In a nutshell, someone who is still stuck in the primitive world of using tools which were invented for physical servers into the virtualization environment, even vROps standard edition can bring in features which can give them an insight into the deep and wide world of Virtual Environments.Here are the things you can achieve:-
1- Powerful data visualization with out of the box Dashboards, Views & Reports.
2- Automated Remediation of issues using the Automated Actions Framework.
3- Customized Groups and customized Performance Monitoring and Capacity Planning Policies.
4- Use of Projects for Capacity Modelling.
5- Workload Balancing across Clusters for improved workload performance and efficient utilization of resources.
6- Configuration and Compliance Manager for vSphere which includes vCenter, ESXi hosts and VM Containers.
Now that is a long list of things which you can do with the basic license edition, Now let us look at how you can make sure that you can operationalize the Standard Edition of vROps in your environments through a simple checklist.
- Get someone in your team to OWN the vROps setup for installation, configuration, customization, maintenance & upgrades.
- Deploy the latest version of the vROps appliance.
- Connect vROps to at least one instance of vCenter and validate data-collection.
- Configure user in vCenter with appropriate rights for this connection.
- Define users to have role-based access to vROps. Do NOT use the default ‘vcenter’ or ‘admin’ users.
- Create at least 2 users with ‘administrative’ and ‘read-only’ privileges.
- Create custom groups for your key applications in production. Define and assign policies to appropriate groups. Do NOT use the default policy AS-IS without understanding implications
- Create at least 2 custom policies – ‘Production’ and ‘Non-Production’
- Configure alerts and notifications. Define who should receive what type of alerts and configure appropriate out-bound notification. Start with basic alerts around CPU/memory/disk/network related alerts for VMs, CPU/memory contention related alerts for hosts and capacity/performance related alerts for data-stores.
- Configure scheduled reports to be sent to relevant users. Key reports such as idle, powered-off, over-sized and under-sized VMs should be analyzed on a monthly basis and sent to relevant stakeholders Unless these reports are actioned, you will not be able to reclaim waste.
- Plan capacity for new requirements. Use projects feature to validate availability of capacity for new demand and also to forecast upcoming capacity in terms of a new hardware purchase.
- Validate vSphere hardening guidelines. Use vROps to ensure your vSphere hosts are in compliance using Alert-Based Compliance.
Share & Spread the Knowledge!!
Great article ….
LikeLike
Very good article sunny��
LikeLike