Skip to end of metadata
Go to start of metadata

Description

This page is to record the high level test design and test cases for HP-UX host support feature in Yoda release.

Test Environment Covered

OS version 11.31
Initiator Type FC, iSCSI 
Multipath softwarePowerPath, MPIO
Backend ArrayVMAX, XtremIO, Vplex

Hardware

Hostlglal017 (PowerPath), lglal018(MPIO)
Backend ArrayVMAX, XtremIO, Vplex

Note: For host has already installed PowerPath, don't need install inq binary.

Test Strategy

We will first cover the basic function test case, after all function test case passed, then to cover concurrent testing.

For all the high level test cases we will cover the initiator type, multipath software and backend array that has mentioned in section "Test Environment Covered".

Only standalone host will be covered as cluster is not supported.

 

High Level Test Cases

1. Basic Function Test 

  • Upgrade Test

    Category Test case nameTest case description  Expected results 
     Positive   HP-UX Host to be discoverable after Upgrade

    1. Add "HP-UX" type host in the previous ViPR version.

    2. All Initiators added manually.

    3. Upgrade build to Yoda.

    HPUX Host become discoverable.

     

    Discover Host   

    Category Test case nameTest case description  Expected results 
     Positive   Discover Host with IP address

    1. Add HP-UX type host with IP address, root user/password.

    2. The HP-UX host contain both FC/iSCSI initiators.

    1. The FC initiator WWN has been successfully added

    2. The iSCSI initiator iqn has been successfully added

    3. Check whether both IPv4 and IPv6 nic has been discovered use viprcli,

         eg. viprcli host list-ipinterfaces -hl lglw7156-Linux

    4. Host is discoverable in the UI.

    DIscover Host with FQDN 

    1. Add HP-UX type host with hostname, root user, root password.

    2. The HP-UX host contain both FC/iSCSI initiators.

    1. The FC initiator WWN has been successfully added

    2. The iSCSI initiator iqn has been successfully added

    3. Check whether both IPv4 and IPv6 nic has been discovered

    4. Host is discoverable in the UI.

    Discover host using sudo user(not root)

    1. Create a sudo user not root user on HP-UX host.

    2. Add HP-UX type host with hostname or IP address, sudo user/password.

    1. The FC initiator WWN has been successfully added

    2. The iSCSI initiator iqn has been successfully added

    3. Check whether both IPv4 and IPv6 nic has been discovered

    4. Host is discoverable in the UI.

    Discover host use viprcli1.  Add HP-UX host use viprcli command, input correct IP address/hostname, root user/passwd.

    1. The FC initiator WWN has been successfully added

    2. The iSCSI initiator iqn has been successfully added

    3. Check whether both IPv4 and IPv6 nic has been discovered

    4. Host is discoverable the UI.

     NegativeDiscover Host with wrong credentials1. Add HP-UX host with wrong user name/passwd.Discovery Fail error
    Discover host using non sudo user1. Add HP-UX host with not sudo user.Discovery Fail error
    Discover a host with FQDN of an already existing IP1. Add a host with a new name but with the FQDN of an already existing IPDiscovery failure with an already existing Host error
     Discover host with wrong host name/IP address 1. Add a host with wrong host name or IP addressDiscovery Fail error
     Discover host with a not HP-UX type host 1. Add a host with a correct host but not HP-UX hostDiscovery Fail error
    Rediscover host after enable firewall

    1. Add HP-UX host with hostname, root user/password.

    2. Then enable the firewall of the host.

        (1) edit /etc/opt/ipf/ipf.conf

            add rules

            "block in quick from <Your ViPR IP> to any"

        (2) Reload the new added rules use command "ipf -Fa -A -f /etc/opt/ipf/ipf.conf".

        (3) List the rule to verify whether new added rule is take effect "ipfstat -io".

    3. Rediscover host on ViPR

    Rediscovery should fail
    Deregister all initiators

    1. Add HP-UX host with hostname, root user/password.

    2. Deregister all of the initiators from the host.

    3. Try to export a volume to this host

      

    1. Export will fail.

  • Mount Existing Volume

     CategoryTest case name Test case description Expected results
     Positive  Mount Volume has Exported 

    1. Create a new volume and export to the host.

    2. Mount this volume.

    1. Volume can be found in host at the mount point.

    2.  IO can successfully run on the file system.

     Mount Volume not Exported (MPIO + VMAX)

    1. Create a new volume.

    2. Mount this volume.

    1. Volume can be found in host at the mount point.

    2.  IO can successfully run on the file system.

     Mount Volume not Exported (MPIO + XtremIO)  
     Mount Volume not Exported (MPIO + Vplex)  
     Mount Volume not Exported (PowerPath + VMAX)  
     Mount Volume not Exported (PowerPath + XtremIO)  
     Mount Volume not Exported (PowerPath + Vplex)  
     Negative Mount Volume has Exported but not format

    1. Create a new volume and exported to the host.

    2. Mount a volume but not choose format

    1. Mount will failed.
    Mount Volume not exported but not format

    1. Create a new volume.

    2. Mount a volume but not choose format

    1. Mount will failed
    Mount Volume use existing mount path

    1. Create a new volume and export to the host.

    2. Mount this volume but use an already has mounted path

     1. Mount will failed.
    Mount Volume use invalid mount path1. Create a new volume.

    2. Mount a volume but use an not valid mount path

     1. It will report error "invalid mount path"
    Mount Volume to a read only mount path

    1. Create a mount path and change it to read-only in host.

    2. Create a new volume and export to the host.

    3. Mount this volume to this read-only mount path.

     1. The Mount task should fail and report clear error message.
  • Create and Mount Volume

    Category  Test case nameTest case description  Expected results
     Positive  Create Volume in CG and Mount Volume (MPIO + VMAX) 1. Create and mount a volume in CG to host.

    1. Volume can be created successfully

    2. Volume can be  mount successfully to the host

    3. IO can successfully run on the file system

     Create Volume in CG and Mount Volume (MPIO + XtremIO)  
     Create Volume in CG and Mount Volume (MPIO + Vplex)  
     Create Volume in CG and Mount Volume (PowerPath + VMAX)  
     Create Volume in CG and Mount Volume (PowerPath + XtremIO)  
      Create Volume in CG and Mount Volume (PowerPath + Vplex)  
     Create Volume not in CG and Mount Volume (MPIO + VMAX) 1. Create and mount a volume not in CG to host.1. Volume can be created successfully

    2. Volume can be  mount successfully to the host

    3. IO can successfully run on the file system

     Create Volume not in CG and Mount Volume (MPIO + XtremIO) 

     

     Create Volume not in CG and Mount Volume (MPIO + Vplex)  
     Create Volume not in CG and Mount Volume (PowerPath + VMAX)  
     Create Volume not in CG and Mount Volume (PowerPath + XtremIO)  
     Create Volume not in CG and Mount Volume (PowerPath + Vplex)  
     Negative  Create and Mount Volume that Volume name already exist  1. Volume can't be create successfully
     Create and Mount Volume Use not valid volume name  1. Volume can't be created successfully
     Create and Mount Volume Use not valid volume size  1. It should failed at invalid volume size
     Create and Mount Volume Use an existing mount path  1. It should failed at mount path already exist.
     Create and Mount Volume  Use invalid mount path  1. It should failed at invalid mount path
  • Expand Volume

    Category  Test case nameTest case description Expected results   
     Positive Expand mounted volume to larger size

    1.  Expand a volume and input a size that large than current size.

    1. Volume can be expanded successfully.

    2. Volume size is actually increased to the expected size

     Negative  Expand volume to smaller size

    1. Expand a volume but input a size that smaller than current size.

     

     

     1. Expand will failed
     Expand volume use invalid size 1. Expand a volume but input a invalid size 1. It should report error as volume size is invalid
  • Unmount Volume from Host

    Category  Test case nameTest case description Expected results   
     Positive     Unmount one volume from host (MPIO + VMAX)

    1. Don't open the mount point

    2. Umount volume

    1. Volume can be unmounts successfully.

    2. Volume is still visible to the host

    Unmount one volume from host (MPIO + XIO)

    1. Don't open the mount point

    2. Umount volume

    1. Volume can be unmounts successfully.

    2. Volume is still visible to the host

    Unmount one volume from host (MPIO + Vplex)

    1. Don't open the mount point

    2. Umount volume

    1. Volume can be unmounts successfully.

    2. Volume is still visible to the host

    Unmount one volume from host (PowerPath + VMAX)

    1. Don't open the mount point

    2. Umount volume

    1. Volume can be unmounts successfully.

    2. Volume is still visible to the host

    Unmount one volume from host (PowerPath + XIO)

    1. Don't open the mount point

    2. Umount volume

    1. Volume can be unmounts successfully.

    2. Volume is still visible to the host

    Unmount one volume from host (PowerPath + Vplex)

    1. Don't open the mount point

    2. Umount volume

    1. Volume can be unmounts successfully.

    2. Volume is still visible to the host

      Negative Unmount open volume

    1. Open the mount path.

    2. Umount volume

     1. Unmount should failed and report busy error.
  • Unmount and Delete Volume

    Category  Test case name Test case descriptionExpected results  
     Positive Unmount and delete one volume from host (MPIO + VMAX)

     

    1. Volume can be unmount successfully

    2. Volume can be deleted successfully.

    3. Other exported volumes are still exist in the host

     Unmount and delete one volume from host (MPIO + XIO)  1. Volume can be unmount successfully

    2. Volume can be deleted successfully.

    3. Other exported volumes are still exist in the host

     Unmount and delete one volume from host (MPIO + Vplex)  1. Volume can be unmount successfully

    2. Volume can be deleted successfully.

    3. Other exported volumes are still exist in the host

     Unmount and delete one volume from host (PowerPath + VMAX)  1. Volume can be unmount successfully

    2. Volume can be deleted successfully.

    3. Other exported volumes are still exist in the host

     Unmount and delete one volume from host (PowerPath + XIO)  1. Volume can be unmount successfully

    2. Volume can be deleted successfully.

    3. Other exported volumes are still exist in the host

     Unmount and delete one volume from host (PowerPath + Vplex) 

    1. Volume can be unmount successfully

    2. Volume can be deleted successfully.

    3. Other exported volumes are still exist in the host

     Unmount and delete Bulk volumes in a CG from host 

    1. Volumes can be unmount successfully

    2. Volumes can be deleted successfully.

    3. Other exported volumes are still exist in the host

     Unmount and delete Bulk volumes without a CG from host 

    1. Volumes can be unmount successfully

    2. Volumes can be deleted successfully.

    3. Other exported volumes are still exist in the host

     Unmount and delete the last volume from host

     

    1. Volume can be unmount successfully

    2. Volume can be deleted successfully.

    3. Export group should be deleted.

    Negative Unmount and delete open volume

    1. Open the mount path

    2. Umount and delete the volume

     1. Umount should failed and report busy error.

      

  • Mount and Umount Snapshot of a Volume

     Category Test case name Test case descriptionExpected results 
     Positive Mount a formatted snapshot without format

    1. Create and mount a volume to the host.

    2. Create files on this mount path.

    3. Create a snapshot for this volume.

    4. Mount this snapshot without format to file system.

    5. Check whether this snapshot could be mounted successfully.

    6. Check whether the file you previously create is still exist.

    1. Snapshot should be mounted successfully.

    2. The previous read file still exist.

    3. The mount snapshot should be read/write.

    Mount a formatted RO snapshot without format (Only XtremIO support)

    1. Create and mount a XIO volume to the host.

    2. Create files on this mount path.

    3. Umount this volume to let all write are flashed to disk.

    3. Create a RO snapshot for this volume.

    4. Mount this snapshot without format.

    5. Check whether this snapshot could be mounted successfully.

    6. Check whether the file you previously create is still exist.

    1. Snapshot should be mounted successfully.

    2. The previous read file still exist.

    3. The mount snapshot should be Read Only.

    Mount a formatted snapshot with format

    1. Create and mount a volume to the host.

    2. Create files on this mount path.

    3. Mount this snapshot with format to file system.

    4. Create a snapshot for this volume.

    5. Check whether this snapshot could be mounted.

    6. Check whether the files previously create is exist or not.

     1. Snapshot should be mounted successfully.

    2. The previous read file will not exist.

    3. The mount snapshot should be read/write

    Umount snapshot from host1. Umount snapshot from host.

    1.  Snapshot can be removed successfully

     Negative Mount a formatted RO snapshot with format (Only XtremIO support)

    1. Create and mount a XIO volume to the host.

    2. Create files on this mount path.

    3. Umount this volume to let all write are flashed to disk

    4. Create a RO snapshot for this volume.

    5. Mount this snapshot with format to file system.

     

    1. Snapshot can't be mount successfully because it is read only.

     

     Umount snapshot when the mount path is still open 1. Umount snapshot from host. 1. Snapshot can't be umounted successfully, it should report busy error.

     

  • Unexport a mounted Volume 

    Category  Test case name Test case descriptionExpected results  
     PositiveUnexport a mounted Volume

     

    1. A mounted volume can be unexported successfully

    2. Volume still exist in ViPR resource.

    3. Check the mount path, the volume should be umounted.

