...
| ID | Type | Test Case | Description | Pre-condition & requirements | Status | Gerrit References |
|---|---|---|---|---|---|---|
| 1 | VPN | VPN CRUD | 1. Create VPN instance and check command return code 2. Check if VPN instance is present 3. Create IETF VM interface and check return code 4. Verify IETF VM interface 5. Create VPN interface for IETF interface 6. Verify VPN interface 7. Verify FIB entry after create 8. Delete VM VPN interface 9. Verify after deleting VM VPN interface 10. Delete VPN instance 11. Verify after deleting VPN instance 12. Delete VM IETF interface 13. Verify after deleting VM IETF interface 14. Verify FIB entry after delete | |||
| 2 | VPN | BGP VPN CRUD | 1. Create BGPVPN 2. Create BGPVPN with malformatted route target (e.g. ASN:NN) should fail. 3. Create BGPVPN with invalid route target (e.g. 65536:0) should fail. 4. Getting the VPN list works without producing an error. 5. Updating an existing BGPVPN works. 6. Displaying parameters of an existing BGPVPN works. 7. Deleting a BGPVPN works. 8. Associating an existing BGPVPN with a Neutron network works 9. Getting the associated Neutron network works. 10. Deleting the network association works. 11. Associating an existing BGPVPN with a Neutron Router works 12. Getting the associated Neutron router works. 13. Deleting the router association works | |||
| 3 | VPN | Data Center Gateway integration | Data Center Gateway integration, check if routes are correctly exchanged between SDN controller and datacenter gateway | |||
| 4 | VPN | Inter-DC communication | Inter-DC communication, Check if communication between two data centers connected through an MPLS backbone works. | |||
| 5 | VPN | Subnet connectivity | VPN provides connectivity between subnets. different subnets cannot reach each other unless they are connected to the same Router. | Colorado Scenario: odl_l2, bgpvpn VIM: Openstack Components: Nova, Cinder, Neutron, KeyStone SDN: ODL Feature: no feature needed | ||
| 6 | VPN | Tenant separation | VPNs enable using the same IP address ranges in different VPNs, which is an important feature for tenant separation in the DC. This test verifies if the correct VM is reached under a given IP address when IP addresses are used multiple times in the same DC. | Colorado Scenario: odl_l2, bgpvpn VIM: Openstack Components: Nova, Cinder, Neutron, KeyStone SDN: ODL Feature: no feature needed | ||
| 7 | VPN | VPN provides connectivity between subnets using router association | VPN provides connectivity between subnets using router association | Colorado Scenario: odl_l2, bgpvpn VIM: Openstack Components: Nova, Cinder, Neutron, KeyStone SDN: ODL Feature: no feature needed | ||
| 8 | VPN | A subnet with a router attached can be associated to a VPN with network association and given a floating IP | A subnet with a router attached can be associated to a VPN with network association and given a floating IP | Colorado Scenario: odl_l2, bgpvpn VIM: Openstack Components: Nova, Cinder, Neutron, KeyStone SDN: ODL Feature: no feature needed |
Fault Management(Doctor)
| ID | Type | Test Case | Description | Pre-condition & requirements | Status | Gerrit References |
|---|---|---|---|---|---|---|
| 1 | Fault management | Relaunch instance ? | When an instance fails, can the platform restart the instance automatically? | |||
| 2 | Fault management | Scale-up ? | Can a new instance of a given type be launched when a certain load is hit? | |||
| 3 | Fault management | Subscribe to a fault event | Listen for an instance fault , and verify that when the instance is killed we hear about it | |||
| 4 | Fault management | failure notification | To test VM failure notification time. Boot a VM and create an alarm event in Ceilometer using the consumer ip. Once Doctor components are started, a failure is injected to the system, then the consumer receives a failure notification. | VIM: Openstack Components: Keystone, Nova, Neutron, Glance Additional component: Cinder, Ceilometer, Aodh, Congress, Vitrage Feature: Doctor |
...