...
| ID | Test Case | Test Case Group | Description | Status | Gerrit References |
|---|---|---|---|---|---|
| 1 | Role CRD using Openstack Keystone | VIM operations | OpenStack Keystone test using Tempest | draft proposed |
|
...
NFVI
| ID | Test Case | Test Case Group | Description | Status | Gerrit References |
|---|---|---|---|---|---|
| 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 |
NFVI/Compute
| ID | Test Case | Test Case Group | DescriptionStatus | Gerrit References | ||
|---|---|---|---|---|---|---|
yardstick_tc010 | 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 | 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 | 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 | ||||
NFVI/Storage
| ID | Test Case | Test Case Group | Description | Status | Gerrit References |
|---|---|---|---|---|---|
yardstick_tc005 | 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 | |||
| |||||
| ...fill out CRUD operations for "network/subnet/router/port" operations |
High Availability (HA)
| ID | Test Case | Test Case Group | Description | Status | Gerrit References |
|---|---|---|---|---|---|
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 | |||||
OPNFV_YARDSTICK_TC054 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 |
...