vrealize operations

Integrating vROps with vRA 8 using Workspace One Auth Source Product Version - vRealize Automation 8.x Why integrate vROps with vRA 8? vRealize Automation can work with vRealize Operations Manager to perform advanced workload placement, provide deployment health and virtual machine metrics, and display pricing. So what is the problem? When configuring the integration, you will input the vROps URL and it will also ask you to input a username and password of the service account you wish to use.

I did a quick search online and could not find a collated list so, by way of a quick summary from all the VMworld 2018 announcements and comments my good friend and PM for vRealize Operations Sunny Dua has made, I have collated a list of what we can expect to see in the next iteration of vROps (7.0). The list is in no order of interest or importance, some of the mentioned improvements have been long standing requests so enjoy and get hyped (I know I am).

When vRealize Lifecycle Manager 1.2 was released recently, I was keen to get it installed in my lab, since I maintain several vRealize Automation deployments for development and testing, as well as performing upgrades. With vRLCM I can reduce the administrative overhead of managing the environments, as well as easily migrate content between environments (I’ll be blogging on some of these cool new features soon). However, I hit a snag when I began to import my existing environment - I couldn’t get the vCenter data collection to run.

Something that has come up with customers recently is why and when old data is cleaned up from your vROps instance. I will make the assumption that you have your data retention set to 6 months but the process is the same whether the value is less than or greater than 6 months. When data reaches and or goes beyond the age threshold set in the global settings it will be cleaned away by a daily process “Old Data Cleaner”.

This was as I expected, the busiest day sessions wise for me. There was so much good stuff I had to be a little ruthless on what I wanted and or needed to attend while also wanting to get into the solutions exchange. Also at the end of the day the customer appreciate party was scheduled so that was something I was looking forward to a great deal (Hint - Kaiser Chiefs)

[vRealize Operations Manager 6.6, which was recently released by VMware. We started with an overview of all the cool new stuff and then drill down into individual areas. We then jumped into a Live Demo as usual to see the new features in action. We would highly appreciate if you could spend 30 seconds to fill up this quick and simple survey to provide us your feedback. You can also request topics of your choice through this survey.

Those of you used to using vSphere on a regular basis will already be aware of the hardening guide for ESXi and vSphere but what about vROps? If the vROps appliance needs to be hardened there is already a VMware provided guide and tool to accommodate. Secure configuration guide - http://pubs.vmware.com/vrealizeoperationsmanager-61/topic/com.vmware.ICbase/PDF/vrealize-operations-manager-61-secure-configuration-guide.pdf “The documentation for Secure Configuration is intended to serve as a secure baseline for the deployment of vRealize Operations Manager.

One of the great new features included in vROps is High Availability, however when you look a little closer at how it works careful thought needs to go into whether you want to use it or not. I have had several discussions with my colleagues on the subject about whether you should or should not enable it in any given deployment of a vROps cluster. So the following are my thoughts and bullet points for you to consider when faced with same dilemma.