I was wondering about this as well. Have not tried it yet, but was told that all functionality was merged to teuthology-suite, see help:
teuthology-suite --help
usage: teuthology-suite [-h] [-v] [--dry-run] --name NAME [--base BASE]
--collections DIR [DIR ...] [--owner OWNER]
[--email EMAIL] [--timeout TIMEOUT] [-n NUM]
[-l LIMIT] [-w WORKER]
[CONFFILE [CONFFILE ...]]
Run a suite of ceph integration tests. A suite is a set of collections. A
collection is a directory containing facets. A facet is a directory containing
config snippets. Running a collection means running teuthology for every
configuration combination generated by taking one config snippet from each
facet. Any config files passed on the command line will be used for every
combination, and will override anything in the suite.
positional arguments:
CONFFILE config file to read
optional arguments:
-h, --help show this help message and exit
-v, --verbose be more verbose
--dry-run do a dry run; do not schedule anything
--name NAME name for this suite
--base BASE base directory for the collection(s)
--collections DIR [DIR ...]
the collections to run
--owner OWNER job owner
--email EMAIL address to email test failures to
--timeout TIMEOUT how many seconds to wait for jobs to finish before
emailing results
-n NUM, --num NUM number of times to run/queue each job
-l LIMIT, --limit LIMIT
limit number of jobs in loop to N
-w WORKER, --worker WORKER
which worker to use (type of machine)