This document describes the release notes of Bottlenecks project.
OPNFV release notes for Bottlenecks Docs are licensed under a Creative Commons Attribution 4.0 International License. You should have received a copy of the license along with this. If not, see <http://creativecommons.org/licenses/by/4.0/>.
The Bottlenecks software is opensource software, licensed under the terms of the Apache License, Version 2.0.
Date | Version | Comment |
Sept 22nd, 2016 | 1.0 | Bottlenecks Colorado release 1.0 |
Feb 17nd, 2017 | 1.1 | Bottlenecks Danube release 1.0 |
Mar 24nd, 2017 | 1.2 | Bottlenecks Danube release 1.0 |
Mar 24nd, 2017 | 1.3 | Bottlenecks Danube release 1.0 |
Apr 25th, 2017 | 1.4 | Bottlenecks Danube release 2.0 |
Jun 19th, 2017 | 1.5 | Bottlenecks Danube release 3.0 |
Sept 15th, 2017 | 1.6 | Bottlenecks Euphrates release 5.0 |
Nov 15th, 2017 | 1.6.1 | Bottlenecks Euphrates release 5.1 |
Apr 10th, 2018 | 1.7 | Bottlenecks Fraser release 6.0 |
May 26th, 2018 | 1.7.1 | Bottlenecks Fraser release 6.1 |
Jul 2nd, 2018 | 1.7.2 | Bottlenecks Fraser release 6.2 |
The Bottlenecks software is developed in the OPNFV community, by the Bottlenecks team.
Project | Bottlenecks |
Repo/tag |
|
Bottlenecks Docker image tag |
|
Release designation |
|
Release date |
|
Purpose of the delivery | Fraser stable release |
Project | Bottlenecks |
Repo/tag |
|
Bottlenecks Docker image tag |
|
Release designation |
|
Release date |
|
Purpose of the delivery | Fraser stable release |
Project | Bottlenecks |
Repo/tag |
|
Bottlenecks Docker image tag |
|
Release designation |
|
Release date |
|
Purpose of the delivery | Fraser stable release |
Project | Bottlenecks |
Repo/tag |
|
Bottlenecks Docker image tag |
|
Release designation |
|
Release date |
|
Purpose of the delivery | Euphrates stable release |
Project | Bottlenecks |
Repo/tag |
|
Bottlenecks Docker image tag |
|
Release designation |
|
Release date |
|
Purpose of the delivery | Euphrates stable release |
Project | Bottlenecks |
Repo/tag |
|
Bottlenecks Docker image tag |
|
Release designation |
|
Release date |
|
Purpose of the delivery | Danube stable release |
Project | Bottlenecks |
Repo/tag | Bottlenecks/colorado.1.0 |
Bottlenecks Docker image tag |
|
Release designation |
|
Release date |
|
Purpose of the delivery | Colorado stable release |
Project | Bottlenecks |
Repo/tag | Bottlenecks/brahmaputra.1.0 |
Bottlenecks Docker image tag |
|
Release designation |
|
Release date |
|
Purpose of the delivery | Brahmaputra stable release |
Bottlenecks source code
Bottlenecks documentation <fraser>
Bottlenecks documentation <euphrates>
Bottlenecks documentation <danube>
Bottlenecks documentation <colorado.1.0>
These tests cases and refactoring further enhance the capability of Bottlenecks project and let it be adaptable to different usages.
These enhancements and test cases help the end users to gain more comprehensive understanding of the SUT. Graphic reports of the system behavior additional to test cases are provided to indicate the confidence level of SUT. Installer-agnostic testing framework allow end user to do stress testing adaptively over either Open Source or commercial deployments.
Bottlenecks uses Yardstick to do stress tests by iteratively calling yardstick running test cases and in the meantime increasing load.
This cause troubles since it seams to get Yardstick into a loop to keep waiting. 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.
It maybe due to the environment issue or poor internet connection causing testing tools are not installed successfully.
Sometimes, a process will go to sleep state. In this case when a running tool go to sleep state, we try to call it twice. Normally, it will response. This applies to the traffic generator, i.e., netperf.
Test results are available in:
- jenkins logs on CI: https://build.opnfv.org/ci/view/bottlenecks/
The test results are reported to MongoDB. An example is given below.
{
"project_name": "bottlenecks",
"scenario": "os-odl_l2-nofeature-ha",
"stop_date": null,
"trust_indicator": null,
"case_name": "posca_stress_ping",
"build_tag": "bottlenecks-compass-posca_stress_ping-baremetal-daily-master",
"version": "master",
"pod_name": "huawei-pod2",
"criteria": "PASS",
"installer": "compass",
"_id": "58cf4d3e32c829000a1150a8",
"start_date": "2017-3-9 4:33:04",
"details": {}
}
JIRA | Description |
---|---|
BOTTLENECK-147 | Investigting why calling remote docker client |
BOTTLENECK-207 | Yardstick loop when executing test cases |
BOTTLENECK-208 | Yardstick empty results when executing test cases |
BOTTLENECK-209 | Sleep process when executing test cases |
- WIKI project page: https://wiki.opnfv.org/display/Bottlenecks
- Bottlenecks jira page: https://jira.opnfv.org/projects/BOTTLENECK/issues/
- Bottlenecks repo: https://git.opnfv.org/cgit/bottlenecks/
- Bottlenecks CI dashboard: https://build.opnfv.org/ci/view/bottlenecks
- Bottlenecks IRC chanel: #opnfv-bottlenecks