Source: Fling Labs
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.
- 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.
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
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.
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:
- The alignment of memory accesses on 4 KB boundaries (i.e., a memory page)
- 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.
|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).
VDSPowerCli gives you the ability to manage:
- VMware vSphere Distributed Switch
- Distributed Port Group
- Distributed Port
Source: Fling Labs
vCenter Cluster Performance Tool is a Powershell script that uses vSphere PowerCLI to obtain performance data for a cluster by aggregating information from individual hosts.
You have the following options to specify in the script.
- An “interval” of 20s or 300s. The default is 20s, and corresponds to real time statistics. 300s corresponds to the 5 min interval statistics.
- A stats query flag to obtain the list of counter IDs available on the vCenter Server. You can then pass the desired counter ID from that list to obtain Performance metrics for the cluster.
- Gathers all data of the specified interval type that is available on each host in the specified cluster
- Easy and a quick way of obtaining performance data for a vCenter cluster
- Data is saved in a CSV file, which can then easily be fed into any charting software
- A chart, in PNG format, is also generated for visualization
PowerActions integrates the vSphere Web Client and PowerCLI to provide complex automation solutions from within the standard vSphere management client.
PowerActions is deployed as a plugin for the vSphere Web Client and will allow you to execute PowerCLI commands and scripts in a vSphere Web Client integrated Powershell console.
Furthermore, administrators will be able to enhance the native WebClient capabilities with actions and reports backed by PowerCLI scripts persisted on the vSphere Web Client. Have you ever wanted to “Right Click” an object in the web client and run a PowerCLI script? Now you can!
For example I as an Administrator will be able to define a new action for the VM objects presented in the Web client, describe/back this action with a PowerCLI script, save it in a script repository within the Web client and later re-use the newly defined action straight from the VM object context (right click) menu.
Or, I as an Administrator can create a PowerCLI script that reports all VMs within a Data Center that have snapshots over 30 days old, save it in a script repository within the Web client and later execute this report straight from the Datacenter object context menu.
Or better yet, why not share your pre-written scripts with the rest of the vSphere admins in your environment by simply adjusting them to the correct format and adding them to the shared script folder.
For additional information see the video in the Video tab, or read this article.
Click to enlarge