# KloudBuster Default configuration file

# Name of the image to use for all test VMs (client, server and proxy)
# The image name must exist in OpenStack and must be built with the appropriate
# packages.
# The default test VM image is named "kloudbuster_<version>" where
# <version> is the KloudBuster test VM image version (e.g. "kloudbuster_v3")
# Leave empty to use the default test VM image (recommended).
# If non empty use quotes if there are space characters in the name (e.g. 'my image')
image_name:

# Config options common to client and server side
keystone_admin_role: "admin"

# Cleanup all kloudbuster resources upon exit
cleanup_resources: True

# VM creation concurrency
vm_creation_concurrency: 5

#
# ssh access to the test VMs launched by kloudbuster is not required
# but can be handy if the user wants to ssh manually to any of them (for example
# to debug)
# public key to use to access all test VMs
# if empty will default to the user's public key (~/.ssh/id_rsa.pub) if it
# exists, otherwise will not provision any public key.
# If configured or available, a key pair will be added for each
# configured user.
#
public_key_file:

# SERVER SIDE CONFIG OPTIONS
server:
    # Flavor to use for the test images
    flavor:
        # Number of vCPUs for the flavor
        vcpus: 1
        # Memory for the flavor in MB
        ram: 2048
        # Size of local disk in GB
        disk: 20

    # Number of tenants to be created on the cloud
    number_tenants: 1

    # Number of Users to be created inside the tenant
    # For now support only 1 user per tenant
    users_per_tenant: 1

    # Number of routers to be created within the context of each User
    routers_per_user: 1

    # Number of networks to be created within the context of each Router
    # Assumes 1 subnet per network
    networks_per_router: 1

    # Number of VM instances to be created within the context of each Network
    vms_per_network: 1

    # Number of security groups per network
    secgroups_per_network: 1

    # Assign floating IP for every VM
    use_floatingip: True

    # Placement hint
    # Availability zone to use for servers in the server cloud
    # Leave empty if you prefer to have the Nova scheduler place the server VMs
    # If you want to pick a particular AZ, put that AZ name (e.g. nova)
    # If you want a paticular compute host, put the AZ and compute host names s
    # eparated by ':' (e.g. nova:tme100)
    availability_zone:


# CLIENT SIDE CONFIG OPTIONS
client:
    # Assign floating IP for every VM
    use_floatingip: True

    # Flavor to use for the test images
    flavor:
        # Number of vCPUs for the flavor
        vcpus: 1
        # Memory for the flavor in MB
        ram: 2048
        # Size of local disk in GB
        disk: 20

    # Placement hint
    # Availability zone to use for clients in the client cloud
    # Leave empty if you prefer to have the Nova scheduler place the server VMs
    # If you want to pick a particular AZ, put that AZ name (e.g. nova)
    # If you want a paticular compute host, put the AZ and compute host names s
    # eparated by ':' (e.g. nova:tme100)
    availability_zone:

    # Interval for polling status from all VMs
    polling_interval: 5

    # Tooling
    tp_tool:
        name: 'nuttcp'
        dest_path: '/usr/bin/nuttcp'
    http_tool:
        name: 'wrk'
        dest_path: '/usr/local/bin/wrk2'

    # HTTP tool specific configs (per VM)
    http_tool_configs:
        # Threads to run tests
        threads: 1
        # Connections to be kept concurrently per VM
        connections: 1000
        # Rate limit in RPS per client (0 for unlimit)
        rate_limit: 500
        # Timeout for HTTP requests
        timeout: 5
        # Connection Type: "Keep-alive", "New"
        connection_type: 'Keep-alive'
        # Interval for periodical report
        report_interval: 5
        # Duration of testing tools (seconds)
        duration: 30

    # Prompt before running benchmarking tools
    prompt_before_run: False