Last month I did a blog post of a fling I often use in project phases (read it at https://www.pascalswereld.nl/post/58225706990/vmware-io-analyzer-fling). I want to blog about another fling you can use in a project and also in normal management of virtual infrastructures.
This fling is called vBenchmark and can create reports of your virtual environment with measurements of the performance of your (just to state the obvious; VMware) virtualized infrastructure. These measurements can be used to report to IT management about the benefits brought with a implementation or migration project. You can also use this in a assessment phase to baseline report your existing environment prior to making (to be beneficial) changes.
The report is targeted at IT as measurement metrics are mostly technical of art, but hey that’s what a virtualization infrastructure is made off.
Measure metrics are categorized as follows:
– Configuration: for example, how much virtual vs physical RAM is registered.
– Efficiency: for example, how is you environment utilized.
– Agility: for example, how much time do you take on average to provision a VM, or how productive can your administrators be (do not get overexcited, this is only from the infrastructure prospective 😉 ).
– Quality of Service: for example, how much downtime do you avoid by using availability features, or how much downtime have you experienced.
The environment metrics can be uploaded to a VMware server to compare (based on your license type and organisation) your metrics with the outside worlds matched peers. Your metrics will be anonymously uploaded.
You can add one or more vCenters to vBenchmark. Be sure to save your session data or you will have to do them again in vBenchmark. But you won’t have a reference data set..
vBenchmark is a OVF appliance that can be downloaded from this link: http://labs.vmware.com/flings/vbenchmark
I have downloaded vBenchmark and I will deploy vBenchmark to my test Lab. My lab environment are 3 ESXi 5.5 hosts managed by a vCenter 5.5 server appliance. There are around 4 VM’s operational so not quite the environment, but large enough to get some metrics in.
The deployment is straightforward, deploy as OVF. Add name, location, storage (deploying on VSAN) and add networks. From the OVF template the IP is defined as static, but there is no configuration.
vBenchmark actually supports IPv4 DHCP (and you can change the network settings via the appliance admin app at https://<vbenchmark>:5480/), and that’s what I’m using. Finish and power on.
After power on go to a console and set the root password. You will have to do this else you can’t access the web interface.
Open up your favorite browser and go to the system. In the startscreen you will have to add a vCenter server to vBenchmark.
After that you can select a statistics period and start adding statics.
When finished collecting you can select to include your cluster in the reports. And you are redirected to your dashboard.
From here on you can create vCenter server groups, share (upload) your metrics to included peer metrics and save your configuration for future references.