Welcome to the next episode of vRealize Operations Manager Webinar Series. This time around we will talk about the latest release of vROps released in the month of June. With this release, VMware has made drastic changes to the product and the initial reviews of the product have been great. Since I was a part of the team delivering this new release, I thought it would be a good topic to discuss in the next episode of the Webinar Series.
The Host Resources Deep Dive book by Frank Denneman and Niels Hagoort has been one of the most widely anticipated books in the VMware community - previous deep dive books by Frank (co-authored with Duncan Epping), tantalising blog posts and captivating presentations have whet the appetite for the last year or so. Having sat through some of these presentations at VMUGs and VMworld I can tell you the depth and understanding that the authors bring to the table is immense.
With the release of vSphere 6.5, VMware upped the game for vCenter High Availability (vCHA) and introduced an active/passive/witness cluster setup to provide a failover cluster for vCenter Server Appliances. The diagram below shows the architecture of the solution. Deploying vCHA can be done in two modes - “Basic” and “Advanced”. You can use Basic mode if the vCenter you want to be HA is managing the hosts it resides on - in this scenario the wizard configures your vCenter and deploys the Passive and Witness nodes for you.
[<img class=“alignright size-thumbnail wp-image-8035” src="/images/2017/03/logo.jpg" alt="" width=“150” height=“150” which vROps can provide by using various extensibility solutions. We discussed the following use cases and demonstrated them in live environments: Use Case 1 - Full-Stack vSphere Monitoring. From application to Infrastructure. Use Case 2 - Amazon RDS Workloads. Monitoring public cloud workloads with vROps. Use Case 3 - vROps Extensibility. Metrics, Logs and Costing come together along with other 3rd party extensibility options.
So very recently i had a great question from a customer regarding ways to monitor things like the temperature of host systems. Would they need a management pack or is this something vROps can do out of the box? The short answer to this is yes, but it is not immediately obvious how. There are a great many metrics that come with a vanilla build of vROps but not all of them are enabled a good example of these are the sensor metrics.
Announcing Part 2 – #vROps Webinar series 2017 – “Full Stack” monitoring with vRealize Operations Manager
As promised, vROps Webinar Series 2017 is back with the second episode of the year. Last time around we looked closely into the features of vROps 6.5 and as stated during that webinar, we will now show you how you can unlock the full capabilities of vROps using the extensibility of the platform. If you have been following the Webinar Series, by now you have a complete visibility into the capabilities of vROps, when it comes to monitoring the vSphere infrastructure.
If you spend a good amount of time in vROps either at your place of work or with customers (like me) you will likely have had to create some custom XML (metric configuration) for custom dashboards. In the past you would either use the sample/examples to get them started and then go and find the specific metric names while, this was usually quite time consuming. In recent versions of vROps however, VMware have introduced a “builder” to help you properly format and slect the corect adapters/adapterkinds and metrics.
I already have a vRealize Orchestrator workflow to shutdown my workload cluster. What I want to do is trigger that by a voice command from Alexa. Now, the correct and proper thing to do here would be to create a new Alexa skill, write the function in Lambda and connect that to my Orchestrator REST API and execute the workflow. That way I could control the “intents” and “utterances” and have verbal feedback.
Time to share the recording of the first episode of the vROps Webinar Series 2017. This time around, Sunny and I spoke about the latest release of vRealize Operations Manager. We spoke about almost all the new features which were introduced with this version and went into some of them in detail. Like always we rounded up the session with Live Demo of the new features for our audiences. We introduced a feedback form which can be used to provide your feedback in general and also request topics on which you would want us to focus this year.
While there is a reasonable amount of information about how HA works in vROps I have found there is still some confusion as to how HA actually works with vROps or rather what are the benefits and perhaps more importantly the cost for enabling the feature. HA is a great feature and in my opinion should be considered seriously with any deployment (where possible). Not only does HA protect your Master node (which essentially behaves as an index for your vROps cluster and if lost will render your cluster dead unless you have a working backup of your cluster) it will also allow your cluster to tolerate a data node failure.