test_device

Table of Contents

1. Description
2. Setup - The basics of getting started with test_device
   • What test_device affects
   • Setup requirements
   • Beginning with test_device
3. Usage - Configuration options and additional functionality
4. Limitations - OS compatibility, etc.
5. Development - Guide for contributing to the module

Description

This module contains a test device that only burns CPU and wall clock time to be used during performance testing. The two different knobs are intended to simulate connection and data processing overhead, as well as delays when waiting on a devices response.

Setup

Configure an arbitrary amount of devices using the spinner type in your device.conf. Inthe credentials you can configure extra wait times for fetching facts and retrieving resources as facts_cpu_time, facts_wait_time, get_cpu_time and get_wait_time. All times can be specified in fractional seconds.

Usage

• Create a catalog with an appropriate number of spinner resources in it.
• Set the cpu_time and wait_time as appropriate for the devices you want to emulate.
• Run puppet device to execute those catalogs.
• ???
• Profit!

Limitations

Understanding the required cpu and wait times to emulate a realistic work load is left as an exercise to the reader, as this is dependent on the mix of devices you are running.

There are currently no known bugs.

Development

PRs on github always appreciated!