Versions Compared

Old Version 50

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

Saved on

compared with

New Version 51

changes.mady.by.user Trevor Cooper

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

IDTest CaseTest Case GroupDescriptionStatusGerrit References
 

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

Comment: There was an agreement not to include any performance related tests to the conformance test suite.

Comment: These tests are not related to platform compliance 

  
 

yardstick_tc012
Measure memory read and write bandwidth using lmbench

nfvi/compute

No SLA

Comment: There was an agreement not to include any performance related tests to the conformance test suite.

Comment: These tests are not related to platform compliance 

  
 

yardstick_tc014
Measure Processing speed using unixbench

nfvi/compute

No SLA

Comment: There was an agreement not to include any performance related tests to the conformance test suite.

Comment: These tests are not related to platform compliance 

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

No SLA

COmment: This is not relevant to compliance and conformance

  
      

...

IDTest CaseTest Case GroupDescriptionStatusGerrit References
 

yardstick_tc005
Measure Storage IOPS, throughput and latency using fio

nfvi/storage

No SLA

Comment: There was an agreement not to include any performance related tests to the conformance test suite.

Comment: These tests are not related to platform compliance 

  
 

 

    
      

High Availability (HA)

HAopnfvyardsticktc053
Openstack Controller Load Balance Service High AvailabilityHA
IDTest CaseTest Case GroupDescriptionStatusGerrit References 

opnfv_yardstick_tc052
OpenStack Controller Node Disk I/O Block High Availability

 

OPNFV_YARDSTICK_TC019_HA 

This test case will verify the high availability of the service provided by OpenStack (like nova-api, neutro-server) on control node.

    
 

OPNFV_YARDSTICK_TC025_HA 

This test case will verify the high availability of controller node. When one of the controller node abnormally shutdown, the service provided by it should be OK

    
 

OPNFV_YARDSTICK_TC045

This test case will verify the high availability of the network service provided by OpenStack (neutro-server) on control node 

    
 

OPNFV_YARDSTICK_TC046

 This test case will verify the high availability of the user service provided by OpenStack (keystone) on control node

    
 

OPNFV_YARDSTICK_TC047 

This test case will verify the high availability of the image service provided by OpenStack (glance-api) on control node

    
 

OPNFV_YARDSTICK_TC048

This test case will verify the high availability of the volume service provided by OpenStack (cinder-api) on control node 

    
 

OPNFV_YARDSTICK_TC049 

This test case will verify the high availability of the storage service provided by OpenStack (swift-proxy) on control node

    
 

OPNFV_YARDSTICK_TC050

This test case will verify the high availability of control node. When one of the controller failed to connect the network, which breaks down the Openstack services on this node. These Openstack service should able to be accessed by other controller nodes, and the services on failed controller node should be isolated 

    
 

OPNFV_YARDSTICK_TC051

This test case will verify the high availability of control node. When the CPU usage of a specified controller node is stressed to 100%, which breaks down the Openstack services on this node. These Openstack service should able to be accessed by other controller nodes, and the services on failed controller node should be isolated 

    
 

OPNFV_YARDSTICK_TC052

This test case will verify the high availability of control node. When the disk I/O of a specified disk is blocked, which breaks down the Openstack services on this node. Read and write services should still be accessed by other controller nodes, and the services on failed controller node should be isolated 

    
 

OPNFV_

YARDSTICK_

TC053

This test case will verify the high availability of the load balance service(current is HAProxy) that supports OpenStack on controller node. When the load balance service of a specified controller node is killed, whether other load balancers on other controller nodes will work, and whether the controller node will restart the load balancer are checked 

    
 

opnfvOPNFV_yardstickYARDSTICK_tc054
OpenStack VIP Master Node abnormally shutdown High AvailabilityTC054

This test case will verify the high availability for virtual ip in the environment. When master node of virtual ip is abnormally shutdown, connection to virtual ip and the services binded to the virtual IP it should be OK 

 HA   

 

IPv6

IDTest CaseTest Case GroupDescriptionStatusGerrit References
 IPv6 IPAM for an instance IPv6Verify DHCPv6 (stateful & stateless), SLAAC  
 Security rulesIPv6IPv6 security rules for Neutron  
 IPv6 routingIPv6using switch/router, IPv6 service VM etc.  
 

 OPNFV_YARDSTICK_TC027_IPv6 connectivity

To do a basic verification that IPv6 connectivity is within acceptable boundaries when ipv6 packets travel between hosts located on same or different compute blades.

    

VPN

IDTest CaseTest Case GroupDescriptionStatusGerrit References
 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.  

...

IDTest CaseTest Case GroupDescriptionStatusGerrit References
 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