You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

TestID

Test Case

Steps To Be Performed to Test

Verification Steps

Priority

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

 

2.

add a shared 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 shared network id
  1.  A new Nic for this new network is associated with VM
  2. Event Nic.created is generated

 

 

 

3.

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

 

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

 

5.

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

 

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.  API should fail

 

7.

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.  API should fail

 

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

 

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

 

10.

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

 

 

 

11.

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

 

12.

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

 

13.

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

 

14.

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.  API should fail

 

15.

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.  API should fail

 

16.

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

 

17.

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

 
  1.  API should fail

 

18.

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

 

19.

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

 

20.

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

 

21.

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

 
  1.  API should fail

 

22.

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

 
  1.  API should fail

 

23.

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

 

24.

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

 

25.

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

 

26.

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

 

27.

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

 

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

 

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

 

30

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

 

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

 

32

Verify UI for addNicToVirtualMachine

 

 

 

33

Verify UI for UpdateDefaultNicForVirtualMachine

 

 

 

34

Verify UI for removeNicFromVirtualMachine

 

 

 
  • No labels