Anuket Project

  • Created by Unknown User (christopherprice), last modified by Unknown User (matthewli) on Aug 31, 2016

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

Compare with Current View Page History

« Previous Version 22 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 CaseSuiteDescription
Add/Delete imageVIM operationsOpenStack Glance test using Tempest
Query/list imagesVIM operationsdo
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

Connect VMs

VIM operationsStart 2 VMs/containers and verify IPv4/IPv6 network connectivity between them
  ...fill out CRUD operations for instances, network (+ storage?)
   
   

Networking - test cases

Use CaseSuiteDescription
vPingsmoke(functest)two vms setup and can ping each other (ssh, userdata)
   

HA - test cases

Use CaseSuiteDescription
   
   

IPv6 - test cases

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

VPN - test cases

Use CaseSuiteDescription
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 CaseSuiteDescription
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)

 

  • No labels