Versions Compared

Key

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

...

#
Test Summary
Steps
Expected
Status
1Verify CPU cycles/instructions upon enable/disable of perf.
  1. Get CPU cycles metric from VM.
    virsh domstats U2 --perf | grep -e cpu_cycles
      perf.cpu_cycles=3304247062191
  2. Compare CPU cycles values from virsh and write plugin (CSV).
  3. Disable  CPU cycles (virsh perf U2 --disable cpu_cycles).
  4. Enable CPU cycles metric (virsh perf U2 --enable cpu_cycles)
  5. Repeat same for CPU instructions metric.

  1. CPU cycles metric retrieved.
  2. CPU cycles metric is similar.
  3. CPU cycles metric is not updated by write plugin.
  4. CPU cycles metric is similar.
  5. Same as above for CPU instructions metric.
Pass
2Verify CPU cycles/instructions upon collectd start/stop, change interval.
  1. Get CPU metrics from VM and collectd write plugin.
  2. Stop collectd. Get CPU metrics from VM and collectd write plugin.
  3. Start collectd. Get CPU metrics from VM and collectd write plugin.
  4. Change interval in range 10-60 seconds (restart collectd).
    Get CPU metrics from VM and collectd write plugin.
  1. CPU cycles and instructions are updated and similar.
  2. CPU cycles and instructions are not updated.
  3. CPU cycles and instructions are updated and similar.
  4. CPU cycles and instructions are updated every interval set.
Pass
3Verify CPU cycles/instructions upon libvirtd start/stop, VM start/destroy.
  1. Get CPU metrics from VM and collectd write plugin.
  2. Stop libvirtd. Get CPU metrics from VM and collectd write plugin.
  3. Start libvirtd. Get CPU metrics from VM and collectd write plugin.
  4. Stop VM (virsh destroy <vm>).
  5. Start VM (virsh start <vm>).
  1. CPU cycles and instructions are updated and similar.
  2. Metric cannot be retrieved from VM.
  3. CPU cycles and instructions are updated and similar.
  4. Metric cannot be retrieved from VM.
  5. CPU cycles and instructions are updated and similar.
     
PASS 
4Verify cache misses/references upon enable/disable of perf.
  1. Get cache misses metric from VM.
    virsh domstats U2 --perf | grep -e cache_misses
      perf.cache_misses=36683
  2. Compare cache misses values from virsh and write plugin (CSV).
    tail -n1 U2/virt/perf-perf_cache_misses-2017-02-15
    1487151170.074,36389.000000
  3. Disable  cache misses (virsh perf U2 --disable cache_misses).
  4. Enable cache misses metric (virsh perf U2 --enable cache_misses)
  5. Repeat same for cache references metric.

  1. Cache misses metric retrieved.
  2. Cache misses metric is similar.
  3. Cache misses metric is not updated by write plugin.
  4. Cache misses metric is similar.
  5. Same as above for cache references metric:
    perf.cache_references=1815957
    1487151170.074,1795347.000000
PASS
5Verify cache misses/references upon collectd start/stop, change interval.
  1. Get cache metrics from VM and collectd write plugin.
  2. Stop collectd. Get cache metrics from VM and collectd write plugin.
  3. Start collectd. Get cache metrics from VM and collectd write plugin.
  4. Change interval in range 10-60 seconds (restart collectd).
    Get cache metrics from VM and collectd write plugin.
  1. Cache misses/references are updated and similar.
  2. Cache misses/references are not updated.
  3. Cache misses/references are updated and similar.
  4. Cache misses/references are updated every interval set.
PASS
6Verify cache misses/references upon libvirtd start/stop, VM start/destroy.
  1. Get cache metrics from VM and collectd write plugin.
  2. Stop libvirtd. Get cache metrics from VM and collectd write plugin.
  3. Start libvirtd. Get cache metrics from VM and collectd write plugin.
  4. Stop VM (virsh destroy <vm>).
  5. Start VM (virsh start <vm>).
  1. Cache misses/references  are updated and similar.
  2. Metric cannot be retrieved from VM.
  3. Cache misses/references  are updated and similar.
  4. Metric cannot be retrieved from VM.
  5. Cache misses/references  are updated and similar.
PASS
7Verify disk metrics upon collectd start/stop, change interval.
  1. Get disk number of operations/bytes read/write metrics from VM and collectd write plugin.
    virsh domblkstat --human Ubuntu-QA had [ | grep -e operations -e bytes]
    tail -n4 disk_octets-hda-2017-02-15
    tail -n4 disk_ops-hda-2017-02-15
  2. Stop collectd. Get disk metrics from VM and collectd write plugin.
  3. Start collectd. Get disk metrics from VM and collectd write plugin.
  4. Change interval in range 10-60 seconds. Get disk metrics from VM and collectd write plugin.
  1. Disk operations/bytes are updated and similar.
  2. Disk operations/bytes are not updated.
  3. Disk operations/bytes are updated and similar.
  4. Disk operations/bytes are updated every interval set.
