Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
List of Category or "use cases" that would result in test suites or test objects to be covered by Dovetail over SUT (NFVi + VIM)
Category: Basic VIM operations (vim-ops) -summary
test designcase | suitetc# | test case number# | operations CRLUDX? | Description(test sub-cases/steps) | Status | Comments |
---|---|---|---|---|---|---|
server operations using Nova | vim-ops | tc<nnnn> to tc<mmm> | CRLUD XRb XRsz XRszC XP XS XAv XDv | Openstack Nova test using Tempest, Nova(v2), server create/delete/get/list/update/Reboot/Resize | Draft | C-Create/Boot/star,R-Query server,L-List server(s), U-update/Modify,D-Delete/stop, Rb-Reboot, Rsz-Resize,RszC-Confirm-Resize,P-Puase, S-Snapshot, A-Attach Volume, D-Detach Volume |
image operations using Glance | vim-ops | tc<nnnn> | CRLUD XLn | Openstack Glance test using Tempest, Glance(v2), images-v2-remove/update/share/list/delete/get, | Draft | D-Remove/Delete, Update(includes Share), R-Get, L-list C-Create or Load from URI/Path, Ln-Launch |
network Name operations using Neutron | vim-ops | tc<nnnn> | CRLUD | Openstack Neutron test using Tempest, Neutron(v2) network | Draft | network name/id |
network Sub-net operations using Neutron IPv4 | vim-ops |
tc<nnnn>
| CRLUD | Openstack Neutron test using Tempest, Neutron(v2) sub-net (IPv4) | Draft | sub-net name/ip<address> IPv4 |
network Sub-net operations using Neutron IPv6 | vim-ops | tc<mmm> | CRLUD | Openstack Neutron test using Tempest, Neutron(v2) sub-net (IPv6) | Draft | sub-net name/ip<address> IPv6 |
network Port operations using Neutron | vim-ops | tc<nnnn> | CRLUD | Openstack Neutron test using Tempest, Neutron(v2) port | Draft | port name/id binding to server instance |
block storage operations using Cinder | vim-ops | tc<nnnn> | CRLUD XA XD | Openstack Cinder test using Tempest, Cinder(v2) volume | Draft | volume name/id and A-attach /D-detach to server/server-id |
host operations using nova | vim-ops | tc<nnnn> | RLUD | Openstack Nova test using Tempest, Nova(v2) host | Draft | Read,List,Update,D-Remove? |
flavor operations using nova | vim-ops | tc<nnnn> | CRLUD | Openstack Nova test using Tempest, Nova(v2) flavor | Draft | C-Create,Read,List,Update, Delete |
object storage operations using S3/Swift | vim-ops | tc<nnnn> | ? | Openstack S3/Swift test using Tempest, S3/Swift(v2) flavor | Draft | ? |
(vim-ops) - Details
test 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 |
Show server details | VIM operations | |
List servers | VIM operations | |
Update server | VIM operations | |
Create server | VIM operations | |
Delete server | VIM operations | |
Update metadata items | VIM operations | |
Stop and start server | VIM operations | |
Reboot server | VIM operations | |
Confirm resized server | VIM operations | |
Resize server | VIM operations | |
Live-migrate server | VIM operations | |
List hosts | VIM operations | |
Create flavor | VIM operations | |
List flavors with details | VIM operations | |
Show flavor details | VIM operations | |
Create extra specs for a flavor | VIM operations | |
Show an extra spec for a flavor | VIM operations | |
Attach and detach a volume by Nova | VIM operations | |
Attach and detach a volume by Cinder | VIM operations | |
...fill out CRUD operations for instances, network (+ storage?) | ||
Category: Networking (Summary)
Test DesignCase | test suite | test case tc#number# | operations CRLUDX? | Description(test sub-cases/steps) | Status | Comments | |
---|---|---|---|---|---|---|---|
Virtual Ping IPv4 using Functest container | net-test | tc<nnnn> (IPv4) | CVMs LVMs cVrtr Xssh-VM11 XvPings Xssh-VM21 XvPings DVMs XReport | VM11-VM12 same subnet ping VM11-VM21 diff subnet ping VM11 VM12 on compHost1 VM21-VM22 on compHost2 | Draft | smoke tests assume Pharos POD config | |
Virtual Ping IPv6 using Functest container | net-test | tc<nnnn> (IPv6) | CVMs LVMs CvRtr Xssh-VM11 XvPings Xssh-VM21 XvPings DVMs XReport | VM11-VM12 same subnet ping VM11-VM21 diff subnet ping VM11 VM12 on compHost1 VM21-VM22 on compHost2 | Draft | smoke tests assume Pharos POD config |
Category: Networking (Details)
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 |
---|---|---|
yardstick_tc010 | nfvi/compute | measure memory read latency, No SLA, some adapted work is needed ---> CAN Measure measure memory read latency |
yardstick_tc012 | nfvi/compute | No SLA |
yardstick_tc014 | nfvi/compute | No SLA |
yardstick_tc055 number of cores, number of threads, available memory size and cache size | nfvi/compute | No SLA |
storage - test cases
Use Case | Suite | Description |
---|---|---|
yardstick_tc005 | nfvi/storage | No SLA |
| ||
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
Table of Contents |
---|