2. Concurrent Test

  • Mount/UnMount Existing Volume

    Test case name Test case description Expected results
     Mount/Unmount different volumes to the same host

    1. Submit several orders to mount different volumes and several orders to unmounts different volumes to the same host concurrently.

    1. Expect the mount/unmounts to the same host should be done sequentially.

    2. All orders can be successfully done.

     Mount/Unmount different volumes to different host 1. Submit several orders to mount different volumes and several orders to unmounts different volumes to the different host concurrently.1. Expect the mount/unmounts to different host should be done parallel.

    2. All orders can be successfully done.

     

     

  • Create and Mount/Unmount and Delete Volume

     Test case nameTest case description  Expected results
     Create and Mount/Unmount and Delete different volumes to the same host 1. Submit several orders to create and mount different volumes and several orders to unmounts and delete different volumes to the same host concurrently.

    1. Create volumes should be done parallel.

    2.  Export/Unexport and  mount/unmounts to the same host should be done sequentially.

    3. Delete volume should be done parallel.

    4. All orders can be successfully done.

     Create and Mount/Unmount and Delete different volumes to different host 1. Submit several orders to create and mount different volumes and several orders to unmounts and delete different volumes to different host concurrently.

    1. Create volumes should be done parallel.

    2. Export/unexport and mount/unmounts to different hosts should be done parallel.

    3. Delete volume should be done parallel.

    4. All orders can be successfully done.

Test Case Execution Result

Link the test case execution result or report here. 

Reference 

Dev Design doc: HP-UX Catalog Services 

Reviewed and Approved By

NameDateComments
 Dawe, Trevor <Trevor.Dawe@emc.com> 11/20 
 Logelin, Jay <Jay.Logelin@emc.com> 11/20 
 Cormier, Jeremie <Jeremie.Cormier@emc.com> 11/20 
 Zhang, Bob <bob.zhang@emc.com> 11/20 

 

 

 

 

  • No labels

1 Comment

  1. Upgrade tests can be added. For current customers who have non-discoverable HP-UX hosts added to ViPR. They should be able to use the UI or CLI to set the host as discoverable and discovery should run and keep the matching initiators that were manually added to the host.