Some config options have changed their help text like 'sqlite_db',
so run 'tox -e genconfig' to generate latest config sample file.
Change-Id: Ifad41b2e1203308c02392ad63e3e90853dbbca68
The python-fuelclient requirement conflicts with other ones.
See logs from the docker job for more details.
Change-Id: I055eaf619ae62752c5fba6d1db26c91dbbbc86cb
Since current scenario implementation transforms method to class at runtime,
it is reasonable to have class-based scenario implementation which will be
much simpler to use behind the scenes.
This class should be based on Scenario and do not break compatibility.
The only required method is run() which is actually a body of scenario.
This patch contains changes for HEAT scenarios and tests
Change-Id: I92a1b63c40a67abbe05a78ba35ca53dc73952e75
setUp will be automatically called around each
testcase, so this is to remove setUp that doing
nothing additional than super to keep code clean.
Change-Id: I33dafd4525c9815961aa55ad652bc8df20cd84d4
Hook plugins allow us to run anything at some iterations. It depends
on the plugin. There can be cases when we need to get access the task
object in plugins to retrieve, for example, credentials. So this patch
resolves the issue.
Change-Id: Ie1f8a9da16715c85b8593cffba5c21bb497a6fb0
Context and scenario to create baymodel
All Magnum scenarios will use some baymodels.
This patch sets up the Rally context to create any
baymodels needed by a scenario. All baymodels created
will be cleaned up at the end of the job.
A simple scenario is included to test a Magnum job in
Rally. Currently the scenario only lists the baymodel created
by the context, but later more user query type of actions can
be added to similate a large user base interacting with Magnum.
The job yaml file specifies the 3 bay types to be created by the
context: Kubernetes, Swarm, Mesos.
Partially-Implements: blueprint benchmark-scenarios-for-magnum
Co-Authored-By: Ton Ngo <ton@us.ibm.com>
Co-Authored-By: Spyros Trigazis <strigazi@gmail.com>
Change-Id: I0979f2461c6e33c9163e19a6d7884fe1c7967e3f
Implements blueprint class-based-scenarios
Since current scenario implementation transforms method to class
at runtime, it is reasonable to have class-based scenario
implementation which will be much simpler to use behind the scenes.
This class should be based on Scenario and do not break compatibility.
The only required method is run() which is actually a body of scenario.
Contains changes for Cinder/Volumes scenarios/tests
Change-Id: I640b88723672d60de4148bb333df88f1c7fa20e5
Implements blueprint class-based-scenarios
This patch contains changes in following modules
(both scenarios and modules):
Manila
Mistral
Monasca
Murano
Change-Id: I1df08e471b3bc7001b11849e9d0186914dbb5b82
Triggers determine when hooks should be executed.
Added event trigger.
Added utils required for implementation of hook_section spec.
implements spec: hook_section
Change-Id: I33d558468f221a7c731e4a3fd42deb4f76be671a
Since current scenario implementation transforms method to class
at runtime, it is reasonable to have class-based scenario
implementation which will be much simpler to use behind the scenes.
This class should be based on Scenario and do not break compatibility.
The only required method is run() which is actually a body of scenario.
Change-Id: I1f1ef261942bcaf7617a5f10f05a74fae35c53f2
While fix for bug #1562713 changed the way how to save verification log in
case of some issues at CLI layer, it did not fixed old saved logs. Also, it
produced one more bug - IOError trace was saved as list instead of string.
This patch fixes the way of storage IOError and add migration to fix old data
Also, we change format of verification_log to dict here
Change-Id: Iffcf066e7033acd48f1446baebe0b2e9a334449f
Related-Bug: #1562713
Since current scenario implementation transforms method to class
at runtime, it is reasonable to have class-based scenario
implementation which will be much simpler to use behind the scenes.
This class should be based on Scenario and do not break compatibility.
The only required method is run() which is actually a body of scenario.
This patch contains changes in following groups (scenarios and tests):
/senlin/
/swift/
/tempest/
/vm/
/watcher/
/zaqar/
and modules:
rally/plugins/openstack/context/vm/custom_image.py
tests/unit/test_docstrings.py
Change-Id: Ia7f33d7c279991232286b34abe199d125b92f023
As discussed at weekly meeting, we should use optional-requirements only
for small number of cases.
This patch:
- moves most of packages from optional-requirements to requirements
- make groups of packages in requirements.txt
- sorts Openstack related group of package
- describes purpose of optional-requirements
Change-Id: I24fff516588d064069bf4226adeb0ae209c16d42
Initialize following clients by keystone session:
* Nova, Neutron, Glance, Heat, Cinder, Ceilometer, Sahara,
Mistral, Manila, Ironic, Trove, Watcher
Monasca currently not support initializing through session.
Senlin initializing through sessoin is broken for now. Should be
fixed after openstack-sdk will cut release.
Change-Id: I66301e3a002a67174ef84594ac38936c4d8b9f41
Since current scenario implementation transforms method to class
at runtime, it is reasonable to have class-based scenario
implementation which will be much simpler to use behind the scenes.
This class should be based on Scenario and do not break compatibility.
The only required method is run() which is actually a body of scenario.
Following modules were redesigned:
ceilometer/meters.py
ceilometer/resources.py
ceilometer/samples.py
ceilometer/stats.py
ceilometer/traits.py
Change-Id: Ia2af282df98cb57ca8ba95cd343bd4506a474b23
It is very inconvenient and even sometimes not possible
(PEP8 restrictions for line length) to use long mock names,
so they are ignored if name if longer than
FuncMockArgsDecoratorsChecker.SHORTEST_VARIANT_LEN_LIMIT.
For example, existing name
`mock_murano_scenario__create_environment' is simplified
in this patch.
Change-Id: Ia2adf7098c60497c3b1fe5048e1145e47b56bc18
In case of empty list of events, rally raises IndexError.
It is not user-friednly and without reading code, it is hard to understand what
had happend.
Change-Id: I998614ca842aaee62b1ea4e77713f527190338ff
