Adding and removing #vROps 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.
Why would you want to add a node?
- Your environment has grown in size to the extent your existing vROps cluster is too small. (very typical)
- Your PoC build is now required (for whatever reason) in production.
- You need to load balance admin/user access to the vROps UI and therefore need more nodes. (unusual but I have seen this)
Know the Limits (correctly size your clusters)
So how do you size your cluster to suit your environment needs? (you don’t want to go too large, but you definitely do not want to be undersized.)
You will be glad to know this is not a painful thing to work out and VMware have done most of the work for you by creating a very useful sizing guide (spreadsheet)
DNS DNS DNS, did I mention DNS? Make sure your new node has a DNS entry (and reverse lookup)
vROps relies on DNS (if you use VMware products regularly this will not be a new thing to you) if you have not already got DNS records in place for your vROps cluster get it done. vROps will not play nice if you get problems in this area and you have more than just one node.
Make sure the node you will add is using the same version as the existing cluster.
You can check the version by logging into the vROps instance and clicking the “about” button on the top right corner of the vROps UI.
If you are going to add a node, make sure it is the same size as the existing nodes. A quick check in the vSphere client will help you see how the existing nodes are sized.
You will be in an unsupported configuration if you try to mix and match your node sizes in a cluster.
- Extra Small – 2x vCPU – 8GB Memory
- Small – 4x vCPU – 16GB Memory
- Medium – 8x vCPU – 32GB Memory
- Large – 16x vCPU – 48GB Memory
Deploying a node and adding it to your cluster
Once you have determined the correct node size go ahead and deploy the OVA (I am assuming you are deploying the appliance but the same rules apply to a windows deployment) and then start the VM up for the first time.
Go to the FQDN or IP address of your new node in your preferred web browser.
You will be presented with the following
Click “Expand an Existing Installation”
On the above screen click next.
Lots of boxes to fill in now, give your node a friendly name (does not affect DNS) and set the node type to Data.
Enter the FQDN of your Master Node and click validate.
Check the box to accept the certificate.
Enter the admin password for vROps and click next.
Everything is now set, just click finish.
The node will now go through the process of being added to the cluster
The browser page will refresh and jump to a new page (likely prompting you regarding certs if you are using self signed) and you will then be presented with a view of the vROps cluster.
After a good while you will see the option to complete the process, click “Finish Adding New Node(s)” A pop up dialogue will appear, click OK.
You will see the node firing up while the process completes
After a while you will be taken to the normal vROps login page, enter your admin creds and go to administration and then to cluster management and you will see your new node up and running and a member of the cluster.
Nice and easy eh?
Removing a node safely from an existing vROps Cluster
Important notice – this process will restart your vROps cluster.
If the node you want to remove is the Replica node you will need to disable HA first and then go ahead with the following steps.
Login to vROps on the admin URL. (not the node you are going to remove)
Select the node you want to remove FIRST
Then click the green and red “take node offline” button.
Give a reason (think of something sensible for auditing purposes)
Notice the node is now “not running”
Click the red cross to remove the node from the cluster.
Read the warning, check the box and click yes.
The cluster will begin to remove the node.
Cluster then restarts.
As you can see the data node has disappeared and the cluster is restarting.
That’s basically it, once the cluster is online you are good to go.