You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 31 Next »

 

Test cases repeated for hypervisors & host versions:
1. XenServer XS 6.0.2
2. KVM RHEL6.3


Test cases repeated for zones:
1. Basic
2. Advance

 

 

 

 

 

 

 

 

 

Test Case ID

Test Case Name

 

Expected Results

Priority
(P1 | P2 |P3)

Test Case Type( Sanity | Functional |
Negative)

Execution Time

Executed on Release

Reviewed By

Status

Comments

HA001

Host maintenance mode
Hypervisor: XEN
Host: XS 6.0.2
Primary storage: NFS

1. Create Advance zone, pod, cluster.
Add 2 hosts to cluster, secondary & primary Storage, isolated network
2. Create a custom compute service offering with HA. Create HA enabled Vms & Acquire IP. Create port forwarding & load balancing rules for Vms.
3. Host 1 : put to maintenance mode.
4. After failover to Host 2 succeeds, deploy Vms
5. Host 1 : cancel maintenance mode.
6. Host 2 : put to maintenance mode.
7. After failover to Host 1 succeeds, deploy VMs

3. All Vms should failover to Host 2 in cluster. Vms should be in running state.
All port forwarding rules and load balancing
Rules should work.
4. Deploy Vms on host 2 should succeed.
6. All Vms should failover to Host 1 in cluster.
7. Deploy Vms on host 1 should succeed.

P1

SANITY, FUNCTIONAL

1 hour

 

 

pass

 

HA002

Host maintenance mode with activities
Hypervisor: XEN
Host: XS 6.0.2
Primary storage: NFS

1. Create Advance zone, pod, cluster.
Add 2 hosts to cluster, secondary & primary Storage, isolated network
2. Create a custom compute service offering with HA. Create HA enabled Vms. Acquire IP. Create port forwarding & load balancing rules for Vms.
3. While activities are ongoing: Create snapshots, recurring snapshots, create templates, download volumes, Host 1 : put to maintenance mode.
4. After failover to Host 2 succeeds, deploy Vms
5. Host 1 : cancel maintenance mode.
6. While activities are ongoing: Create snapshots, recurring snapshots, create templates, download volumes, Host 2 : put to maintenance mode.
7. After failover to Host 1 succeeds, deploy VMs

3. All Vms should failover to Host 2 in cluster. Vms should be in running state.
All port forwarding rules and load balancing Rules should work.
4. Deploy Vms on host 2 should succeed. All ongoing activities in step 3 should succeed.
6.  All Vms should failover to Host 1 in cluster.
7. Deploy Vms on host 1 should succeed. All ongoing activities in step 6 should succeed.

P1

SANITY, FUNCTIONAL

1 hour

 

 

pass

 

HA003

Network disconnect
Hypervisor: XEN
Host: XS 6.0.2
Primary storage: NFS

1. Create Advance zone, pod, cluster.
Add 2 hosts to cluster, secondary & primary Storage, isolated network
2. Create a custom compute service offering with HA. Create HA enabled Vms & Acquire IP. Create port forwarding & load balancing rules for Vms.
3. Host 1 : Disconnect the NIC.
4. After failover to Host 2 succeeds, deploy Vms

3. All Vms should failover to Host 2 in cluster. Vms should be in running state.
All port forwarding rules and load balancing
Rules should work.
4. Deploy Vms on host 2 should succeed.

P1

SANITY, FUNCTIONAL

1 hour

 

 

pass

 

HA004

Network disconnect with activities
Hypervisor: XEN
Host: XS 6.0.2
Primary storage: NFS

1. Create Advance zone, pod, cluster.
Add 2 hosts to cluster, secondary & primary Storage, isolated network
2. Create a custom compute service offering with HA. Create HA enabled Vms & Acquire IP.  Create port forwarding & load balancing rules for Vms.
3. While activities are ongoing: Create snapshots, recurring snapshots, create templates, download volumes,
Host 1 : Disconnect the NIC
4. After failover to Host 2 succeeds, deploy Vms

3. All Vms should failover to Host 2 in cluster. Vms should be in running state.
All port forwarding rules and load balancing Rules should work.
4. Deploy Vms on host 2 should succeed. All ongoing activities in step 3 should succeed.

P1

SANITY, FUNCTIONAL

1 hour

 

 

pass

 

HA005

Host power off (not a graceful shutdown)
Hypervisor: XEN
Host: XS 6.0.2
Primary storage: NFS

1. Create Advance zone, pod, cluster.
Add 2 hosts to cluster, secondary & primary Storage, isolated network
2. Create a custom compute service offering with HA. Create HA enabled Vms & Acquire IP.  Create port forwarding & load balancing rules for Vms.
3. Host 1 : power off
4. After failover to Host 2 succeeds, deploy Vms

