Eric Windisch 8454877d17 tcup default to printing documentation if run without tcup.py
There should only be one way of running tcup. To make it clear
to users that might attempt directly running the Docker image,
that they must use tcup.py, print the documentation to those
users via STDOUT. It also ensures that users get the correct
documentation for running their version of the tcup image.

Change-Id: Id18f1316c5d7ee4f64c0c2c1c6a32cfc6b648b35
2014-06-11 15:26:28 -07:00
2014-05-13 16:32:01 +02:00
2014-05-29 23:34:52 +00:00
2014-05-28 06:35:32 -07:00
2014-05-13 16:36:30 +02:00
2014-05-18 19:02:40 +02:00
2014-03-01 17:36:44 -08:00
2014-05-13 16:32:01 +02:00
2014-03-27 13:04:21 -07:00
2014-05-13 16:37:37 +02:00
2014-05-13 16:32:01 +02:00
2014-05-13 16:32:01 +02:00
2014-03-01 17:36:44 -08:00
2014-03-01 17:36:44 -08:00
2014-03-01 17:36:44 -08:00

RefStack/TCUP and Driver Test

This project support collection and publication of Community Test results for OpenStack. There are multiple components of this effort:

  • RefStack: Community-facing API for registration of interop-compliance endpoints for on-demand testing.
  • TCUP: Portable, Containerized Tempest for Community running and reporting results to RefStack
  • Driver Test

Participate

Collecting the Results > Running RefStack

RefStack is a Web UI and API used to collect and display test results. This information is used by the DefCore committee to help select must-pass capabilities.

RefStack docs

Test your Cloud and Share! > Running TCUP

TCUP (Tempest in a Container to Upload from Probe) is a portable way for community members to quickly and consistently run Tempest against private and public clouds.

TCUP docs

Description
Vendor-facing API for registration of interop-compliance
Readme 8.4 MiB
Languages
Python 57.9%
JavaScript 29%
HTML 10.4%
Shell 2.1%
CSS 0.5%