|Fetch the current configuration in JSON format.|
|Set the configuration and creates the stack in OpenStack.|
|DELETE||Deletes the stack from OpenStack and resets configuration back to default.|
|DELETE||Terminates the currently running job.|
Command line options:
- -t or –target
- -w or –workload
- -s or –nossd
- -c or –nowarm
- verbose optional Emit periodic output describing the current read and write latency, and measured IOPS.
If specified from command line, the option is in the format
–option=. For ReST, it is embedded in the URL as
target=[device or path] Optional The path to either an attached storage device (/dev/vdb, etc) or a directory path (/opt/storperf) that will be used to execute the performance test. In the case of a device, the entire device will be used. If not specified, the current directory will be used.
workload=[workload module] Optional If not specified, the default is to run all workloads. The workload types are:
rs: 100% Read, sequential data
ws: 100% Write, sequential data
rr: 100% Read, random access
wr: 100% Write, random access
rw: 70% Read / 30% write, random access
nossdoptional Do not perform SSD style preconditioning.
nowarmoptional Do not perform a warmup prior to measurements.
report=[job_id] optional Query the status of the supplied job_id and report on metrics. If a workload is supplied, will report on only that subset.
The report command returns a JSON string with the job status (
completed). If still running:
I didn't realize that you can execute commands inside a container without ssh - see docker video:
So I need to update the cli to make it easier to run canned scenarios, or at least document that it can be done this way.