Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0

TestID

Test Case

Steps To Be Performed to Test

Verification Steps

Execution status

1.

add an isolated network via addNicToVirtualMachine api to a VM in running state for xen hypervisor

  1.  Create a VM in advanced Zone
  2. call addNicToVirtualMachine with a new isolated network id
  1.  A new Nic for this new network is associated with VM
  2. Event Nic.created is generated

Pass

2.

add a shared network via addNicToVirtualMachine api to a VM in running state for xen hypervisor

  1. Create a VM in advanced ZoneZone 
  2. call addNicToVirtualMachine with a new shared network id
  1.  A new Nic for this new network is associated with VM
  2. Event Nic.created is generated

Pass

 

 

3

add a isolated network that is in implemented state to a VM

  1. Create a VM in advanced Zone
  2. Create a Isolated network
  3. call addNicToVirtualMachine with a new isolated network id
  1. A new Nic for this new network is associated with VM
  2. A router for this network comes up
  3. Event Nic.created is generated

Pass

 

 

4

Verify usage for addNicToVirtualMachine

 

  1. usage event network.offerings.assign should be generated when addNicToVirtualMachine api is called

Pass

 

 

5

Verify usage for removenicfromvirtual machine

 

  1. usage event NETWORK.OFFERING.REMOVE should be generated when removeNicFromVirtualMachine api is called

Pass

 

 

6

Verify usage for updateNicforVirtualmachine

 

  1. UpdateDefaultNicForVirtualMachine api should also create usage events for updating new default network

Pass

 

 

7.

add an isolated network via addNicToVirtualMachine api to a VM in stopped state for xen hypervisor

  1. Create a VM in advanced Zone
  2. Stop the VM
  3. call addNicToVirtualMachine with a new shared network id
  1.  A new Nic for this new network is associated with VM
  2. Event Nic.created is generated

Pass

8 4.

add a shared network via addNicToVirtualMachine api to a VM in stopped state for xen hypervisor

  1.  Create a VM in advanced Zone
  2. Stop the VM
  3. call addNicToVirtualMachine with a new shared network id
  1.  A new Nic for this new network is associated with VM
  2. Event Nic.created is generated

Pass

5. 9

add a network and IP address via addNicToVirtualMachine api to a VM for xen hypervisor

  1.  Create a VM in advanced Zone
  2. call addNicToVirtualMachine with a new shared network id and IP address that we want to assign to the VM
  1.  A new Nic for this new network is associated with VM
  2. VM  has the provided IP address for this NIC
  3. Event Nic.created is generated

Pass

10 6.

add a VPC type of network to a running VM  belonging to isolated network via addNicToVirtualMachine api for xen hypervisor

  1. Create a VM in advanced Zone
  2. call addNicToVirtualMachine with a VPC network id
  1. A new Nic for this new network is associated with VM
  2. Event Nic.created is generated

Pass

7 11.

add a VPC type of network to a stopped VM  belonging to isolated network via addNicToVirtualMachine api for xen hypervisor

  1. Create a VM in advanced Zone
  2. Stop the VM
  3. call addNicToVirtualMachine with a VPC network id
  1. A new Nic for this new network is associated with VM
  2. Event Nic.created is generated

Pass

12 8.

add same network id multiple times to a VM via addNicToVirtualMachine api for xen hypervisor

  1. Create a VM in advanced Zone
  2. call addNicToVirtualMachine with a  network id to which VM  already belongs
  1.  A new Nic for this same network is associated with VM
  2. Event Nic.created is generated

Pass

  1.  APi should fail giving message Network already exists

Pass

13 9.

add an isolated network via addNicToVirtualMachine api to a VM in running state for kvm hypervisor

Same as above only hypervisor changes to KVM

  1.   A new Nic for this new network is associated with VM
  2. Event Nic.created is generated

Pass

10 14.

add a shared network via addNicToVirtualMachine api to a VM in running state for kvm hypervisor

Same as above only hypervisor changes to KVM

  1.   A new Nic for this new network is associated with VM
  2. Event Nic.created is generated

Pass

 

 

11 15.

add an isolated network via addNicToVirtualMachine api to a VM in stopped state for kvm hypervisor

