- Created by Unknown User (christopherprice), last modified by Unknown User (hongbotian) on Sept 07, 2016
You are viewing an old version of this page. View the current version.
Compare with Current View Page History
« Previous Version 29 Next »
List of "use cases" that would result in test suites or test objects to be covered by Dovetail over SUT (NFVi + VIM)
Basic VIM operations - test cases
Use Case | Suite | Description |
---|---|---|
Add/Delete image | VIM operations | OpenStack Glance test using Tempest |
Query/list images | VIM operations | do(for openstack, there are 2 kinds of images related, 1st the nova, compute-images-create/delete/get/list, 2nd Glance, images-v2-remove/update/share/list/delete/get, MatthewLi ) |
Create/Delete network | VIM operations | OpenStack Network(Neutron) test using Tempest |
Create/Delete subnet | VIM operations | do |
Create/Delete port | VIM operations | do |
Start an instance | VIM operations | Start a VM/container, verify that it comes up / OpenStack Nova Tempest test |
Stop an instance | VIM operations | Stop a VM/container, verify that it goes down/ / OpenStack Nova Tempest test |
...fill out CRUD operations for instances, network (+ storage?) | ||
Networking - test cases
Use Case | Suite | Description |
---|---|---|
vPing | smoke(functest) | two vms setup in the same subnet and can ping each other (ssh, userdata, IPv4, IPv6(afraid not support now MatthewLi)) |
vRouter | Two VMs in two different subnets, connected by a Neutron virtual router, can ping each other | |
Security rules | Verify that a security rule prevents a type of traffic, remove rule, verify that traffic passes, add it back, test that traffic is stopped | |
External routing | Verify that a VM can access hosts external to the VIM | |
...fill out CRUD operations for "network/subnet/router/port" operations |
compute - test cases
Use Case | Suite | Description |
---|---|---|
storage - test cases
Use Case | Suite | Description |
---|---|---|
HA - test cases
Use Case | Suite | Description |
---|---|---|
opnfv_yardstick_tc052 | HA | |
opnfv_yardstick_tc053 | HA | |
opnfv_yardstick_tc054 | HA |
IPv6 - test cases
Use Case | Suite | Description |
---|---|---|
IPv6 IPAM for an instance | IPv6 | Verify DHCPv6 (stateful & stateless), SLAAC |
Security rules | IPv6 | IPv6 security rules for Neutron |
IPv6 routing | IPv6 | using switch/router, IPv6 service VM etc. |
VPN - test cases
Use Case | Suite | Description |
---|---|---|
VPN operations | VPN CRUD |
|
VPN operations | BGP VPN CRUD |
|
Subnet connectivity | VPN DC | VPN provides connectivity between subnets. different Neutron subnets cannot reach each other unless they are connected to the same Router. |
Tenant separation | VPN DC | 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. |
Data Center Gateway integration | VPN Multisite | Data Center Gateway integration, check if routes are correctly exchanged between SDN controller and datacenter gateway |
Inter-DC communication | VPN Multisite | Inter-DC communication, Check if communication between two data centers connected through an MPLS backbone works. |
Fault Management - test cases
Use Case | Suite | Description |
---|---|---|
Relaunch instance ? | Fault management | When an instance fails, can the platform restart the instance automatically? |
Scale-up ? | Fault management | Can a new instance of a given type be launched when a certain load is hit? |
Subscribe to a fault event | Fault management | Listen for an instance fault , and verify that when the instance is killed we hear about it |
Dovetail test areas.
Some "area" ideas in priority order:
- Basic VIM operations (CRUD for instances, networks)
- Networking
- HA (Service availability, instance availability)
- IPv6
- VPN
- Fault management (FCAPS)
- SFC
Lower priority area ideas (mostly because of unclear scope, or unclear capabilities in OPFNV):
- Security
- Policy enforcement (hardware/host requirements, affinity/anti-affinity, SLA)
- Application LCM (not sure what this might mean)
- Scalability (scale-in, scale-out?)
- Updates, upgrades (deploying host, guest updates)
- Storage?
- Regulatory compliance
- No labels