DefinIT

#vROps 6.5 – Two new enhancements/features I really liked

So vROps 6.5 has been out for around a month now and I finally have a little while to write a post on what I personally really like.

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.

 

Increasing the Java Heap size for vRealize Orchestrator Client (7.x)

vRealize OrchestratorBack in January 2015 I wrote an article on how to modify the Java heap settings for the vCenter Orchestrator client when working with very large workflows. Since vRealize Orchestrator 7.x has been released, we no longer have an installable client, just a Java WebStart file (.jnlp) that you run, or a package that you can download – but nothing that installs.

Note that none of this is official or supported by VMware as far as I know – it’s the results of my experimentation which has shown some performance improvement by increasing the configured memory pool. Use it at your own risk! (more…)