NOTE – Don’t forget to mark your calendars by saving the calendar invite!! Feel free to forward the invite to anyone who might be interested. It’s open to all!!
Understanding #vROps High Availability
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. So in short what is not to like!
The important thing to remember here is the cost in terms of object/metric capacity for your vROps cluster and in turn the additional nodes and or hardware you may need to facilitate/provide for having a HA enabled vROps Cluster.
If you have deployed vROps before then I would hope you are already familiar with the VMware provided vROps Sizing Spreadsheets When you input your environment figures you will be informed of the size of nodes and number of nodes required to monitor your environment. Furthermore you can select how many months you plan to retain data and whether you will enable HA or not.
#vROps 6.5 – Two new enhancements/features I really liked
There is a lot of great new enhancements and improvements added in 6.5 but for the sake of brevity I shall highlight two that I really liked.
Flexibility to increase RAM in between node sizes
So if you are familiar with vROps you will know that when you deploy it you have “T-Shirt” sizes to choose from, Small, Medium, Large and now Extra Large (6.5). However an additional extra in 6.5 is support to increase the memory allocation of your vROps nodes, you will not require additional CPU for the node until you hit the next node size bracket. If in doubt check the sizing guide spreadsheet VMware has provided so you can be sure on what you can and cannot do.
This flexibility plus the introduction of a new Extra Large Node size will give you more choice and flexibility with your existing or future vROps deployments.
Direct integration with Log Insight
There was already some integration with Log Insight via the launch in context menu, but now you can access Log Insight from the home page and also when you are troubleshoot individual objects. From a UX perspective this is fantastic and just saves time and further cements the relationship the two products have. You will still need to configure the Log Insight Management Pack and point it to the vLI instance you wish to integrate your vROps cluster with.
#vROps Webinar 2016 : Part 5 : Design and Deployment considerations
Session Details:- In this instalment of the series, we discussed the steps and thought processes that should be used before and during the design and deployment of vRealize Operations Manager. During the session among other things we will cover the planning, core components, correct sizing, HA, clustering, DR and future growth.
Once again I would like to thank my friend and partner in this project Sunny as without him this would not be possible.
So without further ado, here is the recording for this session:
Note : It is recommended that you watch the video in HD quality for a great experience.
#vROps Webinar 2016 – Announcing Part 5 : Design & Deployment Considerations
Time to announce the next part of the year long webinar series on vRealize Operations Manager. This time around, Sunny and I thought about discussing Architecture of vROps. To some, it might sound strange as for smaller deployments you might not have to worry about Sizing and Architecture much since it is pretty simple to install and configure a small or a medium node for a small shop. However as your monitoring needs grow and you start adding solutions for monitoring data sources beyond vSphere, you would need to think about scaling up or scaling out. As your monitoring environment weaves into your incident ticketing system, you would start to see the need to HA of vROps and as you have a DR strategy for your workloads, you will start thinking about DR for your operations tools as well.