tests/kvmfornfv_cyclictest_hostenv_guestenv.yaml

   1 ---
   2 # Sample benchmark task config file
   3 # Measure system high resolution by using Cyclictest
   4 #
   5 # For this sample just like running the command below on the test vm and
   6 # getting latencies info back to the yardstick.
   7 #
   8 # sudo bash cyclictest -a 1 -i 1000 -p 99 -l 1000 -t 1 -h 90 -m -n -q
   9 #
  10
  11 schema: "yardstick:task:0.1"
  12
  13 scenarios:
  14 -
  15   type: Cyclictest
  16   options:
  17     affinity: 1
  18     interval: 1000
  19     priority: 99
  20     loops: 600000
  21     threads: 1
  22     histogram: 90
  23   host: kvm.LF
  24   runner:
  25     type: Duration
  26     duration: 1
  27     interval: 1
  28   tc: "kvmfornfv_cyclictest-node-context"
  29   sla:
  30     max_min_latency: 100
  31     max_avg_latency: 600000
  32     max_max_latency: 1200000
  33     action: monitor
  34   setup_options:
  35     rpm_dir: "/opt/rpm"
  36     script_dir: "/opt/scripts"
  37     image_dir: "/opt/image"
  38     host_setup_seqs:
  39     - "host-setup0.sh"
  40     - "reboot"
  41     - "host-setup1.sh"
  42     - "host-install-qemu.sh"
  43     - "host-run-qemu.sh"
  44     guest_setup_seqs:
  45     - "guest-setup0.sh"
  46     - "reboot"
  47     - "guest-setup1.sh"
  48
  49 context:
  50   type: Node
  51   name: LF
  52   file: /opt/scripts/pod.yaml
  53   env:
  54      type: script
  55      prefix:  yardstick.benchmark.scenarios.compute
  56      teardown:
  57      -
  58        kvm:
  59          script: disable_trace.bash