Javelin CLI utilities has been deprecated in Jan 2016
- Ie4ab5258946271a16e96a070abeedfafa5423714
which is over 6 months of Tempest deprecation period.
This patch removes the javelin CLI and corresponding doc/sample
files etc.
Change-Id: Ia59d3e81f245f29a7bf0f56b690586dfc55f16a0
Adds new command subunit-describe-calls, documentation,
and unittests.
subunit-describe-calls is a parser for subunit v1 & v2 streams to
determine what REST API calls are made inside of a test and in what
order they are called.
Later commits will add additional functionality relating to request
& response headers & body data along with a stdout output option and
stdin input.
Change-Id: I468d0d3e3b6098da95a81cc86d9bdd1b47ee1f03
This commit adds a new run command to the unified cli endpoint. The
intent here is for tempest to control it's own run story. This
implements the basic runner and selection functionality to use the
command, however it's not necessarily the end state of the command.
The functionality in this patch is just a starting point to add the
command and the basic functionality needed. It is starting with a
limited feature set with the intent to add additional, more complex
functionality in self contained patches after the command exists.
Co-Authored-by: David Paterson <davpat2112@yahoo.com>
Co-Authored-by: Stephen Lowrie <stephen.lowrie@rackspace.com>
Partially-Implements bp tempest-run-cmd
Depends-On: I09299043e536521d48dbe10632621138e3a366e0
Change-Id: I24588b5c00d005320e8719cf82b5dd95662572cf
Create a consistent means for creation and management of Tempest
workspaces.
Creates a file located at ~/.tempest/workspaces.yaml which stores existing
workspaces.
Available subcommands: list, register, rename, move, remove
bp centralized-workspaces
Change-Id: I9595e3ba809e457951a0ffdf4b15f641f2fec4f4
Now that tempest_lib code is copied back into tempest, stop using
tempest_lib in tempest, and start using the copied code.
Remove the dependency to tempest_lib from requirements, and drop
the script to use tempest_lib in tempest. Add os-testr to the
test-requirements.
Partially implements bp tempest-lib-reintegration
Change-Id: I21ab5fe6349f72c98ac9f960a29bf62e813f8b1b
Leave existing endpoint for now as to not disrupt existing
workflows and deprecate next cycle.
Add deprication warning for old usage.
Change-Id: I9db27a853184126a7f751800bc8cacd7dd4e40fd
Implements: blueprint tempest-cli-improvements
Leave existing endpoint for now as to not disrupt existing
workflows and deprecate next cycle.
Added deprecation message for old entry point.
Change-Id: If8afab441f51e5cf0f3bf1e2b95d76b2c1d0c474
Implements: blueprint tempest-cli-improvements
Also disable ability to run script in stand-alone mode. So users need to
use 'tempest run-stress' instead.
Change-Id: I3effd1b71b2375f75a11f5924205741be0903361
Implements: blueprint tempest-cli-improvements
Also disable ability to run script in stand-alone mode so
users will use 'tempest cleanup' instead.
Change-Id: I2119acd402b0985d4a81c85501ce7265f782d37b
Implements: blueprint tempest-cli-improvements
This commit fixes a few things in the tempest docs. First it fixes all
of the sphinx warnings and enables fail on warn to ensure we're using
valid sphinx everywhere. It also adds a link from the configuration
guide to the sample config file.
Change-Id: I3ad645a6bbfa46b4498e1732410743e46d6eb0cb
The absolute path causes failures when installing in a virtual
environment, not having root privileges.
This change solves the installation in a virtual environment,
but it does not fix yet the tempest init workflow when installing
into a virtual environment.
Partially-fixes bug #1480389
Change-Id: Iddefb8db77ffe35a84fb35b6f9e7e823de4ab45f
This commit adds a new 'tempest init' command to the unified cli.
This command tempest init will be the first step of the new workflow
for running tempest. It is used to initilize a local working directory
to run tempest from. The idea being you can setup different local
working dirs for different tempest envs to test against several
different clouds.
The basic idea for this new workflow after installing tempest is
something like:
1. mkdir tempest-newcloud
2. cd tempest-newcloud
3. tempest init
4. edit local config file
5. tempest run
The next step after this is to start working on the 'tempest run'
command. (which will include the hooks for the tempest plugin
interface) But, until that is added a test runner can be called
directly inside a local tempest working directory.
Partially Implements bp tempest-cli-improvements
Change-Id: I572267e61ba8ca86f92299e174864a7a89597207
This commit adds the necessary bits to tempest's setup.cfg file to
instruct pbr on how to make sure that the sample config files and
a /etc/tempest dir get setup when installing tempest. In the new
cli workflow it is expected that by default /etc/tempest will exist
as a source for local working dir configs.
Partially implements: bp tempest-cli-improvements
Change-Id: I2bf93f6789601caaebdfb85ac2b9f34b82f87980
This commit adds the basic framework to tempest for a unified modular
CLI endpoint using cliff. As of right now this entry-point doesn't
really do anything but exist. It will be expanded in the future first
all the existing commands will be refactored to be used through this.
Secondly a new interface and workflow for running tempest will be
created on top of this.
Co-Authored-By: Matthew Treinish <mtreinish@kortar.org>
Change-Id: I1ff8d22c120dbc81d812f1f107db7c2d9b15a505
Implements: blueprint tempest-cli-improvements
Implemented:
https://etherpad.openstack.org/p/accounts-yaml-generation
This tool can be used for creating user accounts for
tempest runs in concurrency.
Basic usage:
./account_generator.py
--tag foo
-c tempest.conf
--os-username <admin-name>
--os-password <admin-password>
--os-tenant-name <admin-tenant>
-r <concurrency count>
--with-admin (optional)
accounts.yaml
Change-Id: I3c313787b0f6f69edcc5ad16c6c186226f619692
This commit adds references explaining the current state of python 3.4
and tempest to the readme, pkg metadata, and adds an etry to the tox
envlist for running the unit tests on python 3.4.
Change-Id: I9c1e3cdf53dbae723a9fee67ad96932709d2305f
PBR handles setting the version based on the git tags, so we don't need
to do this in the setup.cfg anymore.
Change-Id: I3c12f54682b58c9eea5b40fa2c34979775c0b827
With the tempest-3 tag being published to signify the end of xml
testing in tempest we need to bump the working version to tempest-4
to indicate that the next tag will be 4.
Change-Id: I1fd12cb3e20692c60daa4eb19c6d876b00318d56
The tempest-2 tag has been pushed to mark the start of support for the
kilo release. This commit bumps the version to 3 to show the current
working tag number. Tempest-3 when it is tagged after the kilo release
will mark support for icehouse, juno, kilo, and the 'L' release based
on the current stable maintenance schedule.
Change-Id: If401356d441ef3dc82a5b8069168c4dd71c8b3d8
Also fixes tempest reported bug with old generator in oslo-incubator,
when identical options are registered in different groups.
Change-Id: I274f48503c1b61ca09cabc8d8c50245ba1059943
Closes-bug: 1282887
With change f8b816af0751b10cc20b0ab456ca334150fcdf5f we started
packaging binaries using pbr entry points. The run_stress.py script
previously lived in tempest.stress, howver since it is intended to be
run as a binary the proper place for it is now tempest.cmd and using
an entry-point it will be easier to run it outside of the tempest
tree.
Change-Id: I96b2c7915875f4f9d7869b8728bf2c6f6ccbeec9
Create a new tool which can create and verify a set of resources to
be used in place of the existing javelin tooling in grename.
This currently can create:
tenants, users, objects, images, servers
And can verfiy:
users, objects, servers
A sample resources.yaml file is included.
Follow on patches will handle the additional create / verify, as well
as destroy operations, and unit tests to meta test the script beyond
the normal javelin runs. However at this point it is useful enough to
consider adding to Tempest to being putting this into grenade.
Part of blueprint:javelin2
Change-Id: I33f1901802c92a2eda2eeb2c225bc7f60d1a186c
Since adopting branchless we've moved to a different "release" model
were we just tag the tree at set points. We're using an incrementing
integer to name these tags. Since the first tag, 1 was pushed to
correspond with the start of branchless tempest. The current working
tag is 2.
Change-Id: I93be84da9bf2a09e9ca9c2f4231f1a4a75da3af9
This commit moves the verify_tempest_config script from the tools dir
to tempest.cmd and adds a pbr entry point for the script. This means
that the script will in effect be a packaged binary for tempest.
Partially implements bp config-verification
Change-Id: I75b9743a8117d55c6c445db05eb39404b5708624
I have checked the author of other projects. Most of them are just
'OpenStack'. And OpenStack QA is not suitable for the author because
many development members contribute to Tempest. And author-email is not
proper email address recently. It is deprecated now.
Change-Id: I0f7405d107bf40d4781acb0e4b4a5db20d7606e4
Universal is used to identify pure-Python module(by bdist_wheel). For
these, it is sufficient to build a wheel with _any_ Python ABI version
and publish that to PyPI (by whatever means).
Change-Id: Ib15e61ce3edf6f2694795167c85d40457bf11292
This commit moves switches tempest from the d2to1 version of pbr and
move to the latest version of pbr. However, there is a bug with
build_spinx so it doesn't work with a doc version set so that section
is removed from the doc conf.py.
Change-Id: I4fe14eb2b2e81132f8fa99936a031176b38c437b
The bin/tempest script was just an out of date copy of run_tests.sh.
There is no reason to keep 2 copies of the same script around so this
commit just removes the copy in bin.
Change-Id: I91bacade03d0b503d9c729b76048aa67f5f209fa
This change adds an rst file for every tempest module, with the
'automodule' macro.
The root of the API documetation will be in the 'API and test cases'
section on the main page.
https://review.openstack.org/39427
Change-Id: I4065a24328dc85bb158b15bdfddb10ee0839916b
This is a first bit of experiment to get a doc tree for tempest
that will publish our doc content to the web as part of a larger
QA doc guide.
Update some of the base READMEs to be a little more accurate,
now that we're going to be pushing them to the web.
Added tox [venv] to ensure that docs get built
Change-Id: Id54e8fbc1d884525087630106e17b37dc1206cc9
This conflicts with testtools and causes nose failures leading to lost
traceback information.
Part of blueprint grizzly/testtools
Change-Id: I131da4d2d2a965a4c4286c493f05980f27acd78d
* Allows a tenant/user to be created by the base test
class, allowing isolation of the tests. The base
compute test case class now controls what users
and tenants get created for the test case
* Moves identity admin stuff into appropriate directory
* Removes _multiprocess_shared_ to force setUpClass to
run for every test case.
* Adds setup.cfg for use with openstack.nose_plugin
* run_test.sh refactoring to make running smoketests easier
Change-Id: I3ea4c44a8c194d7ae2833b5443df7678924bcd5d