nodes

I was asked recently if there were any materials I could direct people to with regards to expanding existing vROps deployments. I did a brief search on the web to see what material was “out there” on how to perform what is a straight forward task. To my surprise very little came up. So I have decided to create this guide with all the things you need to consider when you are going to either expand or need to remove a node from one of your active vROps deployments.

For the last few months and certainly very recently (at the London VMUG meeting) I have had the chance to talk to peers and #vExperts and share “war stories” with regards to vRealize Operations Manager. What has become a consistent theme in all the stories is just how much compute resources vROps requires when you “go big” and not just what is clearly defined in the sizing spreadsheet. For example some of the large deployments I have either been involved in or heard about (to monitor upwards and beyond of 30000 VMs) required the deployment of Large vROps nodes.