|
|
|
|
|
|
|
|
Requirements |
|
|
|
|
|
|
Kickstart Supported Guest OS |
|
|
|
|
|
|
|
|
|
|
|
|
Testcase |
Test Description |
Steps |
Expected Results |
Priority |
Type |
Results |
|
Kickstart Supported Guest OS |
|
|
|
|
|
|
CentOS 6.2 |
Baremetal host installed CentOS 6.2 |
successful |
P1 |
functiona |
Pass |
|
CentOS 6.3 |
Baremetal host installed CentOS 6.3 |
successful |
P1 |
functiona |
Pass |
|
Fedora 17 |
Baremetal host installed Fedora 17 |
successful |
P1 |
functiona |
Pass |
|
Ubuntu 12.04 |
Baremetal host installed Ubuntu 12.04 |
successful |
P1 |
functiona |
Pass |
|
PING style Windows |
Baremetal host installed PING style Windows 2008 R2 |
successful |
P1 |
functiona |
|
|
|
|
|
|
|
|
|
Zone Configuration |
|
|
|
|
|
1 |
baremetal network offering |
Create network offering shared, no vlan specify, dhcp, userdata, security group, baremetalPxeService |
|
P1 |
functional |
Pass |
2 |
Basic Zone with BareMetal Hypervisor |
create Basic Zone with BareMetal Hypervisor |
No SSVM ,CPVM will be launched. |
P1 |
functional |
Pass |
|
Adding Baremetal Host |
|
|
|
|
|
3 |
Add Baremetal Host providing valid values for the following: |
Add Baremetal Host via API addBaremetalHost providing valid values for following: |
Host addition should succeed. |
P1 |
functional |
Pass |
4 |
Add Baremetal Host without Host tags |
Add Baremetal Host without Host tags |
Host addition should fail |
P2 |
negative |
|
6 |
Add Baremetal Host without providing a Mac Address |
Add Baremetal Host without providing a Mac Address |
Host addition should fail |
P2 |
negative |
|
7 |
Add Baremetal Host without providing IPMI Ipaddress, account and password. |
Add Baremetal Host without providing IPMI Ipaddress, account and password. |
Host addition should fail |
P2 |
negative |
|
8 |
Add Baremetal Host by specifying a invalid values for IPMI Ip, account and password. |
Add Baremetal Host by specifying a invalid values for IPMI Ip, account and password. |
Host addition should fail. |
P2 |
negative |
|
9 |
Add cluster of 2 Baremetal hosts |
Add cluster of 2 Baremetal hosts |
Cluster of hosts added successfully |
P1 |
functional |
Pass |
|
|
|
|
|
|
|
|
Configuring and adding a TFTP DHCP PXE server |
|
|
|
|
|
10 |
Configure TFTP DHCP PXE server |
1. In Xencenter add Xenserver 6.0.2 host which must be on same L2 switch level as Baremetal hosts. |
TFTP server should be started successfully. |
P1 |
functional |
Pass |
11 |
Add a TFTP server to the zone using addBaremetalPxeKickStartServer() |
1. Add a TFTP server to the zone using API addBaremetalPxeKickStartServer() |
TFTP server should get added successfully to the Zone. |
P1 |
functional |
Pass |
12 |
Add a TFTP server to the zone using addBaremetalPxeKickStartServer() when the TFTP server is not running. |
1. Add a TFTP server to the zone using addBaremetalPxeKickStartServer() when the TFTP server is not running. |
Should the addition of TPFT server fail ? |
P2 |
negative |
|
|
|
|
|
|
|
|
|
Configuring DHCP server |
|
|
|
|
|
13 |
Configure DHCP server |
Configure VM as DHCP server and configure it to service all the hosts in the pod ip range via API addBaremetalDhcp |
DHCP server add to deployment |
P1 |
functional |
Pass |
|
|
|
|
|
|
|
|
Kickstart Installation. Register kickstart templates. |
|
|
|
|
|
14 |
Create Baremetal compute offering |
Create Baremetal compute offering with Baremetal host hosttag |
Baremetal compute offering created |
P1 |
functional |
Pass |
15 |
Register baremetal kickstart template |
Register a template by passing valid values for displaytext,format,hypervisor="Baremetal", ostypeid,url="Kickstart_file_location;template_repo_on_nfs_path",zoneid . |
Template registration should succeed. |
P1 |
functional |
Pass |
16 |
Register template with invalid format |
Register a template by passing url with invalid format like only Kickstart_file_location /only template_repo_on_nfs_path /using a different separator instead of ";" like Kickstart_file_location.template_repo_on_nfs_path |
Template registration should fail. |
P2 |
negative |
|
17 |
Register template with invalid Kickstart_file_location |
Register a template by passing invalid values for Kickstart_file_location |
Template registration should fail. |
P2 |
negative |
|
18 |
Register template with invalid template_repo_on_nfs_path |
Register a template by passing invalid values for template_repo_on_nfs_path |
Template registration should fail. |
P2 |
negative |
|
19 |
List all the templates for Baremetal hypervisors. |
1. Register few "Baremetal" templates. |
All the templates for Baremetal should be listed. |
P1 |
functional |
Pass |
20 |
Deletion of templates. |
1. Register few "Baremetal" templates. |
Deletion of templates should succeed. |
P1 |
functional |
Pass |
|
|
|
|
|
|
|
|
Ping style Installation Register PING style template |
|
|
|
|
|
21 |
Install Windows 2008 R2 Server on a server that is identical (CPU, memory, disk, resources) to the servers which will be used as baremetal hosts. |
1. Install Windows 2008 R2 Server on a server |
Template registration should succeed. |
P1 |
functional |
Pass |
22 |
Register a template by passing url with invalid format like only ping_file_location /only template_repo_on_nfs_path /using a different separator instead of ";" like ping_file_location.template_repo_on_nfs_path |
Register a template by passing url with invalid format like only ping_file_location /only template_repo_on_nfs_path /using a different separator instead of ";" like ping_file_location.template_repo_on_nfs_path |
Template registration should fail. |
P2 |
negative |
|
23 |
Register template with invalid values for ping_file_location |
Register a template by passing invalid values for ping_file_location |
Template registration should fail. |
P2 |
negative |
|
|
|
|
|
|
|
|
|
Deploying Baremetal VM |
|
|
|
|
|
24 |
Deploy baremetal kickstart VM |
Deploy a VM using a SO with host tag of a Baremetal host using a baremetal kickstart style template. |
Vm deployment should succeed. |
P1 |
functional |
Pass |
25 |
Deploy baremetal PING style Windows VM |
Deploy a VM using a SO with host tag of a Baremetal host using a baremetal PING style template |
Vm deployment should succeed. |
P2 |
functional |
|
26 |
Deploy a VM by passing a disk offering id. |
Deploy a VM by passing a disk offering id. |
VM deployment should fail. |
P2 |
negative |
|
29 |
Deploy a VM using userdata |
Deploy a VM using userdata |
Vm deployment should succeed. |
P2 |
functional |
|
30 |
Deploy a VM when TFTP server is not yet configured in the zone. |
Deploy a VM when TFTP server is not yet configured in the zone. |
Vm deployment should fail. |
P2 |
negative |
|
31 |
Deploy a VM when TFTP server is not reachable. |
Deploy a VM when TFTP server is not reachable. |
Vm deployment should fail. |
P2 |
negative |
|
32 |
Deploy a VM when DHCP server is not reachable. |
Deploy a VM when DHCP server is not reachable. |
Vm deployment should fail. |
P2 |
negative |
|
33 |
Deploy a VM when host is in "Down" state. |
Deploy a VM when host is in "Down" state. |
Vm deployment should fail. |
P2 |
negative |
|
34 |
Deploy a VM on a host which has an invalid ipaddress( Ipaddress does not exist in the DHCP server) assigned to it. |
Deploy a VM on a host which has an invalid ipaddress( Ipaddress does not exist in the DHCP server) assigned to it. |
Vm deployment should fail. |
P2 |
negative |
|
35 |
Deploy a VM on a host which has an invalid ipaddress ( Ipaddress that existis in the DHCP server but is associated with a different MAC address) assigned to it. |
Deploy a VM on a host which has an invalid ipaddress ( Ipaddress that existis in the DHCP server but is associated with a different MAC address) assigned to it. |
Vm deployment should fail. |
P2 |
negative |
|
36 |
Deploy a VM on a host which has an invalid MAC address ( MAC address does not exist in the DHCP server) assigned to it. |
Deploy a VM on a host which has an invalid MAC address ( MAC address does not exist in the DHCP server) assigned to it. |
Vm deployment should fail. |
P2 |
negative |
|
37 |
Deploy a VM on a host which has an invalid MAC address ( MAC address that existis in the DHCP server but is associated with a different ip address) assigned to it. |
Deploy a VM on a host which has an invalid MAC address ( MAC address that existis in the DHCP server but is associated with a different ip address) assigned to it. |
Vm deployment should fail. |
P2 |
negative |
|
38 |
Deploy a VM on a host which has an invalid ipaddress assigned to it. |
Deploy a VM on a host which has an invalid ipaddress assigned to it. |
Vm deployment should fail. |
P2 |
negative |
|
39 |
Deploy a VM on a host which has an invalid MAC address assigned to it. |
Deploy a VM on a host which has an invalid MAC address assigned to it. |
Vm deployment should fail. |
P2 |
negative |
|
|
|
|
|
|
|
|
|
Hosts |
|
|
|
|
|
40 |
Force reconnect Host() |
Force reconnect Host() |
|
P1 |
functional |
Pass |
41 |
UpdateHost() - Edit host tags |
UpdateHost() - Edit host tags |
|
P1 |
functional |
Pass |
42 |
deleteHost() - > Put the host in maintenance and then delete the host |
deleteHost() - > Put the host in maintenance and then delete the host |
|
P1 |
functional |
|
43 |
Put the host in maintenance mode |
Put the host in maintenance mode |
|
P1 |
functional |
Pass |
44 |
Put the host in maintenance mode and bring the host out of maintenance mode. |
Put the host in maintenance mode and bring the host out of maintenance mode. |
|
P1 |
functional |
Pass |
46 |
Power down host |
Power down host |
Unable to access VM console |
P1 |
functional |
Pass |
47 |
Power down host and the power on the host |
Power down host and the power on the host |
After host comes up able too access VM console |
P1 |
functional |
|
48 |
Reboot host |
Reboot host |
|
P1 |
functional |
|
49 |
Bring down the network connectivity of the host. |
Bring down the network connectivity of the host. |
|
P1 |
functional |
|
50 |
Bring down the network connectivity of the host and then bring the network connectivity back up again. |
Bring down the network connectivity of the host and then bring the network connectivity back up again. |
|
P1 |
functional |
|
|
|
|
|
|
|
|
|
Allocators |
|
|
|
|
|
51 |
Deploy a Vm with a host tag that points to Baremetal host , when there are multiple baremetal hosts with the same host tag. |
Deploy a Vm with a host tag that points to Baremetal host , when there are multiple baremetal hosts with the same host tag. |
Deployment succeed |
P1 |
functional |
Pass |
52 |
Deploy multiple Vm with a host tag that points to Baremetal host , when there are multiple baremetal hosts with the same host tag. |
Deploy multiple Vm with a host tag that points to Baremetal host , when there are multiple baremetal hosts with the same host tag. |
Deployment succeed |
P1 |
functional |
Pass |
53 |
Deploy a Vm with a host tag that points to Baremetal host , when there is 1 Vm running in all the baremetal hosts with this host tag. |
Deploy a Vm with a host tag that points to Baremetal host , when there is 1 Vm running in all the baremetal hosts with this host tag. |
Deployment should fail |
P1 |
functional |
Pass |
54 |
Deploy a Vm with a host tag when there are multiple Baremetal hosts , some with host tag - tag1 and others with host tag -tag2. |
Deploy a Vm with a host tag when there are multiple Baremetal hosts , some with host tag - tag1 and others with host tag -tag2. |
Deployment succeed |
P1 |
functional |
Pass |
55 |
Deploy a Vm with a host tag that points to Baremetal host , when there is 1 Vm running in all the baremetal hosts with this host tag. |
Deploy a Vm with a host tag that points to Baremetal host , when there is 1 Vm running in all the baremetal hosts with this host tag. |
|
P1 |
functional |
Fail unable to test https://issues.apache.org/jira/browse/CLOUDSTACK-1440 |
|
|
|
|
|
|
|
|
VM life Cycle: |
|
|
|
|
|
56 |
Stop a VM that is running on Baremetal host. |
Stop a VM that is running on Baremetal host. |
VM to stop state |
P1 |
functional |
|
57 |
Start a VM that is in "stopped" state on Baremetal host. |
Start a VM that is in "stopped" state on Baremetal host. |
VM to start state |
P1 |
functional |
Fail unable to test |
58 |
Destroy a VM. |
Destroy a VM. |
VM destroyed |
P1 |
functional |
|
59 |
Restore/Reset VM |
Restore/Reset VM |
VM restored |
P1 |
functional |
|
60 |
Reboot a VM that is running on Baremetal host. |
Reboot a VM that is running on Baremetal host. |
|
P1 |
functional |
|
61 |
Change the Service Offering of a VM in "Stopped" state. Can we get the VM to start in a different host now by changing the host tags in the new service offering ? |
Change the Serive Offering of a VM in "Stopped" state. Can we get the VM to start in a different host now by changing the host tags in the new service offering ? |
after VM in stop state |
P1 |
functional |
Fail unable to test https://issues.apache.org/jira/browse/CLOUDSTACK-1618 |
64 |
Update Vm and set userdata for a VM that was deployed with no userdata. |
Update Vm and set userdata for a VM that was deployed with no userdata. |
|
P1 |
functional |
|
65 |
Update Vm and set a different userdata for a VM that was deployed with some userdata to begin with. |
Update Vm and set a different userdata for a VM that was deployed with some userdata to begin with. |
|
P1 |
functional |
|
66 |
Retrieve userdata of the user Vms. |
Retrieve userdata of the user Vms. |
|
P1 |
functional |
|
67 |
Retrieve metadata of the user Vms. |
Retrieve metadata of the user Vms. |
|
P1 |
functional |
|
68 |
Migrate Virtual machine() ..API should throw an error in this case. |
Migrate Virtual machine() ..API should throw an error in this case. |
|
P2 |
negative |
|
|
|
|
|
|
|
|
|
Account |
|
|
|
|
|
69 |
Delete an Account which has Vms running in SG. |
Delete an Account which has Vms running in SG. |
Account, VM, volumes, network, SG should be deleted |
P1 |
functional |
Fail due to |
|
|
|
|
|
|
|
|
Security Groups |
|
|
|
|
|
70 |
Deploy a VM by passing a Security Group. |
1.To the default security group, Add a TCP ingress rule for a port range (22-80) for any ipaddress (cidr1). |
1. VM should be deployed as part of only SG1 not default security group. |
P1 |
functional |
Pass |
71 |
Deploy a VM by passing a list of Security Groups. |
1. Create a Security Group SG1. |
1. VM should be deployed as part of all 3 SG rules. |
P1 |
functional |
Pass |
|
CIDR based Ingress rules |
|
|
|
|
|
72 |
Deploy a VM in a Security group which has an ingress rule that allows TCP protocols for a port range for a cidr. |
1.Create a Security Group SG1. |
1. VM deployment should succeed. |
P1 |
functional |
Pass |
73 |
Deploy a VM in a Security group which has an ingress rule that allows ICMP protocols for a 1 type and 1 code for a cidr. |
1.Create a Security Group SG1. |
1. VM deployment should succeed. |
P1 |
functional |
Pass |
73 |
Deploy few Vms in a Security group which has an ingress rule that allows TCP protocols for cidr1. |
1.Create a Security Group SG1. |
Before Step4: |
P1 |
functional |
Pass |
74 |
Deploy few Vms in a Security group which has an ingress rule that allows TCP protocols for cidr1 and cidr2. |
1.Create a Security Group SG1. |
Before Step4: |
P1 |
functional |
Pass |
75 |
Deploy few Vms in a Security group which has an ingress rule that allows ICMP protocols for cidr1 and cidr2. |
1.Create a Security Group SG1. |
Before Step4: |
P1 |
functional |
Pass |
76 |
Add Ingress rules when the VM is in stopped state. |
1.Create a Security Group SG1. |
As part of starting the VM , we should see the iptable rules being reprogrammed. |
P1 |
functional |
Pass |
77 |
Delete an Ingress rules when the VM is in stopped state. |
1.Create a Security Group SG1. |
Before Step4: |
P1 |
functional |
Pass |
|
Account based Ingress rules |
|
|
|
|
|
78 |
Deploy a VM in a Security group which has an ingress rule that allows TCP protocols for a port range for another Security Group - SG2. |
1. Deploy few Vms in Security Group - SG2. |
VM should get deployed successfully. |
P1 |
functional |
Pass |
79 |
VM should be accessible using their vm name from any other VM. |
1. Deploy few VM in Security Group - SG2. |
VM should get deployed successfully. |
P1 |
functional |
Pass |
80 |
Deploy a VM in a Security group which has an ingress rule that allows ICMP protocols for a port range for another Security Group - SG2. |
1. Deploy few Vms in Security Group - SG2. |
VM should get deployed successfully. |
P1 |
functional |
Pass |
81 |
Deploy a VM in a SG that is allowed Ingress access to another Security Group. |
Pre-Red: |
This should result in the new VM's ipaddress being added to the ingress chain of all the Vms that are part of SG1. |
P1 |
functional |
Pass |
82 |
Stop a VM that is in a SG that is allowed Ingress access to another Security Group. |
Pre-Red: |
This should result in the stopped VM's ipaddress being removed from the ingress chain of all the Vms that are part of SG1. |
P1 |
functional |
Pass |
83 |
Stop and Start a VM that is in a SG that is allowed Ingress access to another Security Group. |
Pre-Red: |
After Step1: |
P1 |
functional |
Pass |
84 |
Destroy a VM that is in a SG that is allowed Ingress access to another Security Group. |
Pre-Red: |
This should result in the destroyed VM's ipaddress being removed from the ingress chain of all the Vms that are part of SG1. |
P1 |
functional |
Pass |
85 |
Restore a destroyed VM that is in a SG that is allowed Ingress access to another Security Group. |
Pre-Red: |
After Step1: |
P1 |
functional |
Pass |
86 |
Reboot a VM that is in a SG that is allowed Ingress access to another Security Group. |
Pre-Red: |
After Reboot is successful: |
P1 |
functional |
Pass |
|
CIDR based egress rules |
|
|
|
|
|
87 |
Deploy a VM in a Security group which has NO egress rules. |
1.Create a Security Group SG1. |
1. VM deployment should succeed. |
P1 |
functional |
Fail Unable to test |
88 |
Deploy a VM in a Security group which has an egress rule that allows TCP protocols for a port range for a cidr. |
1.Create a Security Group SG1. |
1. VM deployment should succeed. |
P1 |
functional |
|
89 |
Deploy a VM in a Security group which has an egress rule that allows ICMP protocols for 1 type and 1 code for a cidr. |
1.Create a Security Group SG1. |
1. VM deployment should succeed. |
P1 |
functional |
|
90 |
Deploy few Vms in a Security group which has an egress rule that allows TCP protocols for cidr1. |
1.Create a Security Group SG1. |
Before Step4: |
P1 |
functional |
|
91 |
Deploy few Vms in a Security group which has an egress rule that allows TCP protocols for cidr1 and cidr2. |
1.Create a Security Group SG1. |
Before Step4: |
P1 |
functional |
|
92 |
Deploy few Vms in a Security group which has an egress rule that allows ICMP protocols for cidr1 and cidr2. |
1.Create a Security Group SG1. |
Before Step4: |
P1 |
functional |
|
93 |
Add egress rules when the VM is in stopped state. |
1.Create a Security Group SG1. |
As part of starting the VM , we should see the iptable rules being reprogrammed. |
P1 |
functional |
|
94 |
Delete an egress rules when the VM is in stopped state. |
1.Create a Security Group SG1. |
Before Step4: |
P1 |
functional |
|
|
Account based egress rules |
|
|
|
|
|
95 |
Deploy a VM in a Security group which has an egress rule that allows TCP protocols for a port range for another Security Group - SG2. |
1. Deploy few Vms in Security Group - SG2 that has a TCP ingress rules that allows port 22-80 for SG1. |
VM should get deployed successfully. |
P1 |
functional |
Fail Unable to test https://issues.apache.org/jira/browse/CLOUDSTACK-1439 |
96 |
Deploy a VM in a Security group which has an egress rule that allows ICMP protocols for another Security Group - SG2. |
1. Deploy few Vms in Security Group - SG2 that has a ICMP ingress rules that allows SG2. |
VM should get deployed successfully. |
P1 |
functional |
|
97 |
Stop a VM that is in a SG that is allowed egress access to another Security Group. |
Pre-Red: |
This should result in the stopped VM's ipaddress being removed from the egress chain of all the Vms that are part of SG1. |
P1 |
functional |
|
98 |
Stop and Start a VM that is in a SG that is allowed egress access to another Security Group. |
Pre-Red: |
After Step1: |
P1 |
functional |
|
99 |
Destroy a VM that is in a SG that is allowed egress access to another Security Group. |
Pre-Red: |
This should result in the destroyed VM's ipaddress being removed from the egress chain of all the Vms that are part of SG1. |
P1 |
functional |
|
100 |
Reboot a VM that is in a SG that is allowed egress access to another Security Group. |
Pre-Red: |
After Reboot is successful: |
P1 |
functional |
|
101 |
Deploy a VM in a Security group that allows for all Vms with in the Security Group to communicate with each other |
1. Create a Security Group SG1 that has a TCP ingress rules that allows port 22-80 for SG1. |
VM should get deployed successfully. |
P1 |
functional |
|
102 |
Deploy a VM in a Security group that allows for all Vms with in the Security Group to communicate with each other. This Security Group should also have restricted egress access to few other cidrs. |
1. Create a Security Group SG1 that has a TCP ingress rules that allows port 22-80 for SG1. |
After Step2: |
P1 |
functional |
|