Noiro master rebase - #2
Open
tbachman wants to merge 34 commits into
Open
Conversation
Change-Id: I1e917b0fb64022729606de4dad7bf9df9d7bb52f
Make Plugin.get return a plugin with "default" platfrom in case of MultipleMatch and `platform is None` condition. Change-Id: I9a77c3e894d7c1eadf77dc6de8e1d9a6839202a4
This validator is one of the general one. Despite the fact, it is not directly hardcoded to OpenStack plaform, it's interface was desgined to openstack credentials and usage of it for non-openstack platforms looks ugly. This patch changes it's behaviour to check existance of the platform in the environemnt spec for main case + searchs&re-calls required_platfrom@platform_name for custom logic like checking admin/user credentials. Change-Id: I546bbd9b0e35abb30195b0f8c98756a9cce10107
Qpid was removed in Mitaka from Oslo Messaging, so we can remove all qpid related explanations. Change-Id: Ib58a5a320b2a1152ed47688c55a1ecc4e7f58835
There is a feature - for existing platforms, specifying 'existing@'
prefix is optional. This feauture doesn't work in py3 environment, it
processes the same platform twice.
Validation step includes the following code (comments are added to
describe the issue):
1 | # ``items`` method of a dict returns immutable object in python 2
2 | # environemnt, but it is mutable in python 3. It means that in
3 | # python 3 environment line #10 will extend returning values of
4 | # ``spec.items()`` with "new" key-value and loop at line #7
5 | # will try to process the same platform again.
6 |
7 | for p_name, p_spec in spec.items():
8 | if "@" not in p_name:
9 | # the next line extends spec with a new key-value pair
10| spec["existing@%s" % p_name] = p_spec
Change-Id: I6f51da8ab37a208c1358d20a7fdaf564c5292da3
Change-Id: I96e48fe51a875f4a1afad06f857c72130f7ba32d
Installing 'rally-openstack' package in our devstack plugin can simplify adoption of a new package, i.e no need to rework legacy jobs while porting custom plugins to use new package. Also, this patch removes checking for openstack samples, since it should be done in rally-openstack repo Change-Id: I3446ccd5a36cb686282e85a9ea210d1723da1fef
With Ibcb949ad98323f770bf20f144ad66b4a47c00e22 the support of stestr was added. Unfortunately, this commit included a wrong check for testr config file which is an identifier what interface should be used (testr or stestr) to launch tests, so stestr was used for all cases. Also, this patch temporary turns off verification gates, since it contains a bug related to openstack roles configuration which make tempest verifier fail. Since we are planning to remove openstack related code from the main repository, this issue should be solved in rally-openstack repository. Change-Id: I691503901c6d1c6ceed79035b0df8bd752d912bd Closes-Bug: #1777757
NOTE: the existing legacy jobs should continue working due to several applied hacks. The new home for OpenStack plugins: https://git.openstack.org/cgit/openstack/rally-openstack https://github.com/openstack/rally-openstack https://pypi.org/project/rally-openstack/ Change-Id: I36e56759f02fe9560b454b7a396e0493da0be0ab
- Modify README - Add CHANGELOG file Change-Id: I8ee5cee95278e0eb8a6462a30426cbc43d1ac9d4
Python 3.6 is installed by default in Ubuntu 18.04 LTS. Therefore, according to transition plan [1], we should have py36 testenv ready for it. [1] https://wiki.ubuntu.com/Python/Python36Transition Change-Id: Iecfa41a5e4b8c5bb614b4ea728d2840f0e714418
In process of deprecating and removing in-tree OpenSTack plugins, the proper warning message was added to make the process as friendly as possible. After these plugins were removed, the warning message become redundant. Change-Id: I429ff7e862e947ffd6ef1087f347a5d8d7494601
Change-Id: I1796182339023d4f04ed08c185ffe99835b44655
Change-Id: I91c7447916ddcc76acae3731d0ed7e86ab3757ac
Change-Id: I9054c116855446def21b611b38ac57f3fb306778
* rally task raw results include environment name and uuid which are quite informative, let's include them in the json report * elasticsearch exporter did not use environment name from the task results, it retrieved this name from database instead which is redundant. This should be fixed now. Change-Id: I475b67d248672650733f07126978a17acd5f7111
* setup proper docstring which should be used in docs * remove deprecated class Change-Id: I532d4d596df754fd7f967f9e4e02bb88c0123abc
Sometimes, expect to see the specified scenarios detailed information, for example, the task which includes many scenarios is a long information, we could query the failed scenarios via the option --filter-by. The sample: 1. query the failed scenarios rally task detailed --filter-by sla-failures 2. query the specified scenarios rally task detailed --filter-by scenarios=scenario1[,scenarios2...] Change-Id: Ie7b20e57b651c622b865d03de56b6528ea5bd440
There are 2 functional tests `TaskTestCase.test_new_report_one_uuid_one_file` and `TaskTestCase.test_new_report_one_file_with_static_libs`. There tests use the same path path for temporary results file. Depending on the order of execution, one of these tests can remove the result file of another which produces an issue. Let's do not use hardcoded paths and use just random ones. Change-Id: I124986ee83f32627699973d47c62ee706c485cc2
Change-Id: Ib4d00b40ffea91bbaaefabe1382bd0cc76888798
This adds a rally job that can be used with the noironetworks OpenStack Director/sauto installs on the noironetworks FABs.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
7 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.