Versions Compared

Version Old Version 1 New Version Current
Changes made by

Paul Le Guen de Kerneizon

eroussy

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Monitoring test profiles: these tests are used to only monitor various system and SEAPATH sensors (ex: CPU/memory/disk usage, bandwidth consumption, etc.).

  • Benchmark test profiles: these tests are used to measure the performance of a particular system or SEAPATH components (ex: CPU, memory, disk, VM migration...).

Name

Test profile type

Tested components

Compatible machines and infrastructure

Test arguments

Generated results

Needed dependencies

cpu

Benchmark

CPU, virtualization stack

Hypervisor and VMs, all SEAPATH configuration

  • time_to_run: duration of the test (default 60s)

PDF report with sysbench score

sysbench

disk

Benchmark

Disk, distributed storage

Hypervisor and VMs, all SEAPATH configuration

  • time_to_run: duration of the test (default 60s)

  • size: size of data to be wrote (default 1M)


By default, the test uses the time based option.

PDF report with fio score

fio

vm_migration

Benchmark

CPU, disk

Hypervisor and VMs, only SEAPATH cluster configuration

  • resource: name of the VM to migrate (default guest0)

  • iterations: number of VM migration (default 5)

PDF report with average VM migration time

A working SEAPATH cluster using crm as resource manager

rt_tests

Benchmark

CPU, real time configuration

Hypervisor and VMs, all SEAPATH configuration

  • time_to_run: duration of the test (default 60s)

  • reference_test: SEAPATH latency reference test1

PDF report with plot by cores of latencies

Cyclictest

gnuplot

process_monitoring

Monitoring

/

Hypervisor and VMs, all SEAPATH configuration

processes_to_monitor: list of processes to monitor separated by a coma ,. If not provided, only shows the three most CPU consumer processes

PDF report with process CPU consumption per CPU core

network_monitoring

Monitoring

/

Hypervisor and VMs, all SEAPATH configuration

interface: network interface to be monitored (default team0)

PDF report with average and max bandwidth for RX and TX

vnstat

1: The test takes about 5 hours to complete.

...

Test scenarios are formatted in YAML file format and are located in vars/test_scenarios directory.

Name

Test scenario description

Test profiles arguments

disk_cpu_rttest

Disk, CPU and RT tests run simultaneously, process_monitoring monitoring

Disk and CPU test profiles: 120s test

vmmigration

5 iterations of VM migration

VM migration test profile: 5 iterations of guest0 VM
processes_to_monitor: crm and qemu-system-x86 processes

disk

Disk test, with process_monitoring and network_monitoring monitoring

size: 1G

idle

Idle test with process_monitoring monitoring

time_to_run: 1800

Installation

Requirements

Localhost machine

...

Each test-profiles arguments have default values, which can be overwritten in the test scenario.

test_scenario_name