Skip to content
This repository was archived by the owner on Aug 16, 2021. It is now read-only.

TestStrategy.md

Latest commit

 

History

History
92 lines (88 loc) · 4.51 KB

TestStrategy.md

File metadata and controls

92 lines (88 loc) · 4.51 KB

Pre-requisities

  • settings at cinder.conf
  • enable_v1_api=false
  • enable_v2_api=false
  • enable_v3_api=true

Positive Test Scenarios

  • check the cinder-volume logs for the start timestamp (st)
  • set logging to INFO mode @ cinder.conf
  • verifying logs is also a part of test
    • if logs are not proper or are invalid then bugs should be raised
  • create volume @ openstack (os) -- verify @ os & elasticenter (ec)
  • delete volume @ os -- verify @ os & ec
  • create volume @ os -- create snapshot @ os -- verify @ os & ec
  • delete snapshot @ os -- delete volume @ os -- verify @ os & ec
  • create volume @ os -- create snapshot @ os -- create clone @ os -- verify @ os & ec
  • delete clone @ os -- delete snapshot @ os -- delete volume @ os -- verify @ os & ec
  • create clone from volume @ os -- verify @ os & ec
  • delete clone from volume @ os -- verify @ os & ec
    • check if a snapshot remains @ ec IMPORTANT
  • create volume with chap @ os -- verify @ os & es & run command (rc)
  • create volume with initiator group (ig) @ os -- verify @ os & ec & rc
  • extend volume @ os -- verify @ os & ec & rc
    • increase size
  • extend clone @ os -- verify @ os & ec & rc
    • increase size
  • increase volume IOPS @ os -- verify @ os & ec
  • decrease volume IOPS @ os -- verify @ os & ec
  • increase volume latency @ os -- verify @ os & ec
    • this feature is supported @ os but not @ ec
  • decrease volume latency @ os -- verify @ os & ec
    • this feature is supported @ os but not @ ec
  • enable grace allowed @ os -- verify @ ec & rc
  • disable grace allowed @ os -- verify @ ec & rc
  • enable compression @ os -- verify @ ec & rc
  • disable compression @ os -- verify @ ec & rc
  • enable sync @ os -- verify @ ec & rc
  • disable sync @ os -- verify @ ec & rc
  • modify noofcopies @ os -- verify @ ec & rc
  • check the scheduler logs
    • verify if the backends available capacity matches the corresponding VSMs'.
    • check if there is a suitable rc or cli
  • check the logs for any errors or warnings after the st
  • check if the INFO, ERROR, DEBUG, WARNING logs are supportable & debuggable
  • change the log level to DEBUG & re-run above cases
  • check if DEBUG logs are proper

Negative Test Scenarios

  • check the cinder-volume logs for the start timestamp (st)
  • set logging to INFO mode @ cinder.conf
  • shutdown the EC network & verify os, logs
  • shutdown EC & verify os, logs
  • provide wrong VSM name & restart & execute create volume
  • provide wrong API key & restart & execute create volume
  • provide wrong Account name & restart & execute create volume
  • do not provide VSM name & restart & execute create volume
  • do not provide API key & restart & execute create volume
  • do not provide Account name & restart & execute create volume
  • reduce the no of attempts & interval for create volume @ conf -- verify logs -- delete volume
  • reduce the no of attempts & interval for delete volume @ conf -- verify logs -- retry delete
  • create volume @ os -- delete from ec -- update IOPS @ os
  • create volume @ os -- delete from ec -- delete from os @ verify os logs
  • create snapshot @ os -- delete from ec -- delete from os & verify os logs
  • create snapshot @ os -- delete from ec -- create clone from os & verify os logs
  • create snapshot @ os -- create clone @ os -- delete clone @ ec -- delete clone @ os & verify os logs
  • create snapshot @ os -- create clone @ os -- delete clone & snapshot @ ec -- delete clone @ os & verify os logs
  • create a volume without chap - now set a wrong chap at cinder.conf - restart - create a volume @ os & verify os logs
  • delete VSM @ ec -- verify logs @ os
  • delete VSM @ ec -- create volume @ os
  • delete VSM @ ec -- delete volume @ os
  • delete VSM @ ec -- create snapshot @ os
  • delete VSM @ ec -- delete snapshot @ os
  • delete VSM @ ec -- create clone @ os
  • delete VSM @ ec -- delete clone @ os
  • remove all volumes, clones & snapshots @ os
    • remove VSM @ ec.
    • verify cinder-volume service should be in a running state.
    • verify cinder-volume service should be in a running state even after cinder-volume restart.

Migration Related Test Scenarios

  • create a KILO VM with bootable disk in a CloudByte storage backend
  • attach data disks to above KILO VM
  • migrate the KILO VM to another backend of CloudByte storage within the same OpenStack environment

Use Case Related Test Scenarios

  • create a volume & attach it to multiple instances (VM A & VM B) on the same host.
  • create files on the volume
  • detach from instance VM A
  • check the file from instance VM B
  • detach from instance VM B
  • attach from instance VM A
  • check the file from VM A