-
Notifications
You must be signed in to change notification settings - Fork 119
ZFS LocalPV e2e test cases
Aman Gupta edited this page Jul 10, 2020
·
14 revisions
-
https://gitlab.openebs.ci/openebs/e2e-nativek8s/pipelines/
Kubernetes version: v1.17.2 (1 master + 3 worker_node cluster)
Application used for E2e test flow: Percona-mysql
ZFS version:
$ modinfo zfs | grep -iw versionversion: 0.8.1-1ubuntu14.4OS details:
$ cat /etc/os-release NAME="Ubuntu" VERSION="18.04.3 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04.3 LTS" VERSION_ID="18.04" HOME_URL="https://www.ubuntu.com/" SUPPORT_URL="https://help.ubuntu.com/" BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/" PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy" VERSION_CODENAME=bionic UBUNTU_CODENAME=bionic
-
Installation
- Validation of installing ZFS-LocalPV provisioner.
- Install ZFSPV controller in High Availabilty (HA) and check the behaviour of zvolume when one of the controller replica is down.
-
Volume Provisioning
- E2e test for succesfully provision and deprovision of the volume. (fsTypes: zfs, xfs, ext4 and btrfs)
- E2e test of custom-topology support for ZFSPV set via storage-class.
- E2e test for Raw-block-volume support for ZFSPV.
-
Zvolume Properties
- Verification of zvolume properties set via the storage-class.
- Modification of zvolume properties after zvolume creation i.e. at runtime (Properties: compression & dedup)
-
Volume Resize
- ZFS volume resize test. (File-system: zfs,xfs and ext4)
-
Snapshot & clone
- E2e test case for ZFS-LocalPV snapshot and clone (File-system: zfs,xfs,ext4 and btrfs)
-
Infra-chaos
- Testcase for restart of the docker runtime on node where volume is provisioned.
- Testcase for restart of kubelet services on node where volume is provisioned.
-
Upgrade Testing
- Upgrade of the ZFS-LocalPV components and verify that older volume is not impacting with any issue.
- Provision of the new volume after upgrading the zfspv-components
- Check for the parent volume; it should not be deleted when volume snapshot is present.
- Test case for the scheduler to verify it is doing volume count based scheduling.