1 .. This work is licensed under a Creative Commons Attribution 4.0 International License.
2 .. http://creativecommons.org/licenses/by/4.0
3 .. (c) Huawei Technologies Co.,Ltd and others.
6 ==================================================
7 Bottlenecks Release Notes for OPNFV Danube Release
8 ==================================================
10 .. _Bottlenecks: https://wiki.opnfv.org/display/bottlenecks
16 This document describes the release notes of Bottlenecks project.
22 OPNFV release notes for Bottlenecks Docs
23 are licensed under a Creative Commons Attribution 4.0 International License.
24 You should have received a copy of the license along with this.
25 If not, see <http://creativecommons.org/licenses/by/4.0/>.
27 The *Bottlenecks software* is opensource software, licensed under the terms of the
28 Apache License, Version 2.0.
34 +----------------+--------------------+---------------------------------+
35 | *Date* | *Version* | *Comment* |
37 +----------------+--------------------+---------------------------------+
38 | Sept 22nd, 2016| 1.0 | Bottlenecks Colorado release 1.0|
40 +----------------+--------------------+---------------------------------+
41 | Feb 17nd, 2017 | 1.1 | Bottlenecks Danube release 1.0 |
43 +----------------+--------------------+---------------------------------+
44 | Mar 24nd, 2017 | 1.2 | Bottlenecks Danube release 1.0 |
46 +----------------+--------------------+---------------------------------+
47 | Mar 24nd, 2017 | 1.3 | Bottlenecks Danube release 1.0 |
49 +----------------+--------------------+---------------------------------+
54 * Documentation generated with Sphinx
66 The *Bottlenecks software* is developed in the OPNFV community, by the
73 -----------------------
75 +--------------------------------------+--------------------------------------+
76 | **Project** | Bottlenecks |
78 +--------------------------------------+--------------------------------------+
79 | **Repo/tag** | Bottlenecks/danube.1.0 |
81 +--------------------------------------+--------------------------------------+
82 | **Bottlenecks Docker image tag** | danube.1.0 |
84 +--------------------------------------+--------------------------------------+
85 | **Release designation** | Danube 1.0 |
87 +--------------------------------------+--------------------------------------+
88 | **Release date** | March 31 2017 |
90 +--------------------------------------+--------------------------------------+
91 | **Purpose of the delivery** | Danube base release |
93 +--------------------------------------+--------------------------------------+
96 -----------------------
98 +--------------------------------------+--------------------------------------+
99 | **Project** | Bottlenecks |
101 +--------------------------------------+--------------------------------------+
102 | **Repo/tag** | Bottlenecks/colorado.1.0 |
104 +--------------------------------------+--------------------------------------+
105 | **Bottlenecks Docker image tag** | colorado.1.0 |
107 +--------------------------------------+--------------------------------------+
108 | **Release designation** | Colorado 1.0 |
110 +--------------------------------------+--------------------------------------+
111 | **Release date** | September 22 2016 |
113 +--------------------------------------+--------------------------------------+
114 | **Purpose of the delivery** | Colorado base release |
116 +--------------------------------------+--------------------------------------+
118 Bramaputra Release Data
119 -----------------------
121 +--------------------------------------+--------------------------------------+
122 | **Project** | Bottlenecks |
124 +--------------------------------------+--------------------------------------+
125 | **Repo/tag** | Bottlenecks/brahmaputra.1.0 |
127 +--------------------------------------+--------------------------------------+
128 | **Bottlenecks Docker image tag** | brahmaputra.1.0 |
130 +--------------------------------------+--------------------------------------+
131 | **Release designation** | Brahmaputra 1.0 |
133 +--------------------------------------+--------------------------------------+
134 | **Release date** | February 25 2016 |
136 +--------------------------------------+--------------------------------------+
137 | **Purpose of the delivery** | Brahmaputra base release |
139 +--------------------------------------+--------------------------------------+
145 Software Deliverables
146 ---------------------
148 **Bottlenecks source code <danube.1.0>**
150 * https://gerrit.opnfv.org/gerrit/gitweb?p=bottlenecks.git;a=summary
153 Documentatiion Deliverables
154 ---------------------------
156 **Bottlenecks documentation <danube.1.0>**
158 * Release Notes: TO-DO
160 * Development Guide: TO-DO
162 Colorado Deliverables
163 =====================
165 Software Deliverables
166 ---------------------
168 **Bottlenecks source code <colorado.1.0>**
170 * https://gerrit.opnfv.org/gerrit/gitweb?p=bottlenecks.git;a=summary
173 Documentatiion Deliverables
174 ---------------------------
176 **Bottlenecks documentation <colorado.1.0>**
178 * Platformation Overview: http://artifacts.opnfv.org/bottlenecks/colorado/1.0/docs/platformoverview/index.html
179 * Configuration Guide: http://artifacts.opnfv.org/bottlenecks/colorado/1.0/configurationguide/index.html
180 * Installation Guide: http://artifacts.opnfv.org/bottlenecks/colorado/docs/installationprocedure/index.html
181 * http://artifacts.opnfv.org/bottlenecks/colorado/1.0/releasenotes/index.html
182 * User Guide: http://artifacts.opnfv.org/bottlenecks/colorado/1.0/docs/userguide/index.html
187 * In Danube, POSCA testsuite is introduced and two stress tests are implemented. Rubbos and vstf are
188 not supported in this release.
189 * In Colorado, rubbos is refactored by using puppet, which makes it quite flexible to configure with different number of load generator(Client), worker(tomcat).
190 * In Colorado, vstf is refactored by extracting the test case's configuration information.
193 Known restrictions/issues
194 =========================
196 * In Danube, Bottlenecks use Yardstick to do stress tests by iteratively calling yardstick running test cases and in the meantime increasing load.
198 * Sometimes, Yardstick just waits for the test environment preparing.
199 This cause troubles since it seams to get Yardstick into a loop to keep waiting.
200 For OPNFV CI, this loop will be automatically stopped because of the default timeout setting. However, for local testing, user should stop this loop manually.
202 * Sometimes, Yardstick will return empty test results with test flag indicating test is excuted succefully.
203 It maybe because of the environment issue or poor internet connection causing tools are not installed successfully.
205 * Sometimes, a process will go to dormancy. In this case, if a tool is installed in the SUT and its process go dormancy, we try to call it twice. Normally, it will response.
211 Test results are available in:
213 - jenkins logs on CI: https://build.opnfv.org/ci/view/bottlenecks/
215 The test results are reported to MongoDB. An example is given below.
220 "project_name": "bottlenecks",
221 "scenario": "os-odl_l2-nofeature-ha",
223 "trust_indicator": null,
224 "case_name": "posca_stress_ping",
225 "build_tag": "bottlenecks-compass-posca_stress_ping-baremetal-daily-master",
227 "pod_name": "huawei-pod2",
229 "installer": "compass",
230 "_id": "58cf4d3e32c829000a1150a8",
231 "start_date": "2017-3-9 4:33:04",
235 For more information, please refer to: https://wiki.opnfv.org/display/testing/Result+alignment+for+ELK+post-processing
240 +------------------+-----------------------------------------------+
241 | JIRA | Description |
242 +==================+===============================================+
243 | BOTTLENECK-103 | Refactoring the Bottlenecks tesing workflow |
244 +------------------+-----------------------------------------------+
245 | BOTTLENECK-135 | Avoiding docker-compose building new image |
246 | | for Bottlenecks |
247 +------------------+-----------------------------------------------+
248 | BOTTLENECK-147 | Investigting why calling remote docker client |
249 +------------------+-----------------------------------------------+
255 - WIKI project page: https://wiki.opnfv.org/display/Bottlenecks
257 - Bottlenecks jira page: https://jira.opnfv.org/projects/BOTTLENECK/issues/
259 - Bottlenecks repo: https://git.opnfv.org/cgit/bottlenecks/
261 - Bottlenecks CI dashboard: https://build.opnfv.org/ci/view/bottlenecks
263 - Bottlenecks IRC chanel: #opnfv-bottlenecks