Doublecloud’s Super vCenter – Part 1 Installation
Quite a bit of time has passed since new year’s and I am trying to keep up with my reading resolution, having finished the first book Systems Performance: Enterprise and the Cloud at least. I diverged a bit into some more salesy literature for now and studying for the VCAP-CMA design beta has also taken a bit of time (and some new stuff was released on the Wii U that I just can’t stay away from right now, I simply love Zelda games…).
In between the last post and now a couple of new vExpert freebies have also been released and while I ordered a couple of new shiny toys for the homelab today (Intel NUC, have been waiting for 32GB RAM models for years and now they are finally available) I though of actually taking a couple of those vExpert for a testdrive.
The topic of monitoring, Linked Mode etc. came up in the vExpert slack a while ago and one of the products mentioned to cope with those challenges was DoubleCloud’s vSearch aka “Super vCenter”.
I will do this in 2 parts, 1 will simply cover the installation as my Google skills told me nobody has shown that off so far. Part 2 will come in about 1-2 weeks when it actually has enough information collected from the lab to also show some useful information.
The deployment is rather simple. As long as you are familiar with how to deploy an OVA to ESXi you are good to go.
Everything will be configured through the OVA settings, there is no need to actually log into the appliance to change any settings. In fact it will just tell you to go to the web page for further configuration.
The initial interface looks pretty slick and does not require a manual to figure out. Simply provide the vCenter Server IP or DNS name and an account to access it. Even though an admin account can be used a read-only account is sufficient which also implies that CRUD operations are coming on a future roadmap.
Add as many vCenter Servers as you like and then simply scroll down to step 2 to finish the configuration, that is something I really would call simple.
After the initial configuration is done you will want to go to the IP of the appliance again to get to the actual log in mask and after having logged in seeing the actual dashboard. The left hand menu will help you navigate through each of the different features like health status, maps, alert monitoring etc. You might want to assign the provided license keys by clicking on the link even though Super vCenter will be running in trial mode with full functionality for a test period of a couple months, applying the trial key got rid of that red banner for me though.
And that already basically sums up all the installation and setup effort, all in all it took about 5-10 minutes to actually get this going, no manual reading was required (something I see as a requirement in 2016…) and the setup actually worked first try (also something I don’t see too often…).
I will revisit this topic in about a week or two to see what kind of statistics Super vCenter is gathering and if it helps in narrowing down root cause of faults and how it actually compares to products familiar to me (vCenter performance charts, vROps) for environment monitoring.