| Test cases repeated for hypervisors & host versions: 1. XenServer XS 5. 6 SP2 6.0.2 2. KVM RHEL6.2 3 . Vmware ESXi 4.1 5.0 4. OVM OVM 2.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.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.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.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 CS-15103 | |
HA004 | Network disconnect with activities Hypervisor: XEN Host: XS 6.0.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 CS-15103 | |
HA005 | Host power off (not a graceful shutdown) Hypervisor: XEN Host: XS 6.0.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.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: XEN Host: XS 6.0.2 Primary storage: NFS 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 | | | On Hold | |
HA008 | | | | | | | | | | |
HA007 | Network disconnect Hypervisor: XEN Host: XS 6.0.2 Primary storage: NFS 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 | | | hold | | | | | | | | | | | | |
HA008 | Host power off (not a graceful shutdown) Hypervisor: XEN Host: XS 6.0.2 Primary storage: NFS 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 | | | | hold | | | | | | | | | | | | |
HA009 | Host maintenance mode Hypervisor: XEN Host: XS 6.0.0 Primary storage: 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 | | | hold | | | | | | | | | | | | |
HA010 | Network disconnect Hypervisor: XEN Host: XS 6.0.0 Primary storage: 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 | | | hold | | | | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | |
HA011 | Host power off (not a graceful shutdown) Hypervisor: XEN Host: XS 6.0.0 Primary storage: 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 | | | | hold | | | | | | | | | | | | |
HA012 | Host maintenance mode Hypervisor: XEN Host: XS 6.0.2 Primary storage: 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 | | | hold | | | | | | | | | | | | |
HA013 | Network disconnect Hypervisor: XEN Host: XS 6.0.2 Primary storage: 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. | P2 | SANITY, FUNCTIONAL | 1 hour | | | hold | | HA014 | Host power off (not a graceful shutdown) Hypervisor: XEN Host: XS 6.0.2 Primary storage: 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.
P2 | SANITY, FUNCTIONAL | | | | hold | | 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 | SANITY, FUNCTIONAL | 1 hour | | | pass | | HA016 | Network disconnect 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 : 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 | | HA017 | Host power off (graceful shutdown) 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 : 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 CS-15180 | | HA018 | Host maintenance mode Hypervisor: KVM Host: RHEL 6.2 Primary storage: 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 | | HA019 | Network disconnect Hypervisor: KVM Host: RHEL 6.2 Primary storage: 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 | | HA020 | Host power off (not a graceful shutdown) Hypervisor: KVM Host: RHEL 6.2 Primary storage: 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 | | HA021 | Host maintenance mode Hypervisor: KVM Host: RHEL 6.2 Primary storage: 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 | | | hold | | HA022 | Network disconnect Hypervisor: KVM Host: RHEL 6.2 Primary storage: 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. | P2 | SANITY, FUNCTIONAL | 1 hour | | | hold | |
HA023 | Host power off (not a graceful shutdown) Hypervisor: KVM Host: RHEL 6.2 Primary storage: 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. | P2 | SANITY, FUNCTIONAL | | | | hold | |
HA024 | Host maintenance mode Hypervisor: vmware Host: ESXi 4.1 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 | | HA025 | Network disconnect Hypervisor: vmware Host: ESXi 4.1 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 | | | Failed 15186 | |
HA026 | Host power off (not a graceful shutdown) Hypervisor: vmware Host: ESXi 4.1 Primary storage: NFS | 1. Create Advance zone, pod, cluster. Add 2 hosts to cluster, secondary & primary Storage, isolated network 2. Create 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 | |
HA027 | Host maintenance mode Hypervisor: vmware Host: ESXi 5.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. | P1 | SANITY, FUNCTIONAL | 1 hour | | | pass | NFS | HA028 | Network disconnect Hypervisor: vmware Host: ESXi 5.0 Primary storage: ISCSI | 1. Create Advance zone, pod, cluster. Add 2 hosts to cluster, secondary & primary Storage, isolated network 2. Create 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 | Host power off (not a graceful shutdown) Hypervisor: vmware Host: ESXi 5.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. | P1 | SANITY, FUNCTIONAL | | | | Failed CS-15180 | NFS |
HA030 | Host maintenance mode
Hypervisor: OVM
Host: 2.3
Primary storage: ISCSI 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 - 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.
|