15be99ec2d
network and router are both top-level network resources and router should be represented in the yaml file both for clarity and also having router name exposed in yaml file is useful for building white list for tempest cleanup. In addition horizon also lists networks and routers as top-level network objects. Adding router to the test account output aligns with this existing pattern. Change-Id: Iddebba793a978281f698ea10c167dc0a8765d785
45 lines
1.3 KiB
Plaintext
45 lines
1.3 KiB
Plaintext
# The number of accounts required can be estimated as CONCURRENCY x 2
|
|
# It is expected that each user provided here will be in a different tenant.
|
|
# This is required to provide isolation between test for running in parallel
|
|
#
|
|
# Valid fields for credentials are defined in the descendants of
|
|
# auth.Credentials - see KeystoneV[2|3]Credentials.CONF_ATTRIBUTES
|
|
|
|
- username: 'user_1'
|
|
tenant_name: 'test_tenant_1'
|
|
password: 'test_password'
|
|
|
|
- username: 'user_2'
|
|
tenant_name: 'test_tenant_2'
|
|
password: 'test_password'
|
|
|
|
# To specify which roles a user has list them under the roles field
|
|
- username: 'multi_role_user'
|
|
tenant_name: 'test_tenant_42'
|
|
password: 'test_password'
|
|
roles:
|
|
- 'fun_role'
|
|
- 'not_an_admin'
|
|
- 'an_admin'
|
|
|
|
# To specify a user has a role specified in the config file you can use the
|
|
# type field to specify it, valid values are admin, operator, and reseller_admin
|
|
- username: 'swift_pseudo_admin_user_1'
|
|
tenant_name: 'admin_tenant_1'
|
|
password: 'test_password'
|
|
types:
|
|
- 'reseller_admin'
|
|
- 'operator'
|
|
|
|
# Networks can be specified to tell tempest which network it should use when
|
|
# creating servers with an account
|
|
|
|
- username: 'admin_user_1'
|
|
tenant_name: 'admin_tenant_1'
|
|
password: 'test_password'
|
|
types:
|
|
- 'admin'
|
|
resources:
|
|
network: 'public'
|
|
router: 'admin_tenant_1-router'
|