3. All Vms should failover to Host 2 in cluster. Vms should be in running state.
All port forwarding rules and load balancing
Rules should work.
4. Deploy Vms on host 2 should succeed.

P1

SANITY, FUNCTIONAL

 

 

 

pass

 

HA006

Host power off with activities (not a graceful shutdown)
Hypervisor: XEN
Host: XS 6.0.2
Primary storage: NFS

1. Create Advance zone, pod, cluster.
Add 2 hosts to cluster, secondary & primary Storage, isolated network
2. Create a custom compute service offering with HA. Create HA enabled Vms & Acquire IP. Create port forwarding & load balancing rules for Vms.
3. While activities are ongoing: Copy snapshots, recurring snapshots, create templates, download volumes. Make sure these are lengthy operations. Power off Host1 while they are still occurring.
4. After failover to Host 2 succeeds, deploy Vms

3. Deploy Vms on host 2 should succeed. All ongoing activities in step 3 should succeed.

P1

SANITY, FUNCTIONAL

1 hour

 

 

pass

 

HA007

Host maintenance mode
Hypervisor: KVM
Host: RHEL 6.3
Primary storage: NFS

1. Create Advance zone, pod, cluster.
Add 2 hosts to cluster, secondary & primary Storage, isolated network
2. Create a custom compute service offering with HA. Create HA enabled Vms & Acquire IP. Create port forwarding & load balancing rules for Vms.
3. Host 1 : put to maintenance mode.
4. After failover to Host 2 succeeds, deploy Vms
5. Host 1 : cancel maintenance mode.
6. Host 2 : put to maintenance mode.
7. After failover to Host 1 succeeds, deploy VMs

3. All Vms should failover to Host 2 in cluster. Vms should be in running state.
All port forwarding rules and load balancing
Rules should work.
4. Deploy Vms on host 2 should succeed.
6. All Vms should failover to Host 1 in cluster.
7. Deploy Vms on host 1 should succeed.

P1

SANITY, FUNCTIONAL

1 hour

 

 


 

HA008

Host maintenance mode with activities
Hypervisor: KVM
Host: RHEL 6.3
Primary storage: NFS

1. Create Advance zone, pod, cluster.
Add 2 hosts to cluster, secondary & primary Storage, isolated network
2. Create a custom compute service offering with HA. Create HA enabled Vms. Acquire IP. Create port forwarding & load balancing rules for Vms.
3. While activities are ongoing: Create snapshots, recurring snapshots, create templates, download volumes, Host 1 : put to maintenance mode.
4. After failover to Host 2 succeeds, deploy Vms
5. Host 1 : cancel maintenance mode.
6. While activities are ongoing: Create snapshots, recurring snapshots, create templates, download volumes, Host 2 : put to maintenance mode.
7. After failover to Host 1 succeeds, deploy VMs

3. All Vms should failover to Host 2 in cluster. Vms should be in running state.
All port forwarding rules and load balancing Rules should work.
4. Deploy Vms on host 2 should succeed. All ongoing activities in step 3 should succeed.
6.  All Vms should failover to Host 1 in cluster.
7. Deploy Vms on host 1 should succeed. All ongoing activities in step 6 should succeed.

P1

SANITY, FUNCTIONAL

1 hour

 

 

 

 

HA009

Network disconnect
Hypervisor: KVM
Host: RHEL 6.3
Primary storage: NFS

1. Create Advance zone, pod, cluster.
Add 2 hosts to cluster, secondary & primary Storage, isolated network
2. Create a custom compute service offering with HA. Create HA enabled Vms & Acquire IP.Create port forwarding & load balancing rules for Vms.
3. Host 1 : Disconnect the NIC
4. After failover to Host 2 succeeds, deploy Vms

3. All Vms should failover to Host 2 in cluster. Vms should be in running state.
All port forwarding rules and load balancing
Rules should work.
4. Deploy Vms on host 2 should succeed.

P1

SANITY, FUNCTIONAL

1 hour

 

 


 

HA010

Network disconnect with activity
Hypervisor: KVM
Host: RHEL 6.3
Primary storage: NFS

1. Create Advance zone, pod, cluster.
Add 2 hosts to cluster, secondary & primary Storage, isolated network
2. Create a custom compute service offering with HA. Create HA enabled Vms & Acquire IP.  Create port forwarding & load balancing rules for Vms.
3. While activities are ongoing: Create snapshots, recurring snapshots, create templates, download volumes,
Host 1 : Disconnect the NIC
4. After failover to Host 2 succeeds, deploy Vms

3. Deploy Vms on host 2 should succeed. All ongoing activities in step 3 should succeed.

P1

SANITY, FUNCTIONAL

1 hour

 

 

 

 

HA011

