Page History

Test cases repeated for hypervisors & host versions:
1. XenServer XS 6.2
2. KVM RHEL6.2
3. Vmware ESXi  5.0
 

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.0
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

HA002

Host maintenance mode with activities
Hypervisor: XEN
Host: XS 6.0.0
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

HA003

Network disconnect
Hypervisor: XEN
Host: XS 6.0.0
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

HA004

Network disconnect with activities
Hypervisor: XEN
Host: XS 6.0.0
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

HA005

Host power off (not a graceful shutdown)
Hypervisor: XEN
Host: XS 6.0.0
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

HA006

Host power off with activities (not a graceful shutdown)
Hypervisor: XEN
Host: XS 6.0.0
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

HA007 HA009

Host maintenance mode
Hypervisor: XEN
Host: XS 6.0.2 0
Primary storage: NFS ISCSI NICBOND

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.

P2

SANITY, FUNCTIONAL

1 hour

HA008  

HA007 HA010

Network disconnect
Hypervisor: XEN
Host: XS 6.0.2 0
Primary storage: NFS ISCSI NICBOND

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.

P2

SANITY, FUNCTIONAL

1 hour

HA011 HA008

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

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 (not shutdown)
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.

P2

SANITY, FUNCTIONAL

HA009 HA012

Host maintenance mode
Hypervisor: XEN
Host: XS 6.0.0 2
Primary storage: ISCSI NICBOND FcoE

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.

P2

SANITY, FUNCTIONAL

1 hour

HA010

Network disconnect
Hypervisor: XEN
Host: XS 6.0.0
Primary storage: ISCSI NICBOND

P2

SANITY, FUNCTIONAL

1 hour

HA011

Host power off (not a graceful shutdown)
Hypervisor: XEN
Host: XS 6.0.0
Primary storage: ISCSI NICBOND

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.

P2

SANITY, FUNCTIONAL

HA012

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

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.

P2

SANITY, FUNCTIONAL

1 hour

HA013

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

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.

P2

SANITY, FUNCTIONAL

1 hour

HA014

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

P2

SANITY, FUNCTIONAL

HA015

Host maintenance mode
Hypervisor: KVM
Host: RHEL 6.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 P2

SANITY, FUNCTIONAL

1 hour

  pass

HA016 HA013

Network disconnect
Hypervisor: KVM XEN
Host: RHEL XS 6.0.2
Primary storage: NFS FcoE

1. Create Advance zone, pod, cluster.
Add 2 hosts to cluster, secondary & primary Storage, isolated network
2. Create  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 P2

SANITY, FUNCTIONAL

1 hour

pass

HA017 HA014

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

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 (not shutdown)
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 P2

SANITY, FUNCTIONAL

  Failed
CS-15180

HA018 HA015

Host maintenance mode
Hypervisor: KVM
Host: RHEL 6.2
Primary storage: NFSOCFS2 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.

P2 P1

SANITY, FUNCTIONAL

1 hour

hold pass

HA019 HA016

Network disconnect
Hypervisor: KVM
Host: RHEL 6.2
Primary storage: NFSOCFS2 NFS

1. Create Advance zone, pod, cluster.
Add 2 hosts to cluster, secondary & primary Storage, isolated network
2.  Create 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.

P2 P1

SANITY, FUNCTIONAL

1 hour

hold pass

HA020 HA017

Host power off (not a graceful shutdown)
Hypervisor: KVM
Host: RHEL 6.2
Primary storage: NFSOCFS2 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 (not shutdown)
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.

P2 P1

SANITY, FUNCTIONAL

Failed
hold CS-15180

HA021 HA018

Host maintenance mode
Hypervisor: KVM
Host: RHEL 6.2
Primary storage: FcoE NFSOCFS2

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.

P2

SANITY, FUNCTIONAL

1 hour

hold

HA022 HA019

Network disconnect
Hypervisor: KVM
Host: RHEL 6.2
Primary storage: FcoE NFSOCFS2

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.

P2

SANITY, FUNCTIONAL

1 hour

hold

HA023 HA020

Host power off (not a graceful shutdown)
Hypervisor: KVM
Host: RHEL 6.2
Primary storage: FCoE NFSOCFS2

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 (not shutdown)
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.

P2

SANITY, FUNCTIONAL

hold

HA024 HA021

Host maintenance mode
Hypervisor: vmware KVM
Host: ESXi 4RHEL 6.1 2
Primary storage: NFS FcoE

1. Create Advance zone, pod, cluster.
Add 2 hosts to cluster, secondary & primary Storage, isolated network
2. Create  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 P2

SANITY, FUNCTIONAL

1 hour

pass hold

HA025 HA022

Network disconnect
Hypervisor: vmware KVM
Host: ESXi 4RHEL 6.1 2
Primary storage: NFS FcoE

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 P2

SANITY, FUNCTIONAL

1 hour

Failed hold 15186

HA026 HA023

Host power off (not a graceful shutdown)
Hypervisor: vmware KVM
Host: ESXi 4RHEL 6.1 2
Primary storage: NFS FCoE

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 (not shutdown)
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 P2

SANITY, FUNCTIONAL

Failed 15186 hold

HA027 HA024

Host maintenance mode
Hypervisor: vmware
Host: ESXi 54.0 1
Primary storage: ISCSI NFS

1. Create Advance zone, pod, cluster.
Add 2 hosts to cluster, secondary & primary Storage, isolated network
2.  Create 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  

NFS

HA028 HA025

Network disconnect
Hypervisor: vmware
Host: ESXi 54.0 1
Primary storage: ISCSI 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

Failed
15186

NFS  

HA029 HA026

Host power off (not a graceful shutdown)
Hypervisor: vmware
Host: ESXi 54.0 1
Primary storage: ISCSI 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 (not shutdown)
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

Failed 15186 CS-15180

NFS

HA027 HA030

Host maintenance mode
Hypervisor: OVM vmware
Host: 2ESXi 5.3 0
Primary storage: ISCSI

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.

P2 P1

SANITY, FUNCTIONAL

1 hour

Also, Sudha says to not do OVM.

pass

NFS

HA028 HA031

Network disconnect
Hypervisor: OVM vmware
Host: 2ESXi 5.3 0
Primary storage: ISCSI

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 & 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.

P2 P1

SANITY, FUNCTIONAL

1 hour

Also, Sudha says to not do OVM.  

Failed
15186

NFS

HA029 HA032

Host power off (not a graceful shutdown)
Hypervisor: OVM vmware
Host: 2ESXi 5.3 0
Primary storage: ISCSI

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 (not shutdown)
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.

P2 P1

SANITY, FUNCTIONAL

Also, Sudha says to not do OVM.

Failed
CS-15180

NFS  

HA033

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

HA034

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

HA035

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.

1.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.

  Fail
CS-15276 - Not able to put the host in maintenance mode when one of the host in the cluster has host tag and the other host does not have a host tag. - CLOSED