Same as above only hypervisor changes to KVM

  1.   A new Nic for this new network is associated with VM
  2. Event Nic.created is generated

Pass

12 16.

add a shared network via addNicToVirtualMachine api to a VM in stopped state for kvm hypervisor

Same as above only hypervisor changes to KVM

  1.   A new Nic for this new network is associated with VM
  2. Event Nic.created is generated

Pass

13 17.

add a network and IP address via addNicToVirtualMachine api to a VM for KVM hypervisor

Same as above only hypervisor changes to KVM

  1.   A new Nic for this new network is associated with VM
  2. VM  has the provided IP address for this NIC
  3. Event Nic.created is generated

Pass

14 18.

add a VPC type of network to a running VM  belonging to isolated network via addNicToVirtualMachine api for kvm hypervisor

Same as above only hypervisor changes to KVM

  1. A new Nic for this new network is associated with VM
  2. Event Nic.created is generated API should fail

Pass

15 19.

add a VPC type of network to a stopped VM  belonging to isolated network via addNicToVirtualMachine api for kvm hypervisor

Same as above only hypervisor changes to KVM

  1. A new Nic for this new network is associated with VM
  2. Event Nic.created is generated API should fail

Pass

16 20.

add same network id multiple times to a VM via addNicToVirtualMachine api for kvm hypervisor

Same as above only hypervisor changes to KVM

  1.  A new Nic for this same network is associated with VM
  2. Event Nic.created is generated

Pass

  1.  APi should fail giving message Network already exists

Pass

21 17.

assign a Network(isolated / shared) belonging to different domain  to a  VM  belonging to different domain via addNicToVirtualMachine api

 

  1.  API should fail

Pass

18 22.

assign a Network (isolated) belonging to different account  to a VM  belonging to different account of same domain via addNicToVirtualMachine api

 

  1.  API should fail

Pass

19 23.

assign a Network (shared) tied to an account via security groups to a VM  belonging to different account of same domain

 

  1.  API should fail

Pass


 

20 24.

assign a Network to a VM belonging to an account which has already reached maximum number of networks that can be created for an account

 

  1.  API should fail

Pass

21 25.

Give network id and VM id belonging to different zone in addNicToVirtualMachine api

 

  1.  API should fail

Pass

22 26.

Give a invalid IP address (which can not be assigned to the VM ) and valid network ID in addNicToVirtualMachine api

 

  1.  API should fail

Pass

23 27.

Remove a nic (not default one) from a VM via removeNicFromVirtualMachine api for xen sever

  1.  Create a VM with multiple NIC
  2. Remove a non default nic via API removeNicFromVirtualMachine
  1. NIC is removed
  2. NIC.Removed event is generated

pass

24 28.

Remove a nic (default one) from a VM via removeNicFromVirtualMachine api for xen sever

  1.  Create a VM with multiple NIC
  2. Remove a default nic via API removeNicFromVirtualMachine
  1.  API should fail

pass

25 29.

Remove a nic  not belonging to the VM via removeNicFromVirtualMachine api

  1.  Create a VM with multiple NIC
  2. Remove a  nic not belonging to this VM via API removeNicFromVirtualMachine
  1.  API should fail

Pass

26 30.

Remove a nic (not default one) from a VM via removeNicFromVirtualMachine api for Kvm

  1.  Create a VM with multiple NIC
  2. Remove a non default nic via API removeNicFromVirtualMachine
  1.  NIC is removed
  2. NIC.Removed event is generated

Pass

27 31.

Remove a nic (default one) from a VM via removeNicFromVirtualMachine api for Kvm

  1.  Create a VM with multiple NIC
  2. Remove a default nic via API removeNicFromVirtualMachine
  1.  API should fail

Pass

32

remove network from VM is removing PF/LB/static nat rules for the VM

1..Create a VM with network N1
2. Create another network N2
3. Add N2 to VM created in step 1
4. Add PF , Load balancing rules to network N2 for VM
5. Acquire an IP in network N2
6. Enable static nat for VM
7. Remove network N2 from VM

  1. Verify remove network from VM is removing PF/LB/static nat rules for the VM

Pass

33

Pass

28

