d889d2ef26
The pre-install operations may fail, yet that failure is not elevated to the user. This masks the failure and makes early package install issues difficult to troubleshoot. If the basic pre-install script fails, the charm should not proceed to later hooks as the requirements may not be met. Hashbangs for bash should specify -e (errexit) on all of the pre-install bash scripts. Change-Id: I3a404f8a4d1be24e3a16e8240ebe72371579f528 Closes-bug: #1815243 Partial-bug: #1815231 |
||
---|---|---|
.. | ||
actions | ||
hooks | ||
lib | ||
reactive | ||
templates | ||
tests | ||
unit_tests | ||
.testr.conf | ||
README.md | ||
actions.yaml | ||
config.yaml | ||
copyright | ||
icon.svg | ||
layer.yaml | ||
metadata.yaml | ||
test-requirements.txt | ||
tox.ini |
README.md
Overview
Tempest is a set of integration tests to be run against a live OpenStack cluster. Tempest has batteries of tests for OpenStack API validation, Scenarios, and other specific tests useful in validating an OpenStack deployment.
The Tempest Charm can be deployed into a new or existing Juju model containing an OpenStack deployment to execute sets or subsets of Tempest tests.
Usage
NOTICE: At this time, the Tempest charm is in development and is in a proof-of-concept alpha state.
Development and related discussion occurs on the freenode #openstack-charms irc channel.
TLDR: Deploy the built charm and relate it to keystone and openstack-dashboard. See config.yaml as annotated.
More docs to come as this matures.
Executing the run-tempest action:
juju run-action tempest/0 run-tempest
Contact Information
See the OpenStack Charm Guide or discuss on Freenode IRC: #openstack-charms