f161dbac04
Add examples of usage of some discover-tempest-config options, document what resources can be created and what's needed for it Change-Id: I78b499a79bc05e9c0528da573af78fd2b58df7f4 Story: 2002703 Task: 22885 Task: 22573
2.3 KiB
Usage
Before reading this page, it's recommended to go through User Guide first as the content on this site is more advanced and uses knowledge gained from the User Guide.
This page shows examples of usage of python-tempestconf
where admin credentials are required.
That means, only users with admin credentials will run discover-tempest-config
with arguments described on this page successfully.
Why admin credentials? It's because python-tempestconf
can create resources necessary for tempest execution in
order to make user's life easier.
The following resources are created only when
--create argument is used:
- flavors, to see what flavors are created, see User Guide, Flavors section
- users, to see what users are created, see User Guide, Users section
Examples
In the following example, python-tempestconf will create
all necessary resources (Flavors and Users) if they don't exist already:
$ discover-tempest-config \
--os-cloud devstack-admin \
--createpython-tempestconf can also create a minimal accounts
file when --create-accounts-file is used. It can be useful
when a user doesn't have any and wants to create it. It can be done with
one call:
$ discover-tempest-config \
--os-cloud devstack-admin \
--create \
--create-accounts-file ~/accounts.yamlThe call above will behave the same as if
--test-accounts argument was used, see here.
The generated accounts file will look similarly to this one:
$ cat ~/accounts.yaml
# A minimal accounts.yaml file
# Will likely not work with swift, since additional
# roles are required. For more documentation see:
# https://git.openstack.org/cgit/openstack/tempest/tree/etc/accounts.yaml.sample
- password: password
project_name: admin
username: adminNote
More about accounts file can be in our documentation about Usage with tempest accounts file