Fling!!!! Technical Preview License: vBenchmark

Source: Fling Labs

vBenchmark

Summary

Have you ever wondered how to quantify the benefits of virtualization to your management? If so, please consider using vBenchmark. vBenchmark measures the performance of a VMware virtualized infrastructure across three categories:

  • Efficiency: for example, how much physical RAM are you saving by using virtualization?
  • Operational Agility: for example, how much time do you take on average to provision a VM?
  • Quality of Service: for example, how much downtime do you avoid by using availability features?

vBenchmark provides a succinct set of metrics in these categories for your VMware virtualized private cloud. Additionally, if you choose to contribute your metrics to the community repository, vBenchmark also allows you to compare your metrics against those of comparable companies in your peer group. The data you submit is anonymized and encrypted for secure transmission.

Key Features:

  • Retrieves metrics across one or multiple vCenter servers
  • Allows inclusion or exclusion of hosts at the cluster level
  • Allows you to save queries and compare over time to measure changes as your environment evolves
  • Allows you to define your peer group by geographic region, industry and company size, to see how you stack up

What’s new in version 1.0.2

  • Fixed bugs that prevented some customers from deploying vBenchmark appliance with vCloud Director and vCenter Server 4.0
  • Fixed a bug that caused network settings not to persist after the reboot
  • You can change the network configuration of the VM via the web interface, please point your browser to https://ip.address:5480
  • Updated VMware Tools

What’s new in version 1.0.1

  • Added a checkbox to include or exclude vCenter license keys when submitting the data to the community repository
  • The application now listens on port 443 (https), requests to port 80 will be automatically redirected to 443
  • The appliance will now prompt you to change the root password at first logon
  • Fixed bugs that prevented some customers from proceeding to the dashboard when they have ESX 3.x hosts in their cluster or are using vCenter credentials that did not have access to the full inventory
  • vBenchmark application log is now written to the VM serial port. If you are using the VMX package, the serial port output will be redirected to a file named vBenchmark.log in the virtual machine folder. If you are importing an OVA or OVF, you need to manually add a serial port device and specify a filename.

Additional Information

vBenchmark Frequently Asked Questions

Read the Frequently Asked Questions PDF

Advertisements

ESXtopNGC Plugin, from Fling Labs of course

Summary

ESXtopNGC Plugin is an enhanced, plugin-version of ESXtop for the vSphere Web Client. The plugin displays ESX server stats in new and more powerful ways by tapping into the GUI capabilities of the Web Client.

Features

  • Separate tabs for CPU, memory, network and disk performance statistics
  • Flexible batch output
  • Flexible counter selection
  • Advanced data grid for displaying stats (sortable columns, expandable rows, etc.)
  • Configurable refresh rate
  • VM-only stats
  • Embedded tooltip for counter description

esxtopNgcPlugin_500
Click to enlarge

Fling Labs! Latency Sensitivity Troubleshooting Tool

Source: Fling Labs

Summary

The Latency Sensitivity Troubleshooting Tool provides scripts and examples to troubleshoot configuration and performance problems with the Latency Sensitivity feature in VMware vSphere 5.5.

Features

  • Python script that runs on ESXi to check virtual machine and physical NIC (PNIC) configuration to monitor host, virtual machine, and PNIC performance.
  • Python program to process traces from pktcap-uw for a ping workload and print time spent in ESXi on the receive path, time spent in the virtual machine, and time spent in ESXi on the transmit path.
  • A simple C program demonstrating the trace format generated by pktcap-uw. The C program was tested on an x86_64 Linux virtual machine.
  • Example SystemTap scripts to break down ping and netperf TCP_RR latencies inside a Red Hat Linux guest. These scripts were tested on a Red Hat Enterprise Linux 6.2 virtual machine.

latsens-screen

Fling Labs: VCS to VCVA Converter

Source: Fling Labs

Summary

The VCS to VCVA Converter Appliance is the winning idea from the 2013 Fling Contest. It allows customers to migrate from Windows vCenter Server with an External Microsoft SQL Server Database to the vCenter Server Appliance with an embedded vPostgres database. The Fling migrates the vCenter database, roles, permissions, privileges, certificates and inventory service. The target appliance will run at the same IP address as the source vCenter.

Open source license

VMware-Migration_fling-0.9-ODP.tar.gz

screenshot

Fling Labs: VM Resource and Availability Service

Source: Fling Labs

This Fling enables you to perform a what-if analysis for host failures on your infrastructure. You can simulate failure of one or more hosts from a cluster (in vSphere) and identify how many:

  • VMs would be safely restarted on different hosts
  • VMs would fail to be restarted on different hosts
  • VMs would experience performance degradation after restarted on a different host

With this information, you can better plan the placement and configuration of your infrastructure to reduce downtime of your VMs/Services in case of host failures.

Please see the Instructions tab to get started.
vRasScreenshot

Fling Labs: IOBlazer – IOPS and bytes/s and IO latency and playback VSCSI traces captured on VMware ESX through the vscsiStats utility

Source: Fling Labs

Summary

IOBlazer is a multi-platform storage stack micro-benchmark. IOBlazer runs on Linux, Windows and OSX and it is capable of generating a highly customizable workload. Parameters like IO size and pattern, burstiness (number of outstanding IOs), burst interarrival time, read vs. write mix, buffered vs. direct IO, etc., can be configured independently. IOBlazer is also capable of playing back VSCSI traces captured using vscsiStats. The performance metrics reported are throughput (in terms of both IOPS and bytes/s) and IO latency.

IOBlazer evolved from a minimalist MS SQL Server emulator which focused solely on the IO component of said workload. The original tool had limited capabilities as it was able to generate a very specific workload based on the MS SQL Server IO model (Asynchronous, Un-buffered, Gather/Scatter). IOBlazer has now a far more generic IO model, but two limitations still remain:

  1. The alignment of memory accesses on 4 KB boundaries (i.e., a memory page)
  2. The alignment of disk accesses on 512 B boundaries (i.e., a disk sector).

Both limitations are required by the gather/scatter and un-buffered IO models.

A very useful new feature is the capability to playback VSCSI traces captured on VMware ESX through the vscsiStats utility. This allows IOBlazer to generate a synthetic workload absolutely identical to the disk activity of a Virtual Machine, ensuring 100% experiment repeatability.

VDSPowerCli From Fling – Powershell for the Distributed Switch

Summary

Note: The functionality of this Fling has now been introduced into a release of PowerCLI. Whenever possible, use the latest supported version of PowerCLI, which can be downloaded here.

PowerShell is a scripting language Microsoft developed to help administrators manage the Windows environment. Third parties can write their own snap-ins (dynamic linked libraries) to implement new commands, which are called cmdlets. With VDSPowerCli, users can use the cmdlets provided by PowerCLI to manage vSphere Distributed Switch(VDS).

Features

VDSPowerCli gives you the ability to manage:

  • VMware vSphere Distributed Switch
  • Distributed Port Group
  • Distributed Port