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

Tech Preview: I/O Analyzer VMware Fling Labs

Summary

VMware I/O Analyzer is an integrated framework designed to measure storage performance in a virtual environment and to help diagnose storage performance concerns. I/O Analyzer, supplied as an easy-to-deploy virtual appliance, automates storage performance analysis through a unified interface that can be used to configure and deploy storage tests and view graphical results for those tests.

I/O Analyzer can use Iometer to generate synthetic I/O loads or a trace replay tool to deploy real application workloads. It uses the VMware VI SDK to remotely collect storage performance statistics from VMware ESX/ESXi hosts. Standardizing load generation and statistics collection allows users and VMware engineers to have a high level of confidence in the data collected.

Please post comments and questions regarding this fling to the I/O Analyzer Community.

Features

  • Integrated framework for storage performance testing
  • Readily deployable virtual appliance
  • Easy configuration and launch of storage I/O tests on one or more hosts
  • Integrated performance results at both guest and host levels
  • Storage I/O trace replay as an additional workload generator
  • Ability to upload storage I/O traces for automatic extraction of vital metrics
  • Graphical visualization of workload metrics and performance results

New in version 1.6.2

  • Patched BASH binary to fix Shellshock vulnerability
  • Patched OpenSSL library to fix Heartbleed vulnerability
  • Added warning messages when invalid VM names are detected

You can also grab the tarball vmware-io-analyzer-1.6-vmw.oss.tgz

ESX Deployment Appliance (EDA) from VMware Solution Exchange

Source: VMware URL

Overview

EDA is an appliance dedicated to deploying ESX servers fast and easy. It has a scriptbuilder to quickly create %post-scripts so the ESX servers are not only installed very quickly, but also completely configured for direct import into vCenter.

Highlights
  • esx deployment
  • script builder
  • deploy AND configure
Description

Comment on this appliance

New in 1.05; Small update to support more installation media for the ESXi 5.x installer. also redeployed with WS9

New in 1.02; full support for ESXi 5. includes scripts for the new version and supports older hardware where the installer doesn’t recognize any local disks!

New in v0.95- Full ESXi installable scripting – new Scriptbuilder editor (should be way more intuitive)- lots of new scriptlets!New in v0.9- ESX 4 support
– Stateless ESXi 4 support
– ESXi 4 installable support
– Boot from SAN support (esx4 only)
– (Initial) console configuration

New in 0.87:
Don’t forget to download the latest patch (0.87-1) for some fixes on hostname input and more! patch 0.87-1
– editing the order of the scriptparts
– bulk creation and deletion of ESX hostnames/ip
– an fs.php page that allows for small remote updates
– ESXi support fixed again

New in 0.85:
– ESXi support (it works- just not unattended yet. hints appreciated!)
– new scriptbuilder interface. makes building scripts even easier and more accessible
– scriptpart editor. rudimentary but working nicely 😉

new in v0.81:
– samba passwords are changed now too
– user password configurable
– support for dhcp number when unconfigured
– persistent network names removed (finaly- now it always uses eth0)
– some work on the interface has been done (configuration pages)
– rebuilt the harddisk to cleanup the vmdk file (saves another 200mb)
Quick setup guide

new in v0.80: some added features:
– root password in ks.cfg now configurable from interface
– fqdn names of ESX hosts derived from hostname entry and DHCP domain
– fixed the active adapters to VSwitch script
– a stop button for DHCP
– initial dhcp configuration
– removed apparmor
– fixed some VM compatibility between workstation and esx
– complete rebuild on the bootstrapped 8.04 JeOS appliance!

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: 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.