Host power off with activity (graceful shutdown)
Hypervisor: KVM
Host: RHEL 6.3
Primary storage: NFS

1. Create Advance zone, pod, cluster.
Add 2 hosts to cluster, secondary & primary Storage, isolated network
2. Create a custom compute service offering with HA. Create HA enabled Vms & Acquire IP. Create port forwarding & load balancing rules for Vms.
3. While activities are ongoing: Copy snapshots, recurring snapshots, create templates, download volumes. Make sure these are lengthy operations. Power off Host1 while they are still occurring.
4. After failover to Host 2 succeeds, deploy Vms

3. Deploy Vms on host 2 should succeed. All ongoing activities in step 3 should succeed.

P1

SANITY, FUNCTIONAL

1 hour

 

 

 

 

HA012

Host power off with activity (graceful shutdown)
Hypervisor: KVM
Host: RHEL 6.3
Primary storage: NFS

1. Create Advance zone, pod, cluster.
Add 2 hosts to cluster, secondary & primary Storage, isolated network
2. Create a custom compute service offering with HA. Create HA enabled Vms & Acquire IP.  Create port forwarding & load balancing rules for Vms.
3. While activities are ongoing: Create snapshots, recurring snapshots, create templates, download volumes,
Host 1 : Disconnect the NIC
4. After failover to Host 2 succeeds, deploy Vms

3. Deploy Vms on host 2 should succeed. All ongoing activities in step 3 should succeed.

P1

SANITY, FUNCTIONAL

1 hour

 

 

 

 

HA013

Maintenance mode with 2 hosts in cluster - Vms need not be HA enabled for being live migrated

1.    Have 1 host in 1 cluster.
2.    Deploy few vms.(These Vms need not be deployed with service offerings that are HA enabled). Create Static Nat/PF rules.
3.    Add 1 more host to this cluster.
4.    Put host1 in maintenance mode.
5.    Verify Step1 in "Expected Results"
6.    Add 1 more Vm. This Vm gets deployed in host2.
7.     Take host1 out of maintenance mode.
8.    Put host2 in maintenance mode.
9.    Verify Step2 in "Expected Results"


After step4 - Check the following

  1. Host1 should be put in Maintenance mode suceessfully. All Vms migrate successfully to host2. Make sure that the Vms are still accessible using their existing PF rules and static Nat rules.

  2. After step8  - Check the following:

    Host2 should be put in Maintenance mode suceessfully. All Vms migrate successfully to host1. Make sure that the Vms are still accessible using their existing PF rules and static Nat rules.

 

 

 

 

 

pass

 

HA014

Maintenance mode with 1 host in cluster

  1. Have a cluster with 1 host.
  2. Deploy few vms.
  3. Put this host in maintenance mode.
  4. Verify step1 from "Expected Results"
  5. Cancel maintenance mode.
  6. Verify step2- 6 from "Expected Results"

Verity following after step3.
1.Putting the host in maintenance mode should succeed.All  VMs will be in stopped state.
Verity following  after step4.
2.    SSVM amd CPVM are started automatically.
3.    All user VMs remains in stopped state.
4.    We are able to manually start the Vms successfully.
5.    Make sure that the Vms are still accessible using their existing PF rules.6.    We are able to deploy more vms

 

 

 

 

 

pass

 

HA015

Maintenance mode with 2 hosts in cluster with different host tag

1-Cluster has 1 host , say host1 with host tag.
2-Deploy few VMS with host tag in service offerings
3-Add another host , host2 to this cluster with  no host tag.
4-Put host1 in maintenance mode.

Host1 should be put in maintenance mode successfully. All the Vms should remain in stopped state since they cannot live migrate to host2 which has no host tags.

 

 

 

 

 

pass

 

 

Maintenance mode with 2 hosts in cluster - Vms need not be HA enabled for being live migrated

Have 1 host in 1 cluster
2-Deploy few vms.(These Vms need not be deployed with service offerings that are HA enabled). Create Static Nat/PF rules
3-Add 1 more host to this cluster.
4-Put host1 in maintenance mode.
5-Verify Step1 in "Expected Results"
6-Add 1 more Vm. This Vm gets deployed in host2.
7-Take host1 out of maintenance mode.
8-Put host2 in maintenance mode.
9-Verify Step2 in "Expected Results"

After step4 - Check the following
1-Host1 should be put in Maintenance mode suceessfully. All Vms migrate successfully to host2. Make sure that the Vms are still accessible using their existing PF rules and static Nat rules.

After step8  - Check the following:
2-Host2 should be put in Maintenance mode suceessfully. All Vms migrate successfully to host1. Make sure that the Vms are still accessible using their existing PF rules and static Nat rules.

 

 

 

 

 

 

 
  • No labels