...
| 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 | ||||
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 | |||
| network basic operations | NFVI / network | This smoke test suite assumes that Nova has been configured to boot VM's with Neutron-managed networking, and attempts to verify network connectivity | draft proposed | ||
| server basic operations | NFVI / compute | This smoke test case follows this basic set of operations: 1.Create a keypair for use in launching an instance 2.Create a security group to control network access in instance 3. Add simple permissive rules to the security group 4. Launch an instance 5. Perform ssh to instance 6. Verify metadata service 7. Verify metadata on config_drive 8. Terminate the instance | draft proposed | ||
| NetworkAdvancedServerOps | .Check VM connectivity after some advanced instance operations | ||||
| GettingAddress | NFVI/networking | 1,Create network with subnets 2. Boot 2 VMs on this network 3.Allocate and assign 2 FIP4 4.Check that vNICs of all VMs gets all addresses actually assigned 5. Each VM will ping the other's v4 private address | |||
| swift basic ops | NFVI/ storage | 1,get swift stat 2.create container. 3.upload a file to the created container. 4.list container's objects and assure that the uploaded file is present. 5.download the object and check the content | |||
| security groups basic ops | This test suite assumes that Nova has been configured to boot VM's with Neutron-managed networking, and attempts to verify cross tenant connectivity as follows | ||||
| VolumeBootPattern | NFVI | 1. Create in Cinder some bootable volume importing a Glance image 2. Boot an instance from the bootable volume 3. Write content to the volume 4, Delete an instance and Boot a new instance from the volume 5.Check written content in the instance | |||
| AggregatesBasicOps | NFVI |
| |||
| ShelveInstance | 1.boot an instance and create a timestamp file in it 2. shelve the instance 3. unshelve the instance 4. check the existence of the timestamp file in the unshelved instance | ||||
| encrypted cinder volumes |
|
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 |
...