This document provides the release notes for Fraser 2.0 of StorPerf.

Version history

Date Ver. Author Comment
2018-06-29 Fraser 3.0 Mark Beierl  

Important notes

StorPerf has added the ability to specify the number of Cinder Volumes per agent VM to test. The name of the device that the volume is attached to has been appended to the host IP address in the metrics so that it can be tracked independently.

Summary

StorPerf is a standalone framework that uses OpenStack to measure Cinder volume performance. If desired, it can push results to the OPNFV Test Results DB, or the embedded Graphite web interface can be used to perform ad hoc queries.

This release allows for changing of stack attributes from the OpenStack CLI. Using a command such as

will change the existing stack to use 6 agents. Note that StorPerf can take up to 1 minute after the stack update is complete before detecting the new values. Please use a GET of the configurations API to test for updated values prior to submitting a new test.

The following command changes the number of volumes per agent:

Release Data

Project StorPerf
Repo/tag opnfv-6.2.0
Release designation Fraser 6.2
Release date June 29 2018
Purpose of the delivery Improvements to stack detection speed.

Version change

Module version changes

No changes to any modules.

Reason for version

  • Loading stack properties from OpenStack could take minutes or longer depending on the stack size. This version includes changes from SNAPS to take advantage of parallel OpenStack object lookups.

Features additions

  • STORPERF-239 - Add IP addresses of slaves to configurations API
  • STORPERF-245 - Change to use multithreaded SNAPS

Deliverables

Software

Known issues

  • Cirros target VMs do not always mount Cinder volumes on first boot. Sometimes a reboot of the VM is required to properly attach the Cinder volume to /dev/vdb
  • A bug in the linux kernel can prevent Cinder volumes from attaching to VMs using ARM architecture. Specifying the following properties in Glance for the ARM based image will work around this problem. Note: this will cause the device to show up as a SCSI device and therefore will be /dev/sdb instead of /dev/vdb.