Versions Compared

Old Version 40

changes.mady.by.user Unknown User (hongbotian)

Saved on

compared with

New Version 41

changes.mady.by.user Unknown User (hongbotian)

Saved on

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)

Basic VIM operations 

test caseSuiteDescriptionstatuscomments
Add/Delete imageVIM operationsOpenStack Glance test using Tempestdraftetherpad
Query/list imagesVIM operationsdo(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 networkVIM operationsOpenStack Network(Neutron) test using Tempest  
Create/Delete subnetVIM operationsdo  
Create/Delete portVIM operationsdo  

Start an instance

VIM operationsStart a VM/container, verify that it comes up / OpenStack Nova Tempest test  
Stop an instanceVIM operationsStop a VM/container, verify that it goes down/ / OpenStack Nova Tempest test  
Show server detailsVIM operations   
List serversVIM operations   
Update serverVIM operations   
Create serverVIM operations   
Delete serverVIM operations   
Update metadata itemsVIM operations   
Stop and start serverVIM operations   
Reboot serverVIM operations   
Confirm resized serverVIM operations   
Resize serverVIM operations   
Live-migrate serverVIM operations   
List hostsVIM operations   
Create flavorVIM operations   
List flavors with detailsVIM operations   
Show flavor detailsVIM operations   
Create extra specs for a flavorVIM operations   
Show an extra spec for a flavorVIM operations   
Attach and detach a volume by NovaVIM operations   
Attach and detach a volume by CinderVIM operations   
  ...fill out CRUD operations for instances, network (+ storage?)  
     

Category: Networking (Details)

Use CaseSuiteDescriptionstatuscomments
vPingsmoke(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 CaseSuiteDescriptionstatuscomments

yardstick_tc010
measure memory read latency using lmbench

nfvi/compute

measure memory read latency, No SLA, some adapted work is needed

---> CAN Measure measure memory read latency

  

yardstick_tc012
Measure memory read and write bandwidth using lmbench

nfvi/computeNo SLA  

yardstick_tc014
Measure Processing speed using unixbench

nfvi/computeNo SLA  
yardstick_tc055
number of cores, number of threads, available memory size and cache size		nfvi/computeNo SLA  
     

storage - test cases

Use CaseSuiteDescriptionstatuscomments

yardstick_tc005
Measure Storage IOPS, throughput and latency using fio

nfvi/storageNo SLA  

 

    
     

HA - test cases

Use CaseSuiteDescriptionstatuscomments

opnfv_yardstick_tc052
OpenStack Controller Node Disk I/O Block High Availability

HA   

opnfv_yardstick_tc053
Openstack Controller Load Balance Service High Availability

HA   

opnfv_yardstick_tc054
OpenStack VIP Master Node abnormally shutdown High Availability

HA   

 

IPv6 - test cases

Use CaseSuiteDescriptionstatuscomments
IPv6 IPAM for an instance IPv6Verify DHCPv6 (stateful & stateless), SLAAC  
Security rulesIPv6IPv6 security rules for Neutron  
IPv6 routingIPv6using switch/router, IPv6 service VM etc.  

VPN - test cases

Use CaseSuiteDescriptionstatuscomments
VPN operationsVPN 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
  
VPN operationsBGP 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
  
Subnet connectivityVPN DCVPN provides connectivity between subnets. different Neutron subnets cannot reach each other unless they are connected to the same Router.  

Tenant separation

VPN DCVPNs 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 integrationVPN MultisiteData Center Gateway integration, check if routes are correctly exchanged between SDN controller and datacenter gateway  
Inter-DC communicationVPN MultisiteInter-DC communication, Check if communication between two data centers connected through an MPLS backbone works.  

Fault Management - test cases

Use CaseSuiteDescriptionstatuscomments
Relaunch instance ?Fault managementWhen an instance fails, can the platform restart the instance automatically?  
Scale-up ?Fault managementCan a new instance of a given type be launched when a certain load is hit?  
Subscribe to a fault eventFault managementListen 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:

  1. Basic VIM operations (CRUD for instances, networks)
  2. Networking
  3. HA (Service availability, instance availability)
  4. IPv6
  5. VPN
  6. Fault management (FCAPS)
  7. SFC

 

Lower priority area ideas (mostly because of unclear scope, or unclear capabilities in OPFNV):

  1. Security
  2. Policy enforcement (hardware/host requirements, affinity/anti-affinity, SLA)
  3. Application LCM (not sure what this might mean)
  4. Scalability (scale-in, scale-out?)
  5. Updates, upgrades (deploying host, guest updates)
  6. Storage?
  7. Regulatory compliance (question)

 

Table of Contents
test case