PASS
8Verify disk metrics upon libvirtd start/stop, VM start/destroy.
  1. Get disk number of operations/bytes read/write metrics from VM and collectd write plugin.
  2. Stop libvirtd. Get disk metrics from VM and collectd write plugin.
  3. Start libvirtd. Get disk metrics from VM and collectd write plugin.
  4. Stop VM (virsh destroy <vm>).
  5. Start VM (virsh start <vm>).
  1. Disk operations/bytes are updated and similar.
  2. Disk operations/bytes cannot be retrieved from VM.
  3. Disk operations/bytes are updated and similar.
  4. Disk operations/bytes cannot be retrieved from VM.
  5. Disk operations/bytes are updated and similar.
PASS
9Verify interface metrics upon collectd start/stop, change interval.
  1. Get interface statistic from VM and collectd write plugin.
    virsh domifstat Ubuntu-QA vnet0; ls | grep if_.*vnet0 | xargs -i -t tail -n4 {}
    (files are: if_dropped-vnet0-2017-02-15; if_errors-vnet0-2017-02-15; 
    if_octets-vnet0-2017-02-15; if_packets-vnet0-2017-02-15)
  2. Stop collectd. Get interface statistic from VM and collectd write plugin.
  3. Start collectd. Get interface statistic from VM and collectd write plugin.
  4. Change interval in range 10-60 seconds (restart collectd).
    Get interface statistic from VM and collectd write plugin.
  1. Interface statistic are updated and similar.
  2. Interface statistic are not updated.
  3. Interface statistic are updated and similar.
  4. Interface statistic are updated every interval set.
PASS
10Verify interface metrics upon libvirtd start/stop, VM start/destroy.
  1. Get interface statistic from VM and collectd write plugin.
  2. Stop libvirtd. Get interface statistic from VM and collectd write plugin.
  3. Start libvirtd. Get interface statistic from VM and collectd write plugin.
  4. Stop VM (virsh destroy <vm>).
  5. Start VM (virsh start <vm>).
  1. Interface statistic are updated and similar.
  2. Interface statistic cannot be retrieved from VM.
  3. Interface statistic are updated and similar.
  4. Interface statistic cannot be retrieved from VM.
  5. Interface statistic are updated and similar.
    vnet0 rx_bytes 2098
    vnet0 rx_packets 32
    vnet0 rx_errs 0
    vnet0 rx_drop 0
    vnet0 tx_bytes 1402
    vnet0 tx_packets 15
    vnet0 tx_errs 0
    vnet0 tx_drop 0

    tail -n1 if_dropped-vnet0-2017-02-15
    1487172921.637,0,0
    tail -n1 if_errors-vnet0-2017-02-15
    1487172921.637,0,0
    tail -n1 if_octets-vnet0-2017-02-15
    1487172921.637,2098,1402
    tail -n1 if_packets-vnet0-2017-02-15
    1487172921.637,32,15

PASS

 

11Verify memory metrics upon collectd start/stop, change interval.
  1. Get memory metrics from VM and collectd write plugin.
    virsh domstats Ubuntu-QA | grep balloon ; ls | grep memory | xargs -i -t tail -n3 {}
    (files are: memory-actual_balloon-2017-02-15; memory-last_update-2017-02-15; memory-rss-2017-02-15; memory-swap_in-2017-02-15; memory-total-2017-02-15)
  2. Stop collectd. Get memory metrics from VM and collectd write plugin.
  3. Make changes to memory configuration (virsh setmem Ubuntu-QA --size 2097152 --live).
  4. Start collectd. Get memory metrics from VM and collectd write plugin.
  5. Change interval in range 10-60 seconds (restart collectd).
    Get memory metrics from VM and collectd write plugin.
  1. Memory metrics are updated and similar.
  2. Memory metrics are not updated.
  3. Memory rss, actual metrics are updated in VM. No changes observed in write plugin.
  4. Memory metrics are updated and similar.
  5. Memory metrics are updated every interval set.

Notes: (see HAA-1517 for details).


  1. Maximum allowed memory is not dispatched by libvirt 3.1.0.
  2. Both memory-actual_balloon and memory-total may return same value.
 

FAIL

Internal JIRA filed

12Verify memory metrics upon VM start/destroy.
  1. Get memory statistic from VM and collectd write plugin.
  2. Stop VM (virsh destroy <vm>). Change max memory limit (virsh setmaxmem Ubuntu-QA --size 4194304).
  3. Start VM (virsh start <vm>). Get memory statistic from VM and collectd write plugin.
  1. Memory metrics are updated and similar.
  2. Memory total metrics updated in configuration but not updated by collectd write plugin.
    virsh domstats Ubuntu-QA | grep balloon.maximum
  3. Memory total metrics updated in VM and collectd write plugin.
PASS

...