There are two proposed components to StorPerf:

1. the Manager, which contains the results database, a web UI for review, the CLI to create VMs and test attached storage
2. the Agent, which is installed on the VM and runs the actual performance test against the attached storage

The manager receives commands to start performance tests. It then:

• Creates a Heat Template with size of VM, and storage requirements.
  • this is where the underlying type of storage is specified
  • simultaneous runs can be specified and multiple VMs created
  • ssh key supplied so manager can control it after launch
  • network plumbing to be on same subnet as manager
  • not sure if we will allow OS to be chosen or will have image ready with FIO already baked in
• Deploys template
  • Heat creates VM, network port
  • Cinder allocates storage
  • Heat connects network and storage to VM
• Once StorPerf Agent VM is ready:
  • Copies StorPerf agent software
  • Remotely starts execution with test configuration

StorPerf Agent:

• Pre-conditions storage using FIO
• Starts FIO test run with parameters supplied
• Gathers periodic metrics from FIO
• Forwards metrics to Carbon for DB storage

Graphite can be used to:

• View test results in progress
• Historically report on tests saved in Carbon
• Extract test run data

StorPerf Manager:

• Extract baseline run from Graphite
• Compare to current run
• Report pass/fail to Yardstick/QTIP