65f0580c41
When running under tenant/user reusing mode: 1. Adding features to automatically pick the flavor; 2. Adding features to check quotas before testing; 3. Merge the server and client tenant into one; Change-Id: Ibdda7624174056d7770de02ed0813cad6db2ac05
27 lines
969 B
YAML
27 lines
969 B
YAML
# KloudBuster tenant and users files
|
|
# Usage: Pass to KloudBuster using "-l"
|
|
#
|
|
# This file contains the a list of tenants and users that will be reused by
|
|
# KloudBuster instead of creating them. This is useful when running
|
|
# KloudBuster on clouds without admin permissions.
|
|
#
|
|
# Settings in this file has higher priority than user configs. It determines
|
|
# the final count of tenants and useres that KloudBuster will use.
|
|
#
|
|
# If running under tenant/user reusing mode, KloudBuster will use *only* one
|
|
# tenant to hold the resources for both server cloud and client cloud.
|
|
#
|
|
# NOTE:
|
|
# (1) For now, we only support one user per tenant;
|
|
# (2) Under tenant/user resuing mode, all resources will be sitting under
|
|
# the same tenant, so there will be fixed *ONLY* one user for holding
|
|
# client side resources;
|
|
|
|
tenant_name: demo_tenant
|
|
server_user:
|
|
- username: demo_user_1
|
|
password: demo_user_1
|
|
client_user:
|
|
username: demo_user_2
|
|
password: demo_user_2
|