Page History

S No

Test Description

Steps

Expected Results

Priority(P0/P1)

Type (Sanity/Functional/Upgrade/Performance)

Automatable(Y/N)

Hyper-V (Y/N)

Other VMM(Y/N)

Licensing

Verify source carries Apache license header discussed at http://www.apache.org/legal/src-headers.html

No references to existing copyright.

P0

Sanity

Y

Y

N

Register Template

Register templates of type VHD and VHDX
Attempt to register templates with wrong image type.  E.g. for VHDX, supply URI that ends in VHD and vice versa.

Templates of type VHD and VHDX should download properly and be reported as 'Ready'.
API should report errors if URI extension does not match intended image type.

P0

Functional

Y

Y

N

Register Template GUI

Verify register template GUI allows VHDX and VHD templates be created for Hypervisors of type Hyper-V

VHDX and VHD should appear in drop download of image types when hypervisor is Hyper-V

Functional

N

Y

N

Dashboard Reporting

Verify that single Hyper-V 2012 cluster reports unallocated storage pool space correctly.

Plugin reports unallocated space equal to space available on local filesystem disk that provides the pool.

Functional

N

Y

N

Add Hyper-V Host

Create advanced zone with network isolation and a XenServer cluster, which will host the system VMs.
Add Hyper-V cluster.  Add Hyper-V host to cluster.

Functional

Y

Y

N

VM Lifecycle

1. Create instance from Hyper-V template.
2. Use API to stop VM
3. Use API to start VM
4. Ping VM
5. Destory VM

domR should be started on the XenServer cluster
Should be able to verify state transitions by examining Hyper-V host directly.

Functional

Y

Y

N

VM State Synchronisation

1. Create instance from Hyper-V template.
2. Call Hyper-V API directly to stop VM
3. Query CloudStack API for VM state after it has been updated. 
4.  Can we repeat this for a stopped VM?  (CloudStack may not allow stopped VMs to exist on the machine)

The state in CloudStack should have been udpated.

Functional

Y

Y

N