tempest/etc/accounts.yaml.sample
Matthew Treinish 9329985d47
Cleanup some details about the accounts files
This commit cleans up some details in the accounts.yaml sample file
and the tempest configuration guide to provide missing details about
how to create and use an accounts file. Specifically it adds more
detailed comments to the sample file about each section, and in the
config guide it removes obsolete sections and adds some missing
details.

Change-Id: Ic11335fe1215ab0625ea2308ccc75d22a284c432
Closes-Bug: #1447851
2015-04-24 09:58:18 -04:00

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'