Update the specified NIC to be the default NIC for the specified VM via api  UpdateDefaultNicForVirtualMachine for Xen

  1. Create a VM with multiple NIC
  2. Update a non default nic to default one
  1. Default nic is updated
  2. Previous Default nic is now a non default one
  3. Event Nic.update is generated

Pass

34 29

Try to make default nic again default nic via api  UpdateDefaultNicForVirtualMachine

  1. Create a VM with multiple NIC
  2. Update  default nic to default one again
  1. API should fail

Pass

30 35

Try to make a nic not belonging to the VM as default nic via API UpdateDefaultNicForVirtualMachine

  1. Create a VM with multiple NIC
  2. Update a  nic not belonging to this VM to default one
  1. API should fail

Pass

36 31

Update the specified NIC to be the default NIC for the specified VM via api  UpdateDefaultNicForVirtualMachine for KVM

  1. Create a VM with multiple NIC
  2. Update a non default nic to default one
  1. Default nic is updated
  2. Previous Default nic is now a non default one
  3. Event Nic.update is generated

Pass

37 32

Verify UI for addNicToVirtualMachine

 

 

Pass

38

Verify UI not showing removed nic

  1. Create a VM
  2. Add 9 nics to the VM
  3. As Vm can have maximum 7 NICs last two will fail hence will be marked as removed in nic table in db

Verify UI shows only active nics of the VM

Fail
[https://issues.apache.org/jira/browse/CLOUDSTACK-2109
]

39 33

Verify UI for UpdateDefaultNicForVirtualMachine

 

 

Pass

40 34

Verify UI for removeNicFromVirtualMachine

 

 

Pass

41 35

Failure scenarios for  addNicToVirtualMachine
incorrect vmid

addNicToVirtualMachine

unable to find a virtual machine

Pass

42 36

incorrect network id

addNicToVirtualMachine

unable to find a network

Pass

43 37

Zone specified is Basic

addNicToVirtualMachine

Zone has a NetworkType of Basic. Can't add a new NIC to a VM on a Basic Network

 

44 38

Insufficient Permission

addNicToVirtualMachine

Unable to modify a vm using network id, permission denied

Pass

45 39

Vm and Network are not in same zone

addNicToVirtualMachine

vminstance is in zone<id>, but  network is in zone <id>

pass

46 40

network already has a vm with specified host name

addNicToVirtualMachine

network already has a vm with host name:

pass

47 41

Failure scenarios for removeNicFromVirtualMachine
 incorrect vmid

removeNicFromVirtualMachine

unable to find a virtual machine with id

pass

48 42

incorrect NIC id

removeNicFromVirtualMachine

unable to find a nic with id

pass

49 45

Nic is not present on Vm

removeNicFromVirtualMachine

<nicid>  is not a nic on  <vmInstanceid>

pass

50 46

Insufficient Permission

removeNicFromVirtualMachine

Unable to modify a vm using network with id , permission denied

Pass

51 47

Failure scenarios for UpdateDefaultNicForVirtualMachine
incorrect vmid

UpdateDefaultNicForVirtualMachine

unable to find a virtual machine with id

pass

52 48

incorrect NIC id

UpdateDefaultNicForVirtualMachine

unable to find a nic with id

pass

49

Changed default NIC is not in the correct network

UpdateDefaultNicForVirtualMachine

something strange happened, new default network is not null, and is not equal to the network of the chosen nic

 

50

Failed to change the NIC to default

UpdateDefaultNicForVirtualMachine

Failed to change default nic and now we have no default

 

51

Setting the NIC as default fails

UpdateDefaultNicForVirtualMachine

Setting a default nic failed, and we had no default nic, but we were able to set it back to the original

 

52

NiC profile not found for default network

UpdateDefaultNicForVirtualMachine

Failed to find a nic profile for the existing default network. This is bad and probably means some sort of configuration corruption

 

57

53

VM is not in Running/Stopped State

UpdateDefaultNicForVirtualMachine

refusing to set default nic, instance is not Running or Stopped

pass

58 54

specifiedNIC is already default

UpdateDefaultNicForVirtualMachine

refusing to set default nic because chosen nic is already the default

pass

59 55

Nic is not present on Vm

UpdateDefaultNicForVirtualMachine

<nicid>  is not a nic on <vmInstanceid>

pass