Test Case ID |
Summary |
Category |
Verification Steps |
Expected Results |
Priority |
Status |
Comment/Remarks/bugs |
---|---|---|---|---|---|---|---|
1 |
Check "/etc/hosts" file inside the domR |
Functional Positive |
1) Start a domR, start a VM.<br>2) LoginComment/Remarks/bugs inside the domR and check that /etc/hosts table has just 2 entries: 1 for gateway, another for the VM:<br><br>10.1.1.1 gateway<br>10.1.1.2 i-2-4-TEST<br> |
1) Make sure that you don't have entries for non-existing vms in /etc/hosts.<br> |
P1 |
|
|
2 |
Reboot domR and verify that the latest network stat was sent to the management server in the result |
Functional Positive |
1) Create a domR.<br>2) Run some traffic.<br>3) Send rebootRouter command and verify that the agent sent the latest network stat to the management server in the result.<br> |
<br> |
P1 |
|
|
3 |
Stop domR and verify that the latest network stat was sent to the management server in the result |
Functional Positive |
1) Create a domR.<br>2) Run some traffic.<br>3) Send stopRouter command and verify that the agent sent the latest network stat to the management server in the result.<br> |
<br> |
P1 |
|
|
4 |
Public IP address should be assigned when domR is created, and released when domR is destroyed |
Functional Positive |
1) Create a user, start a first VM for him.<br>2) Make sure that public ip address got allocated by domR in vmops.user_ip_address table.<br>3) Delete the user, the domR is getting destroyed along.<br> |
1) Verify that publicIP got released once the domR got destroyed.<br> |
P1 |
|
|
5 |
Make sure that publicIP is not allocated when domR fails to create |
Functional Positive |
1) Create a user.<br>2) Make sure that you don't have a storage host.<br>3) Try to start a first VM by the user. You should fail to create a domR<br> |
1) Verify that publicIP didn't get allocated by the domR.<br> |
P1 |
|
|
6 |
rebootRouter for destroyed instance - Negative case |
Functional Negative |
1) Create an account. Start domR.<br>2) Destroy the account. The domR gets destroyed along.<br>3) Execute rebootRouter command with the id of destroyed router.<br> |
1) You should get an error response.<br> |
P2 |
|
|
7 |
Try to assign a new IP when domR is stopped - negative case |
Functional Negative |
1) Create and start a domR.<br>2) Stop the domR.<br>3) Try to allocate a new IP address when the domR is stopped.<br> |
1) You should be denied to do that.<br> |
P2 |
|
|
8 |
Try to release non-source NAT when domR is stopped |
Functional Positive |
1) Create and start a domR. IP assoc a new non-source nat ip address<br>2) Stop the domR.<br>3) Try to release the IP.<br> |
1) You should be able to do it.<br> |
P2 |
|
|
9 |
IP Assoc when domR is running |
Functional Positive |
1) Create and start a domR.<br>2) Try to associate a new ip address for the domR.<br><br> |
1) The new IP should be allocated for the domR in user_ip_address table.<br>2) From inside domR you should see the ip in the list for the public interface:<br><br>ip addr show | grep eth2<br>4: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000<br> inet 192.168.0.106/24 brd 192.168.0.255 scope global eth2<br> inet 192.168.0.106/32 scope global eth2<br> inet 192.168.0.108/32 scope global eth2<br> inet 192.168.0.110/32 scope global eth2<br> |
P1 |
|
|
10 |
Verify that when you deploy a first VM per account, a new domR getting created/started |
Functional Positive |
1) Create a user; and account is getting created along.<br>2) Send deployVirtualMachine command.<br> |
1) domR should be started.<br> |
P1 |
|
|
11 |
Verify that separete domR gets created per zone |
Functional Positive |
1) Configure multiZone setup.<br>2) Create an account.<br>3) Deploy 2 VMs in different zones.<br> |
1) 2 domRs should be started, 1 per zone.<br> |
P2 |
|
|
12 |
Vnet should be allocated once domR is started |
Functional Positive |
1) Create an account, start a VM.<br>2) DomR should be started, and "vnet" should be allocated for guestNetwork in "vmops.vnet" table<br> |
1) We allocate vnet once first domR is started by account<br> |
P1 |
|
|
13 |
Vnet should be released when account doesn't have vms/domRs running. Stop all VMs first |
Functional Positive |
1) Create an account, start a VM.<br>2) Stop the VM, stop the domR.<br> |
1) Make sure that vnet is released once the domR is stopped.<br> |
P1 |
|
|
14 |
Vnet should be released when account doesn't have vms/domRs running. Stop domR first |
Functional Positive |
1) Create an account, start a VM.<br>2) Stop the domR, then stop the VM.<br> |
1) Make sure that vnet is released once the vnet is stopped<br> |
P2 |
|
|
15 |
Assign IP address when domR is running |
Functional Positive |
1) Start domR per account (deploy a first VM).<br>2) Allocate a new ip address.<br> |
1) Login to domR and execute "ip addr show". You should see a new pubic IP in the list belonging to public interface.<br> |
P1 |
|
|
16 |
Assign IP address when domR is stoppped - Negative |
Functional Negative |
1) Start domR per account (deploy a first VM).<br>2) Stop the domR.<br>3) Try to allocate a new ip address.<br> |
1) You should fail to do it.<br> |
P2 |
|
|
17 |
Release non-source Nat ip address when domR is running |
Functional Positive |
1) Start domR.<br>2) Assign a new IP address.<br>3) Try to release the ip address.<br> |
1) You shouldn't see the ip address from inside the domR anymore.<br>2) Ip address should be released from the DB (check vmops.user_ip_address table)<br> |
P2 |
|
|
18 |
Release non-source Nat ip address when domR is stopped |
Functional Positive |
1) Start a domR.<br>2) Assign a new IP address.<br>3) Stop the domR.<br>4) Try to release the ip address.<br> |
1) You should be able to do it.<br>2) Ip address should be released from the DB (check vmops.user_ip_address table).<br>3) Once the domR is started, you shouldn't see the IP address in domR anymore.<br> |
P2 |
|
|
19 |
ROOT Admin should be able to release IP address of the regular user |
Functional Positive |
1) Create a user, start a domR by this user.<br>2) Get a new IP address by the user.<br>3) Login as admin and try to release the ip address belonging to the regular user.<br> |
1) You should be allowed to do it.<br> |
P2 |
|
|
20 |
Make sure that traffic is not getting generated when user VM doesn't sed anything |
Functional Positive |
1) Create an account.<br>2) Deploy a first VM. Make sure that there is no "yum update" cron job running.<br>3) Stop domR.<br> |
1) Verify that no traffic was generated during the domR stop.<br> |
P3 |
|
|
21 |
domR Live Migration: should get latest Network stat |
Functional Positive |
1) Deploy a domR.<br>2) Run some traffic.<br>3) Perform Live Migration for the domR.<br> |
1) You should get the latest network stat before the domR has migrated.<br> |
P2 |
|
|
22 |
Try to release sourceNat ip address - should fail |
Functional Negative |
1) Deploy a virtual machine for the user.<br>2) Try to send disassociateIpAddress command with the source nat ip address.<br> |
1) you should fail.<br> |
P2 |
|
|
23 |
Each network gets its own virtual router |
Functional Positive |
1)Create an account 2) Create a VM for this account 3) Create a VPN on the network used and select the IP associated with this account 4) Add user to VPN |
1) make sure a virtual router is created for this network |
P2 |
|
|