right now, users have to always pass --machine-type when scheduling a
run, when not specified, command fails with no machine type specified
error.
Instead of failing, we can have `default_machine_type` which in our case
should pick smithi, specified in /etc/teuthology.yml
Signed-off-by: Deepika Upadhyay <dupadhya@redhat.com>
doc = """
usage: teuthology-suite --help
- teuthology-suite [-v | -vv ] --machine-type <type> --suite <suite> [options] [<config_yaml>...]
- teuthology-suite [-v | -vv ] --machine-type <type> --rerun <name> [options] [<config_yaml>...]
+ teuthology-suite [-v | -vv ] --suite <suite> [options] [<config_yaml>...]
+ teuthology-suite [-v | -vv ] --rerun <name> [options] [<config_yaml>...]
Run a suite of ceph integration tests. A suite is a directory containing
facets. A facet is a directory containing config snippets. Running a suite
teuthology.log.setLevel(logging.DEBUG)
if not conf.machine_type or conf.machine_type == 'None':
- schedule_fail("Must specify a machine_type")
+ if not config.default_machine_type or config.default_machine_type == 'None':
+ schedule_fail("Must specify a machine_type")
+ else:
+ conf.machine_type = config.default_machine_type
elif 'multi' in conf.machine_type:
schedule_fail("'multi' is not a valid machine_type. " +
- "Maybe you want 'plana,mira,burnupi' or similar")
+ "Maybe you want 'gibba,smithi,mira' or similar")
if conf.email:
config.results_email = conf.email