blob: d80e421daf93005ce2547bbf70f7c07dabcef58b (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
|
.. This work is licensed under a Creative Commons Attribution 4.0 International License.
.. http://creativecommons.org/licenses/by/4.0
This document provides the release notes for Fraser 2.0 of StorPerf.
.. contents::
:depth: 3
:local:
Version history
===============
+--------------------+--------------------+--------------------+--------------------+
| **Date** | **Ver.** | **Author** | **Comment** |
| | | | |
+--------------------+--------------------+--------------------+--------------------+
| 2018-04-18 | Fraser 1.0 | Mark Beierl | |
| | | | |
+--------------------+--------------------+--------------------+--------------------+
| 2018-05-18 | Fraser 2.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
.. code-block::
heat stack-update StorPerfAgentGroup --existing -P "agent_count=6"
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:
.. code-block::
heat stack-update StorPerfAgentGroup --existing -P "volume_count=2"
Release Data
-------------
+--------------------------------------+--------------------------------------+
| **Project** | StorPerf |
| | |
+--------------------------------------+--------------------------------------+
| **Repo/commit-ID** | storperf/fraser.2.0 |
| | |
+--------------------------------------+--------------------------------------+
| **Release designation** | Fraser base release |
| | |
+--------------------------------------+--------------------------------------+
| **Release date** | 2018-05-18 |
| | |
+--------------------------------------+--------------------------------------+
| **Purpose of the delivery** | OPNFV Fraser release 2.0 |
| | |
+--------------------------------------+--------------------------------------+
Version change
===============
Module version changes
-----------------------
No changes to any modules.
Reason for version
===================
Features additions
-------------------
* STORPERF-242 - Allow user to change stack parameters outside of StorPerf
Bug Fixes
----------
Deliverables
=============
Software
---------
- `StorPerf master image <https://hub.docker.com/r/opnfv/storperf-master/>`_
(tag: x86_64-fraser.2.0 or aarch64-fraser.2.0)
- `StorPerf swaggerui <https://hub.docker.com/r/opnfv/storperf-swaggerui/>`_
(tag: x86_64-fraser.2.0 or aarch64-fraser.2.0)
- `StorPerf graphite image <https://hub.docker.com/r/opnfv/storperf-graphite/>`_
(tag: x86_64-fraser.2.0 or aarch64-fraser.2.0)
- `StorPerf reporting image <https://hub.docker.com/r/opnfv/storperf-reporting/>`_
(tag: x86_64-fraser.2.0 or aarch64-fraser.2.0)
- `StorPerf Http-Frontend image <https://hub.docker.com/r/opnfv/storperf-httpfrontend/>`_
(tag: x86_64-fraser.2.0 or aarch64-fraser.2.0)
Documentation
--------------
- `User Guide <http://docs.opnfv.org/en/latest/submodules/storperf/docs/testing/user/index.html>`_
Known Limitations, Issues and Workarounds
------------------------------------------
Limitations
============
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.
.. code-block:
--property hw_disk_bus=scsi --property hw_scsi_model=virtio-scsi
Test Result
===========
- `OPNFV Test Results DB <http://testresults.opnfv.org/reporting/fraser/storperf/status-apex.html>`_
|
