A profile.yaml
is helpful mainly in jobs running on different versions of
OpenStack, because arguments for python-tempestconf
may differ in each
OpenStack version. Using the --profile
argument those jobs can use
a profile.yaml
file for each OpenStack version which makes the code of
those jobs much clearer and more readable, as for example they contain less if
else statements, …
Note
Apart from --deployer-input
config file which specifies content of
a tempest.conf, profile.yaml
file defines arguments which are passed
to python-tempestconf
, see CLI documentation.
Warning
If this argument is used, other arguments cannot be defined, it means, user uses either CLI arguments or profile.yaml file.
$ discover-tempest-config --generate-profile ./etc/profile.yaml
Note
The generated sample of a profile.yaml
file contains all
python-tempestconf
arguments set to their default values. That means,
that you can remove arguments you didn’t modify to keep the file simple
and more readable.
python-tempestconf
accepts both of the following inputs, so you can use
what suits you better, either strings or lists:
After you’ve created your customized profile.yaml
file, let’s say in
./etc/profile.yaml
, use it as follows:
$ discover-tempest-config --profile ./etc/profile.yaml
Except where otherwise noted, this document is licensed under Creative Commons Attribution 3.0 License. See all OpenStack Legal Documents.